| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
ok miod@, deraadt@
|
| |
|
|
| |
Request and testing by krw@
|
| |
|
|
|
|
|
| |
xrstor, and xsaveopt.
based on kettenis's original that did xgetbv and xsetbv
ok kettenis@
|
| | |
|
| |
|
|
|
|
|
| |
that controls the behaviour of Intel's Supervisor Mode Access Prevention
(SMAP) feature.
'looks correct' miod@ ok deraadt@
|
| | |
|
| |
|
|
|
|
|
|
|
| |
that are needed to omplement accelerated AES (and AES-GCM mode) on newer
Intel cores.
Diff from Mike Belopuhov.
no objections/ok miod@
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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@
|
| |
|
|
| |
ok hshoexer@, it's my fault initially miod@
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- 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@.
|
| | |
|
| |
|
|
| |
ok drahn@
|
| |
|
|
|
| |
isn't that far away... xcrypt-ctr (AES ctr mode), montmul (montgomery
multiply for 800 RSA sign/sec at 1024bit), and xsha1/xsha256 too.
|
| |
|
|
| |
ok drahn@
|
| |
|
|
| |
remove testsuites (not useable) remove mmalloc (not part of new binutils).
|
| | |
|
| |
|
|
|
|
|
| |
From: binutils CVS HEAD branch, based on rev 1.8
Reported by: Daniel Lucq <daniel at lucq dot org>
ok miod@
|
| | |
|
| | |
|
| |
|
|
|
|
| |
- only the binutils package (no gdb here)
- don't import libiberty and texinfo, they are elsewhere
- remove all .info* generated files
|
| | |
|
| | |
|
| |
|
|
| |
(This is probably a work-around for a bug in ksh)
|
| |
|
|
| |
(trivial part done, `interesting' patches remain)
|
| | |
|
| |
|
|
|
|
| |
- only the binutils package (no gdb here)
- don't import libiberty and texinfo, they are elsewhere
- remove all .info* generated files
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
on - this way now the whole tree builds without requiring any file
being executable (binutils was the last which required it) - now
ctm -> cvs checkout -> make build works just fine (aside from
other bugs in the source tree :-)
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
mpi
guenther
miod
jsg
naddy
thib
kettenis
tom
deraadt
drahn
brad
fgsch
espie
d
niklas
graichen