<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-openbsd/gnu/gcc, branch master</title>
<subtitle>WireGuard implementation for the OpenBSD kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-openbsd/atom/gnu/gcc?h=master</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-openbsd/atom/gnu/gcc?h=master'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/'/>
<updated>2021-02-01T05:49:48Z</updated>
<entry>
<title>a regular function decl collides with an inline, due to C99 inline rules.</title>
<updated>2021-02-01T05:49:48Z</updated>
<author>
<name>deraadt</name>
<email>deraadt@openbsd.org</email>
</author>
<published>2021-02-01T05:49:48Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=490e531a93b653cba1836d6c61936d91d79106eb'/>
<id>urn:sha1:490e531a93b653cba1836d6c61936d91d79106eb</id>
<content type='text'>
We are never updating this sub-tree.  Knock out the collision in the simplest
way.  diff from mortimer.
This is the last change required for -fno-common on all architectures,
thanks to mortimer for starting the effort and encouraging others.
</content>
</entry>
<entry>
<title>Don't pass the -dynamic-linker flag to ld when linking statically.</title>
<updated>2020-09-23T17:01:51Z</updated>
<author>
<name>millert</name>
<email>millert@openbsd.org</email>
</author>
<published>2020-09-23T17:01:51Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=1107cbef0eaf8f4f0f082368a3652533a380231c'/>
<id>urn:sha1:1107cbef0eaf8f4f0f082368a3652533a380231c</id>
<content type='text'>
Fixes creation of static binaries with base gcc and ld.lld.
OK kettenis@ a while ago, prodded by daniel@
</content>
</entry>
<entry>
<title>base tree had only two uses of the printf %n format string, in this file.</title>
<updated>2020-07-10T15:31:59Z</updated>
<author>
<name>deraadt</name>
<email>deraadt@openbsd.org</email>
</author>
<published>2020-07-10T15:31:59Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=28fe39c8b64e2a28225dd596f0fbf5248ae68fca'/>
<id>urn:sha1:28fe39c8b64e2a28225dd596f0fbf5248ae68fca</id>
<content type='text'>
Appending "%n" to the format string to capture the output-length in bytes
(into an uninitialized variable) is exactly the same as using the printf
return value.  Why did they do this so unnaturally?
(normally we don't change gcc import code, but I'm doing a study of %n
prevelance)
ok millert
</content>
</entry>
<entry>
<title>mortimer unlinked libobjc from the build, but didn't know how to cvs rm.</title>
<updated>2019-04-03T04:52:26Z</updated>
<author>
<name>tedu</name>
<email>tedu@openbsd.org</email>
</author>
<published>2019-04-03T04:52:26Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=1cbfedc589454d1648a14b53fbd0e0645f3d28c4'/>
<id>urn:sha1:1cbfedc589454d1648a14b53fbd0e0645f3d28c4</id>
<content type='text'>
I don't know much about compilers, but what I do have are a very particular
set of skills. Skills I have acquired over a very long career.
</content>
</entry>
<entry>
<title>Pass -L/usr/lib to the linker in preparation for switching to lld, which</title>
<updated>2018-09-14T13:44:18Z</updated>
<author>
<name>naddy</name>
<email>naddy@openbsd.org</email>
</author>
<published>2018-09-14T13:44:18Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=86f55b3d2a934eb190815c5f83a3d683acf7337d'/>
<id>urn:sha1:86f55b3d2a934eb190815c5f83a3d683acf7337d</id>
<content type='text'>
does not have a default search path.  ok kettenis@ jsg@
</content>
</entry>
<entry>
<title>inform that diagnostics in functions won't work, but don't error out</title>
<updated>2018-07-20T10:02:03Z</updated>
<author>
<name>espie</name>
<email>espie@openbsd.org</email>
</author>
<published>2018-07-20T10:02:03Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=154a9ab32bace1b31337109d92288a8db9fede87'/>
<id>urn:sha1:154a9ab32bace1b31337109d92288a8db9fede87</id>
<content type='text'>
flatly.

this will help sparc64 compile code without needing to patch away recent
pragma diagnostic use.

problem found by landry@

okay kettenis@, guenther@
</content>
</entry>
<entry>
<title>Explicitly pass -L/usr/lib to the linker.  Needed for switching to lld(1)</title>
<updated>2018-07-08T09:28:44Z</updated>
<author>
<name>kettenis</name>
<email>kettenis@openbsd.org</email>
</author>
<published>2018-07-08T09:28:44Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=980c57468196583253c0914ca0e9ee6b99969e99'/>
<id>urn:sha1:980c57468196583253c0914ca0e9ee6b99969e99</id>
<content type='text'>
as the default linker on armv7.

ok espie@
</content>
</entry>
<entry>
<title>Add ARM EABI aliases and remove functions that are also provided by our libc.</title>
<updated>2018-01-04T19:46:31Z</updated>
<author>
<name>kettenis</name>
<email>kettenis@openbsd.org</email>
</author>
<published>2018-01-04T19:46:31Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=c7cbac187684cfb8bf7fa4d2401eb831ecbf60be'/>
<id>urn:sha1:c7cbac187684cfb8bf7fa4d2401eb831ecbf60be</id>
<content type='text'>
This allows linking code compiled by clang with the gcc compiler driver
and makes sure we always use the softfloat implementation in libc.  The
libc softfloat implementation is preferred over the one in libgcc as it
implements rounding modes and floating point exceptions.

ok patrick@
</content>
</entry>
<entry>
<title>Fix the __sync_* functions to make them work properly</title>
<updated>2017-08-20T11:12:42Z</updated>
<author>
<name>visa</name>
<email>visa@openbsd.org</email>
</author>
<published>2017-08-20T11:12:42Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=ec223ac0f2a20d15b0aa7691596d53012f339a5a'/>
<id>urn:sha1:ec223ac0f2a20d15b0aa7691596d53012f339a5a</id>
<content type='text'>
as full memory barriers.
</content>
</entry>
<entry>
<title>Make gcc accept -Oz as an alias for -Os for compatibility with clang.</title>
<updated>2017-07-24T16:42:56Z</updated>
<author>
<name>kettenis</name>
<email>kettenis@openbsd.org</email>
</author>
<published>2017-07-24T16:42:56Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=b428c8644ab58debe667f365296ae60b4a66efdc'/>
<id>urn:sha1:b428c8644ab58debe667f365296ae60b4a66efdc</id>
<content type='text'>
With clang -Os doesn't generate the smallest code possible but some middle
ground between optimization for speed and optimization for size.  A new -Oz
option was introduced for optmization for size only.  We need that for our
floppies, otherwise they overflow.  Making gcc accept -Oz too makes our life
easier.

ok millert@, deraadt@, robert@
</content>
</entry>
</feed>
