From: "Kris Warkentin" <kewarken@qnx.com>
To: <Richard.Earnshaw@arm.com>
Cc: <Richard.Earnshaw@arm.com>,
"Gdb@Sources.Redhat.Com" <gdb@sources.redhat.com>
Subject: Re: Elf OS ABI Number
Date: Thu, 12 Jun 2003 14:46:00 -0000 [thread overview]
Message-ID: <014101c330f1$748af060$0202040a@catdog> (raw)
In-Reply-To: <200306121427.h5CERJR20619@pc960.cambridge.arm.com>
> > Actually, we do have a few things that are different - QNX specific
> > relocations, different MIPS ABI, etc. It seems like having the ABI
number
> > can do no harm but can certainly be useful.
>
> As I said before, new relocations is a valid reason for an OS_ABI field
> change. However, an ABI change (calling standard) is not -- it doesn't
> change the meaning of the ELF container, which is what the field is about.
> The harm is that a linker is supposed to reject an OS_ABI field setting
> it doesn't understand.
Yes, I just learned that yesterday. I'm beginning to lean back towards the
.note section. I'm beginning to win hearts and minds on this end as well.
> Is there a good reason why you've invented your own relocs? If the
> processor vendor (who generally own the reloc space allocation for their
> processor) where to allocate a reloc that conflicts with your usage at a
> later date you might have a major problem on your hands.
We do some weird stuff for execute in place and various kernel stuff. I
don't understand the details particularily well but we have to use our own
linker on certain startup code and such. Probably doesn't affect much else.
> > The problem with things like
> > .note sections for identifying binaries is that a stripped binary can no
> > longer be identified.
>
> No, .note sections are not symbols, so are not removed by strip. The only
> way to remove a .note section is to use objcopy and tell it not to copy
> that section.
Well, I should have been more clear on that. When we put binaries into an
image, they are REALLY stripped - no sections at all. They are also
pre-relocated so that they can be run directly off of flash or other memory
type media. Ultimately, you can't really debug these anyway (bfd won't even
recognize them properly) so it doesn't really matter that much. If you have
a version with debug info that gdb can load, you can debug them properly
anyway though so it's only a minor quibble.
cheers,
Kris
next prev parent reply other threads:[~2003-06-12 14:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 14:00 Kris Warkentin
2003-06-11 14:23 ` Andrew Cagney
2003-06-11 16:44 ` Richard Earnshaw
2003-06-11 17:20 ` Kris Warkentin
2003-06-12 14:27 ` Richard Earnshaw
2003-06-12 14:46 ` Kris Warkentin [this message]
2003-06-12 14:50 ` Kris Warkentin
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='014101c330f1$748af060$0202040a@catdog' \
--to=kewarken@qnx.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gdb@sources.redhat.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