Age | Commit message (Collapse) | Author |
|
use of awk. Slightly faster and works around an apparent namei or
buffer cache related bug on arm. Requested and OK deraadt@
|
|
|
|
okay fgs@, millert@
|
|
ok miod@
|
|
|
|
|
|
C++98, so clang++ rightfully complains about it when in C++98 mode (the
default).
Found while investigating the other clang issue, with helpful input from
espie@.
ok jsg@
|
|
without barfing about conflicting declarations.
Issue reported by Amit Kulkarni, investigated by matthew@ and kettenis@.
ok kettenis@
|
|
memory usage optimization, because this code is just bogus and causes
access-beyond-allocated-size SIGSEGV in the wild.
This is part of a larger diff (being worked on) backporting the removal of
``permanent_obstack'' completely from gcc, as done by the gcc folks in 3.x
after they came to their senses (or got tired of dissecting coredumps on
platforms with strong malloc implementations).
Only affects m68k, m88k and vax; collecting dust in the m88k tree, commit
triggered by sebastia@ via espie@ as this fixes the devel/gperf port on vax.
|
|
and change ASM_OUTPUT_ALIGNED_COMMON to output an explicit .align directive,
as gas will not compute it from the size (despite what comments elsewhere in
gcc code say).
This effectively makes __attribute__ ((aligned (N))) constructs work as
intended for .bss objects.
ok kettenis@
|
|
word boundaries, and enable the builtins.c `one-byte memcpy' workaround.
|
|
size 1 (the size being known at compile-time) into an inline mempcpy()
expansion, which will in turn expand into a byte load and store operation.
This expansion loses precious address alignment information at some point
(because everybody knows that you can read a byte from any address, right?),
and this loses bigtime on strict alignment platforms which lack the ability
to accesse bytes directly, such as alpha (unless compiling with -mbwx and
runnning on a BWX-capable cpu).
An example of such call with size 1 is lib/libkvm/kvm.c line 780.
|
|
different libstdc++.so majors. ok deraadt@
|
|
ok drahn@
|
|
ok kettenis@
|
|
Always install addr2line(1), objcopy(1), and readelf(1) manuals,
even on architectures with !ELF_TOOLCHAIN && !USING_NEW_BINUTILS.
Such architectures do not yet exist, but both symmetry
and fixing potential future issues early are good ideas.
ok jsing@
|
|
Patch gyped from nicm@'s and jasper@'s work on the gdb port.
|
|
Pointed out by sthen@, LGTM jsing@.
|
|
ok deraadt@
|
|
From brad. ok kettenis espie
|
|
ok espie@ millert@
|
|
architectures with !ELF_TOOLCHAIN && !USING_NEW_BINUTILS (like vax, m68k).
There is no need to reach around from usr.bin/Makefile into binutils;
we always descend into either binutils or binutils-2.17.
All is fine so far with binutils-2.17 since ia64 has USING_NEW_BINUTILS.
tested on vax and ok deraadt@
|
|
(passes -export-dynamic to ld(1))
ok drahn@ miod@
|
|
from brad; ok kettenis
|
|
|
|
testing by naddy, final diff from kettenis
|
|
|
|
Thanks Emeric Boit for reporting me this.
ok millert@ espie@
|
|
|
|
don't yet support. OK stsp@
|
|
No more exceptions even for binutils.
No more share/man in src/distrib/sets/lists/*/md.*
ok deraadt@
|
|
|
|
can be put between two set of pc-relative loaded data if we are compiling
PIC code; subsequent optimization passes are not as benign as what
find_barrier() expects, leading to dreaded ``pcrel too far'' as(1) errors.
|
|
handling thread safe and enables thread safety for libstdc++
- bump libstdc++ major
See faq/current.html for instructions on how to correctly build
userland for this change.
originally from kurt@, ok miod@
|
|
static binaries impossible.
|
|
it possible to build a cross compiler, and we don't really care about
exception handling until we have a kernel to run C++ code on anyway.
|
|
jasper@.
This omits the sizeof(pointer) tracking which is very difficult to
implement for gcc4 due to internal changes.
Thanks to landry@ for running through a ports bulk build and both
landry@ and jasper@ for fixing a few issues.
ok deraadt millert jasper
|
|
ok kettenis@
|
|
implemented in hardware anyway.
|
|
ok deraadt@
|
|
for a specific link to see if things worked out. Add a check for the very
last file in the MANIFEST, as well, since we are trying to spot a very
odd bug where symbolic links are not being created. Hopefully this will
help us diagnose it.
ok guenther millert
|
|
|
|
|
|
- restore local lynx.cfg settings [avsm]
- fix makefile races [espie]
- read/write result checking fixes to avoid unsigned comparisons vs -1 [krw]
- initialize all the InputFieldData members correctly [fgsch]
- fix socklen_t test to include <sys/types.h> [miod]
- fgets(3) returns NULL on error, not 0. No functional change [cloder]
ok krw@, tests by Simon Kuhnle and Martin Pieuchot
|
|
ok miod@, drahn@, kurt@
|
|
ok miod@
|
|
when the code was committed a few days ago. noticed by kettenis.
|
|
by actual make rules to enforce that order.
While here, correct the MANDIR which must no more contain "cat".
krw@ also confirms that this lets binutils build with -j.
|
|
commit, and deal with problems (if any) in tree.
Note that this adds the following functions. Ports with hacks might
need adjustments.
nexttoward(3), fma(3), nexttowardf(3), fmaf(3), acoshl(3), asinhl(3),
atanhl(3), coshl(3), sinhl(3), tanhl(3), expl(3), expm1l(3), logl(3),
log10l(3), log1pl(3), log2l(3), modfl(3), cbrtl(3), hypotl(3),
powl(3), erfl(3), erfcl(3), lgammal(3), tgammal(3), ceill(3),
floorl(3), lrintl(3), llrintl(3), roundl(3), lroundl(3), llroundl(3),
truncl(3), fmodl(3), remainderl(3), remquol(3), nextafterl(3),
nexttowardl(3), fmal(3).
With this commit, our library implements all functionality required
by C99. Documentation bits will follow.
|
|
NOTE: binutils-2.17 has not been tested on any archs. ok pirofti@
|