WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/gnu/usr.bin/binutils/opcodes?h=jd%2Fhistogram 2014-11-18T22:27:54Z 2014-11-18T22:27:54Z mpi mpi@openbsd.org 2014-11-18T22:27:54Z urn:sha1:11a30b8ce02bf5174b39dcdd2c2a9e0e51c65536 ok miod@, deraadt@ 2014-08-20T04:12:30Z guenther guenther@openbsd.org 2014-08-20T04:12:30Z urn:sha1:edc69924ddc8d56051f77025a4d399654b74382a Request and testing by krw@ 2014-02-09T22:42:27Z guenther guenther@openbsd.org 2014-02-09T22:42:27Z urn:sha1:3d8cda5c6dfb336dd44829ddb27918d91290d05e xrstor, and xsaveopt. based on kettenis's original that did xgetbv and xsetbv ok kettenis@ 2012-12-31T23:54:20Z miod miod@openbsd.org 2012-12-31T23:54:20Z urn:sha1:ef32b02ba689b1f014669bc462fecefb76aea7d1 2012-10-18T00:54:12Z jsg jsg@openbsd.org 2012-10-18T00:54:12Z urn:sha1:5ef8804eb2cb3fb082b117bcaf5d5819556e50d7 that controls the behaviour of Intel's Supervisor Mode Access Prevention (SMAP) feature. 'looks correct' miod@ ok deraadt@ 2012-09-07T22:33:01Z naddy naddy@openbsd.org 2012-09-07T22:33:01Z urn:sha1:0b2ac3b7f3d336ccaaf893d8f6d118f3a3ce5280 2010-06-11T10:50:48Z thib thib@openbsd.org 2010-06-11T10:50:48Z urn:sha1:47d15e0bce1a8b68c4e5962ace552a85d9da0b24 that are needed to omplement accelerated AES (and AES-GCM mode) on newer Intel cores. Diff from Mike Belopuhov. no objections/ok miod@ 2010-02-03T21:44:17Z miod miod@openbsd.org 2010-02-03T21:44:17Z urn:sha1:e4ff4a19c44407f2c73360fa24737543bf26b849 is intended to be used when compiling kernel code which will run on a Loongson 2E or 2F processor, and inserts an explicit BTB clear operation before every jump through a register (jr or jalr instructions), unless that register is k0 or k1, or we are in .set noat. This is a reliable, although aggressive, workaround for the misbehaviour of the branch prediction engine of many Loongson 2F processors with regard to the Branch Translation Buffer, for which an official errata has yet to be published, and for which the Loongson suggested workaround apparently only works due to pipeline side effects, but requires all the executable kernel code to be located in CKSEG0/CKSEG1. These changes are inspired by a backport of the Loongson binutils 2.19 patch to binutils 2.18; the idea of doing an aggressive BTB clear is mine. This causes no functional change to code compiled without the -mfix-loongson2f-btb option. ``looks reasonable'' kettenis@ 2005-01-20T22:42:17Z kettenis kettenis@openbsd.org 2005-01-20T22:42:17Z urn:sha1:17779c480f713f8c2d9bf34904b1837878f0e215 ok hshoexer@, it's my fault initially miod@ 2004-11-02T20:44:57Z miod miod@openbsd.org 2004-11-02T20:44:57Z urn:sha1:007c2a4539b8b8aaa95c5e73e77620090abe113b - extra $(SHELL) and sugar for make (so that files not mode +x still work) - safer temp file handling - our W^X binary layout changes in ld - OpenBSD policy for library file selection in ld - arm and m88k changes which were not merged in time for official 2.15 - bfd core file handling - a couple typos New for 2.15: - ld(1) and as(1) manpages now generated at build time - binutils/stabs.c reverted to use our in-tree libiberty for now - we still use our VIA C3 crypto code over stock binutils, as it recognizes more instructions - new emulations for OpenBSD on mips64 machines, to help OpenBSD/sgi - relaxed %f# handling in gas on OpenBSD/sparc64 (same as was in 2.14) Tested on all platforms by various people; special thanks to sturm@ and otto@.