* Complex relocs and RELOC_IMPLIES_OVERFLOW attr
@ 2011-09-08 8:31 Aurelien Buhrig
2011-09-12 16:38 ` Frank Ch. Eigler
0 siblings, 1 reply; 2+ messages in thread
From: Aurelien Buhrig @ 2011-09-08 8:31 UTC (permalink / raw)
To: cgen
Hi,
I've defined OBJ_COMPLEX_RELC macro to enable complex relocations
(from mep port) in my cpu port which seems to work well.
But for gas to compile, the RELOC_IMPLIES_OVERFLOW attr must be
defined in the cpu file (only in mep-core.cpu till now).
Shouldn't this attr be a general attribute rather than a target
dependant attr, or are the complex relocs in cgen a very experimental
feature we shouldn't use ?
Thanks,
Aurélien
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Complex relocs and RELOC_IMPLIES_OVERFLOW attr
2011-09-08 8:31 Complex relocs and RELOC_IMPLIES_OVERFLOW attr Aurelien Buhrig
@ 2011-09-12 16:38 ` Frank Ch. Eigler
0 siblings, 0 replies; 2+ messages in thread
From: Frank Ch. Eigler @ 2011-09-12 16:38 UTC (permalink / raw)
To: Aurelien Buhrig; +Cc: cgen
Hi -
> I've defined OBJ_COMPLEX_RELC macro to enable complex relocations
> (from mep port) in my cpu port which seems to work well.
> But for gas to compile, the RELOC_IMPLIES_OVERFLOW attr must be
> defined in the cpu file (only in mep-core.cpu till now). [...]
I can't explain why it's done in the present way (using a generated
symbol rather than a hard-coded one); maybe because cgen .cpu-level
symbols cannot normally refer to normal C ones.
> are the complex relocs in cgen a very experimental feature we
> shouldn't use ?
They are done, working as far as I know. However, they are not used
much: their capability is not needed or just not appreciated widely.
- FChE
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2011-09-12 16:38 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-09-08 8:31 Complex relocs and RELOC_IMPLIES_OVERFLOW attr Aurelien Buhrig
2011-09-12 16:38 ` Frank Ch. Eigler
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).