From: Doug Evans <devans@cygnus.com>
To: bfd@cygnus.com
Subject: arm questions
Date: Thu, 15 Apr 1999 10:38:00 -0000 [thread overview]
Message-ID: <199904151738.KAA02138@canuck.cygnus.com.> (raw)
Two random questions.
1)
elfarm-oabi.c uses USE_RELA
elfarm-nabi.c uses USE_REL
That seems rather backwards, doesn't it?
I'd expect a new version of an abi to switch from USE_REL to USE_RELA,
but not the other way around.
[not that it can be changed, but rather ... why the switch?]
2)
Whats the R_ARM_THM_XPC22 reloc for?
next reply other threads:[~1999-04-15 10:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-15 10:38 Doug Evans [this message]
1999-04-15 11:01 ` Ian Lance Taylor
1999-04-15 11:31 ` Scott Bambrough
1999-04-15 11:47 ` Ian Lance Taylor
1999-04-15 13:29 ` H.J. Lu
1999-04-15 13:59 ` Ian Lance Taylor
1999-04-15 14:15 ` Mixing REL and RELA H.J. Lu
1999-04-15 14:21 ` Ian Lance Taylor
1999-04-15 14:28 ` H.J. Lu
1999-04-15 13:10 ` arm questions H.J. Lu
1999-04-15 13:45 ` Ian Lance Taylor
1999-04-15 13:36 ` Philip Blundell
1999-04-16 0:43 ` Lee Smith
1999-04-16 3:21 ` Toshi Morita
[not found] ` <3.0.5.32.19990416083918.0099b8a0.cygnus.local.bfd@mail1.bateman.arm.com>
1999-04-18 17:10 ` Doug Evans
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=199904151738.KAA02138@canuck.cygnus.com. \
--to=devans@cygnus.com \
--cc=bfd@cygnus.com \
/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).