| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
config.sh.OpenBSD are the only local changes.
|
|
update.
|
|
it should never do so. This can cause global constructors and
destructors to not be executed at run-time, resulting in crashes
and other strange behaviour.
From FreeBSD: http://svnweb.freebsd.org/base?view=revision&revision=244600
This unbreaks building chromium with binutils-2.17
ok miod@, sthen@
|
|
|
|
|
|
|
|
.openbsd.randomdata so that ld can cleanly suppress the program header
slot for PT_OPENBSD_RANDOMIZE when it isn't needed...such as for /boot.
The symbols probably can and should be removed completely, but until that
can be tested this at least unblocks the 2.17 transition
ok miod@ matthew@
|
|
mprotect these sections RO as soon as they have been relocated; similar to
what the W^X changes in 2.15 did.
|
|
ok millert
|
|
eplace a comment asking for a particular order to build stuff in
by actual make rules to enforce that order.
While here, correct the MANDIR which must no more contain "cat".
|
|
2.15 directory, but only to build gdb.
ok deraadt@ espie@
|
|
to binutils 2.15. Do not preserve brain cells. Do not collect $20,000.
Do not pass go. Do not keep your sanity.
|
|
elsewhere, and the latter only installs useless documentation about how
configure scripts waste your time and resources, and the awfully ugly GNU
coding standards which waste whitespace.
|
|
For more information please refer to: http://code.activestate.com/lists/perl5-porters/191311/
ok millert@
|
|
|
|
|
|
ok miod@
|
|
epilogue_begin.
Backported from binutils 2.17.
ok miod@
|
|
- only the binutils package (no gdb here)
- don't import libiberty and texinfo, they are elsewhere
- remove all .info* generated files
|
|
|
|
Backported from binutils 2.17.
ok miod@
|
|
|
|
|
|
definition forces variable-sized types to always be passed by reference.
Update the varargs code to cope with this.
gcc.c-torture/execute/20020412-1 finally passes.
|
|
RTL generation in SETUP_INCOMING_VARARGS(...,0).
This means we no longer need to explicitely allocate room on the stack for
the saved register area (which we did in EXPAND_BUILTIN_SAVEREGS). We were
returning the correct size in SETUP_INCOMING_VARARGS's ``pretend_size''
argument anyway, causing this space to be allocated twice.
This change should also allow for the stack protector to be reenabled (after
more testing).
|
|
warnings caused by a maze of twisty little macros in the process, which appeared
when m88k ELF support was added to the toolchain.
|
|
configuration, the wrong life analysis bug leading to removal of half the
code of ISDOT() in libc's fts.c fts_stat() no longer triggers.
|
|
code on m68k. In pure gcc tradition, even though the issue has been
acknowledged as a bug introduced around gcc 2.5, it was considered as
`not a regression' with subtle semantics tricks, and only fixed in 3.4.x
although the fix was available for a long time.
Although this changes an MI file, this chunk actually removes a no longer
used function which was only ever used on m68k.
|
|
considerations.
|
|
considerations.
|
|
command line. While technically -static only controls whether we link against
static libraries, people expect that doing so produces a fully static binary.
tested by sthen@
ok pascal@, miod@
|
|
ok miod@
|
|
and i386.
pointed out by miod@
|
|
i386.
ok pascal@, miod@
|
|
|
|
in the compiler. Not investigated further since the compiler will hopefully
get an upgrade soon.
|
|
32-bit boundaries, function return values being in %a0 instead of %d0 if they
are declared as pointers, and in fp registers if they are floating point types).
Compiler configuration bits (including a few m68k PIC code generation fixes)
borrowed from NetBSD.
|
|
And there was much rejoicing.
|
|
existing behaviour of wrapping big PIC addresses in `unspec's to prevent the
cse pass from modifying them.
However, instead of building the unspec ourselves in the C code, rely upon
explicitely named define_insn() constructs in the .md description.
Then, fix the ambiguity this introduces between the locate1 and movsi_high_pic
insns by defining symbolic constants as the unspec selector, and using them,
instead of 0.
|
|
error test. The logic was correct, I was tricked by bogus compiler generated
assembly.
|
|
be resolved at link time, such as when linking a binary from objects which
have been compiled PIC (one such case being perl's miniperl).
While there, borrow the check and error message for GOT_16[HL] with nonzero
addend (which can only happen with badly crafted .s files and do not behave
like one may naively think they do) from elf32-ppc.
|
|
SYMBOL_REF or LABEL_REF, when deciding to put #got_rel relocations. This allows
(symbol + constant) to be correctly relocated when building PIC.
|
|
caused the code responsible for adding the proper #got_rel relocation to the
second part of the PIC symbol address load.
Instead of using an UNSPEC for that purpose (which violates assumptions made
by the MI code anyway), check for the the second operand of a LO_SUM being
either a SYMBOL_REF or a LABEL_REF, to output the #got_rel relocation, and
drop the remaining bits of UNSPEC handling.
|
|
|
|
|
|
PIC base register, it case it turns out to not be necessary. This should not
be needed because this sequence is only generated if
current_function_uses_pic_offset_table is set, but it can't hurt to expect the
worse (from rs6000).
legitimize_address(): do not coerce the address using (unspec:SI gen_rtvec() ),
but rather use it unmodified, in the -fPIC case. This lets libstdc++.so build
(and probably anything else being compiled with -fPIC rather than -fpic).
|
|
the fully static one. Update the compiler specs to allow for dynamic linking
of libraries and binaries.
|
