From: "Frank Ch. Eigler" <fche@redhat.com>
To: Aurelien Buhrig <aurelien.buhrig.gcc@gmail.com>
Cc: cgen <cgen@sourceware.org>
Subject: Re: Complex relocs and RELOC_IMPLIES_OVERFLOW attr
Date: Mon, 12 Sep 2011 16:38:00 -0000 [thread overview]
Message-ID: <20110912163821.GD1596@redhat.com> (raw)
In-Reply-To: <CAJ-J9_Uua-MVWnJ5cZTFWyvGsTJAzCvxeA4D9budRFub_qy7Yw@mail.gmail.com>
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
prev parent reply other threads:[~2011-09-12 16:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-08 8:31 Aurelien Buhrig
2011-09-12 16:38 ` Frank Ch. Eigler [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110912163821.GD1596@redhat.com \
--to=fche@redhat.com \
--cc=aurelien.buhrig.gcc@gmail.com \
--cc=cgen@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).