| Age | Commit message (Collapse) | Author |
|---|
|
|
|
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@
|
|
|
|
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.
|
|
plt, because it may need to be written to during initial relocation.
|
|
from elf32-ppc.c. The plt entry setup matches what can be found in Motorola's
SVR4/m88k binaries.
|
|
relocations to local symbols to be rewritten as relocations to the beginning
of the section they are in, plus an addend, as addend can't work for these
relocations, the way the got is set up. Inspired by tc-ppc.
|
|
- For DefaultSize instructions, don't guess a 'q' suffix if the instruction
doesn't support it.
- Corrections for x86_64 assembly.
ok miod@
|
|
ok miod@
|
|
a long time ago, because I had not realized symbol visibility required a
lot of shared library major bumps to avoid mixed binaries.
However, at the moment, none of the platforms using gcc 3 supports shared
libraries (this is being worked on), and the remaining gcc 2 platforms won't
support gcc 3 until switching from a.out to ELF, which makes the risk of mixing
visibility-unaware binaries with visibility-aware binaries moot.
Reminded by brad@.
|
|
#plt symbol modifiers, and produce the appropriate relocation types.
This allows as(1) to correctly assemble PIC code.
|
|
-fpic or -fPIC. Same for __PIE__ and __pie__; matches the behaviour of
the in-tree gcc 4.
|
|
Backported from a commit made after binutils 2.17 but before the GPLv3 switch.
ok miod@
|
|
with a test of ELF_TOOLCHAIN provided by bsd.own.mk.
No functional change.
|
|
|
|
compiler can be built on one particular m88k system and output code for another
with the proper options, but it only does half the job since there is too much
knowledge of the native toolchain embedded (at compile-time) in the compiler.
Building code for a different operating system and toolchain is what
cross-compiler are for.
Remove support for SDB debug information (only used by SVR3) and tdesc debug
information (only used by SVR4). The latter is questionable, but this helps
making the code less entangled.
Tell m88k.h to not rewrite almost all ASM_WHATEVER macros gratuitously on the
false pretense that `all m88k assemblers use the same syntax for pseudo-ops'.
This was already not true with SVR4, and is getting worse with our ELF
toolchain.
|
|
used for more than registers).
Convert all output of registers to asm_fprintf with %R.
Stop altering reg_names[] at runtime depending on the selected register prefix.
|
|
|
|
in the m88k backend; as a result, SHORT_ADDRESS_P() will always return 0,
therefore remove all code depending on it being nonzero.
|
|
-m{no-,}optimize-arg-area doesn't do anything either since the arg area has
been removed in gcc 2.95.
|
|
- add the frame pointer to EPILOGUE_USES when profiling
- when the initial stack adjustement is larger than 64KB and requires a
temporary register to be used, add a REG_FRAME_RELATED_EXPR of the original
computation (not constrained by the adjustement size) to the REG_NOTES of
the stack pointer adjustement sequence. Borrowed from alpha which has a
similar issue.
|
|
with the same value.
|
|
need to sync with upstream anymore) to make things a bit simpler and get
rid of unintended bitrotting.
This time:
- remove the small-data feature. It was only supported for COFF binaries
anyway. This allows us to stop providing TARGET_ASM_SELECT_SECTION and
use the default flavour, from which this backend had derived a bit in
addition to sdata support, so this is a good thing...
- remove the -midentify-version option
- remove the -mbig-pic option, it has been superseded by -fPIC since years
and was supposed to be removed `in a future version' since a long time
as well.
- remove the old MONITOR_GCC debug hooks.
|
|
|
|
Assembler supports a register prefix of `#' when configured for SVR4, and `%'
when configured for OpenBSD. Pseudo-ops do not need a leading dot, except
when configured for OpenBSD, allowing the `set' instruction to be recognized
correctly.
Based upon various unfinished or unreliable works, including smurph@'s early
work in 2003, my own attempts in 2004 and 2005, and Michael Kato's binutils
2.15 diff from 2005. Support for register prefixes, as well as fixing an
evil off-by-one in resolving 16-bit pc-relative relocations in ld (which would
only affect kernel .S files branching to global symbols), came as part of the
2012 work.
Not enabled yet (needs Makefile.bsd-wrapper, bfd/config.bfd and
gdb/configure.tgt updates to completely enable) so as not to disturb the
existing a.out toolchain builds; will hopefully be enabled very soon.
|
|
|
