| Age | Commit message (Collapse) | Author |
|---|
|
that are needed to omplement accelerated AES (and AES-GCM mode) on newer
Intel cores.
Diff from Mike Belopuhov.
no objections/ok miod@
|
|
found the hard way by matthieu@ and krw@
in /usr/xenocara/lib/libXaw/spec/strings.mit.
This needs to be done more carefully. Sorry!
|
|
millert@ ok.
|
|
in both our old in-tree groff and in mandoc, because
1) It looks and reads better.
2) It agrees with both bsd.lv mandoc and with modern groff.
The tmac.an part was done by millert@, with a minor fix by me.
While touching our old groff, switch off hyphenation, suggested a long
time ago by millert@. It helps searching and comparisons.
While touching mandoc terminal_man(), explicitely initialize the
tabwidth - not strictly required, but easier to understand
and more robust, also suggested by millert@.
General mumbling of agreement by many,
including millert@ deraadt@ jmc@ sobrado@ ...
Remaining problem:
Setting the title length (.lt) has no effect for me,
but we can fix this in tree in case anybody figures it out.
|
|
some man pages when built with gcc4.
ok deraadt
|
|
as discussed with Theo, so that he can synch set.
(eventual gcc2 fallout to fix later)
|
|
through the PLT.
|
|
with out own rules but apparently this causes problems after
git_version.h is generated in the obj dir. This will only ever be
a stub as we build from a release, not a git checkout. Add a
pre-generated lib/Config_git.pl and prevent git_version.h and
Config_git.pl from being removed by the clean target.
Appears to fix parallel make issues. OK oga@
|
|
|
|
problem spotted by matthieu/naddy
okay kettenis@, matthieu@
|
|
is now NULL for zero-length arrays so check for that).
ok avsm
|
|
complier picking, eg supporting gcc2, gcc3, and gcc4. based on diff by Marco,
with fixes from espie@.
ok espie@ general mumbling of approval of others.
|
|
okay millert@, nicm@ ...
(thx others for pointing out stupidity in intermediate patches...)
|
|
ok oga kettenis
committed in the skys over the continental us :-)
|
|
|
|
|
|
the process; ok kettenis@ miod@
|
|
headers.
ok robert kettenis jsg
|
|
ok jsg@, miod@
|
|
work on sparc64.
|
|
handling work with shared libraries.
|
|
ok kettenis@
|
|
|
|
|
|
|
|
check the arguments. Fixes autocrap tests in c++, which otherwise fail with
"error: nonnull argument with out-of-range operand number".
miod@ ok
|
|
|
|
|
|
|
|
actual cross support.
|
|
|
|
|
|
'looks reasonable' kettenis@
|
|
progress.
most of the smarts from drahn, ok drahn
|
|
|
|
|
|
okay millert@
|
|
|
|
2004-08-10 Mark Mitchell <mark@codesourcery.com>
* expr.c (operand): Handle the "~", "-", and "!" operators applied
to bignums.
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gas/expr.c.diff?cvsroot=src&only\
_with_tag=MAIN&r2=1.52&r1=1.51&f=u
Fixes the problem mentioned here:
http://llvm.org/bugs/show_bug.cgi?id=6528
ok jsg@, miod@
|
|
ok miod@
|
|
simplify_shift_const(), and only do this on mips64 platforms, because we are
too late in the release cycle.
This change has the nice side effect of preventing a wrong overoptimistic
optimization on mips64, when masking bit 31 of a long; which in turns causes
python to misbehave.
Help and ok otto@
|
|
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@
|
|
files or directories when applicable.
The inspiration and name of MACHINE_CPU come from NetBSD, although the way to
provide it to Makefiles is completely different.
ok kettenis@
|
|
Actually we should probably look further than just the immediate
predecessor here. ok miod@
|
|
when compiling boost 1.41.
From http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17327 via
Markus Hennecke <markus-hennecke at markus-hennecke dot de>.
miod@ tested and ok
|
|
are checked in.
|
|
|
|
|
|
in non-obj dir.
|
|
syntax errors found by mandoc(1), also required to fix the mandoc build;
ok jmc@
|
