WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/gnu/gcc?h=jd%2Fqueueboosts 2019-04-03T04:52:26Z 2019-04-03T04:52:26Z tedu tedu@openbsd.org 2019-04-03T04:52:26Z urn:sha1:1cbfedc589454d1648a14b53fbd0e0645f3d28c4 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. 2018-09-14T13:44:18Z naddy naddy@openbsd.org 2018-09-14T13:44:18Z urn:sha1:86f55b3d2a934eb190815c5f83a3d683acf7337d does not have a default search path. ok kettenis@ jsg@ 2018-07-20T10:02:03Z espie espie@openbsd.org 2018-07-20T10:02:03Z urn:sha1:154a9ab32bace1b31337109d92288a8db9fede87 flatly. this will help sparc64 compile code without needing to patch away recent pragma diagnostic use. problem found by landry@ okay kettenis@, guenther@ 2018-07-08T09:28:44Z kettenis kettenis@openbsd.org 2018-07-08T09:28:44Z urn:sha1:980c57468196583253c0914ca0e9ee6b99969e99 as the default linker on armv7. ok espie@ 2018-01-04T19:46:31Z kettenis kettenis@openbsd.org 2018-01-04T19:46:31Z urn:sha1:c7cbac187684cfb8bf7fa4d2401eb831ecbf60be 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@ 2017-08-20T11:12:42Z visa visa@openbsd.org 2017-08-20T11:12:42Z urn:sha1:ec223ac0f2a20d15b0aa7691596d53012f339a5a as full memory barriers. 2017-07-24T16:42:56Z kettenis kettenis@openbsd.org 2017-07-24T16:42:56Z urn:sha1:b428c8644ab58debe667f365296ae60b4a66efdc 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@ 2017-05-31T03:24:20Z stefan stefan@openbsd.org 2017-05-31T03:24:20Z urn:sha1:a7e293634bed787cebebfe65a74ec3cb6e3385bb For C++, gcc has to make use of comdat sections instead of .gnu.linkonce sections for this because switch tables and functions would now end up in different .gnu.linkonce sections. This can cause ld to sometimes incorrectly discard the switch tables, which causes linker errors. With comdat sections, making the switch table and function sections belong together is more reliable. ok deraadt@ 2017-05-08T20:58:40Z espie espie@openbsd.org 2017-05-08T20:58:40Z urn:sha1:cec5ac9d21d833fdec085b7f0bd8c8946f72c086 Reimplement that from scratch in our ancient gcc, because it's really useful for porting newer code and dealing with compiler variations. (slightly tweaked to reset location to unknown location after the okays) okay kettenis@ jasper@ found out https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28322 after the patch, which explains a similar reasoning better, and leads to another patch for older GCC, possibly GPLv3. 2017-04-27T00:02:03Z dlg dlg@openbsd.org 2017-04-27T00:02:03Z urn:sha1:c31aa7c2c5b9bbd839a954f05d7fd1e547476e82 i got sick of not having arguments in ddb stack traces on amd64, which is because amd64 passes arguments in registers, and it's impossible to figure out where they go without dwarf info, and when you have dwarf info it is complicated. solaris has a simple solution for this. they tweaked their compilers to accept an -msave-args option which makes functions store their arguments on the stack, while maintaining compatability with the System V AMD64 ABI. tools (eg, ddb) can then look at the stack to get access to function arguments in traces. this ports their changes to gcc 3 to our gcc. ok deraadt@