Age | Commit message (Collapse) | Author |
|
Reduces drastically the number of warnings one gets when compiling old
library with newer preprocessor.
tests and okay miod@
|
|
from a pcb when debugging a kernel. Make sure we provide the matching stack
pointer too to avoid duplicating the first frame. Makes "target kvm" much
more useful on powerpc.
|
|
#include <math.h> and expect the C99 macros in that file to be available in
the global namespace. This include was removed upstream some time after
the libstdc++ we use was released.
ok naddy@
|
|
more default stuff.
as discussed with kettenis, landry, and others.
Allow some gnome stuff (gtk2mm) to compile, and does not break source
compatibility with the standard (well, not more than gcc 4.2 does)
|
|
|
|
functions: acos, asin, atan, atan2, cos, cosh, exp, fabs, floor,
log, log10, sqrt, sin, sinh, tan, tanh
fixes quite some ports
tested by brad@. no objections millert@
|
|
-fpie & -fPIE which are similar to -fpic & -fPIC except that the resulting
objects can not be used in shared libraries due to an additional
optimization for pie. This also adds the -pie link flag which produces a
pie executable given pic or pie objects. Combining -pie with -static is
currently disabled. The only gcc3 arch that doesn't support pie at moment
is arm due to binutils relocation bugs.
ok kettenis@
|
|
<ezannoni at redhat dot com> pie branch in gdb cvs, less extraneous
parts and with some bug fixes. Debugging w/core files for pie programs
isn't working yet since AUXV data isn't included in our core files at
the moment.
feedback and ok kettenis@
|
|
|
|
construct, so that it is still written in rtl statements, and part of
it can be put in a delay slot. And the way it's written now, it does not
create bogus uninitialized warnings.
|
|
the two SImode subregs of the DImode destination operand, this confuses
the register life analysis and causes gcc to emit wrong warning about
values not being initialized.
Unfortunately, the fallback logic infers a worse sequence (mov + cmp against
zero + ext of the cmp signedness bit, instead of mov + ext of the sign bit),
which wastes an instruction and a register.
This is hopefully a temporary measure until a nonconfusing flavour of the
fast expansion is devised (preferrably one which does not expose the
optimize_reg_copy_3 big-endian bug as well).
|
|
PR #5033; gcc 2.95 will need a similar fix (soon).
|
|
okay kettenis@, miod@, otto@
|
|
installperl to prevent man page installation of the perl man pages.
|
|
deraadt@
|
|
fixed. tested by me and naddy@. ok theo
|
|
|
|
existing submit.mc to the stock version. Closes PR 4951.
OK sthen@ martynas@
|
|
requested by jmc@
|
|
ok sthen@, xsa@, deraadt@
|
|
This time, add a comment describing why it is there.
|
|
|
|
2008-04-27 (2.8.7dev.9)
* pass a newline after the start of PRE-section in HTGopher.c to force
the first newline between records to be seen and cause the lines to
split (report by Ciprian Dorin Craciun) -TD
|
|
We cannot mkdep DynaLoader.c since it is a generated file.
|
|
makewhatis info for the perl man pages now matches the pages themselves.
|
|
|
|
|
|
|
|
|
|
|
|
ok kurt@
|
|
ok joris@
|
|
|
|
Sendmail folks have been notified and are fixing this for
the next release.
|
|
be able to link against libc_pic.a anyway.
|
|
|
|
__udivti3, because MUST_PASS_IN_STACK always returned 1 on amd64;
pr#5780
reported by Simon Kuhnle
tested by Simon Kuhnle, sthen@, brad@
double-checked & tweak from miod@
ok sthen@, brad@
|
|
They really are just a way to share common code between gdb and binutils
(which in the GNU world are seperate packages). The developers (and I'm
one of them) make absolutely no effert to maintain a stable API/ABI.
If ports people really need libbfd or libopcodes, they should just
package a suitable version.
ok weingart@, deraadt@
|
|
noticed by ajacoutot
|
|
ok millert@
|
|
derefs in at least one case and I do not have time to debug this before the
release.
ok deraadt@
|
|
compile current libm. ok martynas@
|
|
can use these functions in C++.
ok millert@. also looked over by espie@, fgsch@.
|
|
|
|
|
|
|
|
uses -1, 0 and 1 which is one value too much for boolean.
Ok krw@, millert@
|
|
|
|
as has been done for the __sentinel__ attribute, since all toolchains support
it.
|
|
|