From: Jeffrey A Law <law@cygnus.com>
To: Nick Clifton <nickc@redhat.com>
Cc: cgd@sibyte.com, gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com
Subject: Re: RFA: Recording MIPS ABI selection in binaries
Date: Wed, 09 Aug 2000 06:55:00 -0000 [thread overview]
Message-ID: <22902.965829122@upchuck> (raw)
In-Reply-To: <200008090030.RAA19784@elmo.cygnus.com>
In message < 200008090030.RAA19784@elmo.cygnus.com >you write:
> Hi Chris,
>
> : as far as i'm concerned, there could have been better use of the
> : existing bits for ABIs (by enumeration, rather than flags)
>
> Indeed, but as you say we are stuck with legacy code which we need to
> carry on supporting, so I doubt if these flags will change any time
> soon.
Correct. For a number of platforms (such as many embedded MIPS chips) the
GNU tools defined the de-facto ABI.
> : Personally I'd like to see the existing flags rationalized to the
> : extent that they can be, and improved from there, rather than
> : perpetuate the existing morass and even make it worse by introducing a
> : mechanism that's not particularly scalable,
>
> The scheme is scalable. In fact it is more scalable than the existing
> scheme of using bits in the file header. The sections can have
> arbitrary names which can be used to encode pretty much anything.
Yup. Or we can put arbitrary contents into a non-loadable section to
record information we care about.
jeff
next prev parent reply other threads:[~2000-08-09 6:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-08 17:30 Nick Clifton
2000-08-09 6:55 ` Jeffrey A Law [this message]
[not found] ` <5tittb2pv3.fsf@highland.sibyte.com>
[not found] ` <3990B4BE.C2273617@cygnus.com>
[not found] ` <5thf8v2oh5.fsf@highland.sibyte.com>
[not found] ` <20000808190706.A27768@cygnus.com>
[not found] ` <39918757.8F2BD597@cygnus.com>
[not found] ` <5tg0oez7fp.fsf@highland.sibyte.com>
[not found] ` <20000809104623.D28802@cygnus.com>
2000-08-09 11:02 ` Michael Eager
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=22902.965829122@upchuck \
--to=law@cygnus.com \
--cc=cgd@sibyte.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=nickc@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