From: Jason R Thorpe <thorpej@wasabisystems.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH/RFA] Add OS/ABI infrastructure to SuperH target
Date: Tue, 07 May 2002 09:29:00 -0000 [thread overview]
Message-ID: <20020507092902.K503@dr-evil.shagadelic.org> (raw)
In-Reply-To: <15575.61481.423043.405803@localhost.redhat.com>; from ezannoni@redhat.com on Tue, May 07, 2002 at 11:18:01AM -0400
On Tue, May 07, 2002 at 11:18:01AM -0400, Elena Zannoni wrote:
> The ABI is unknown for all the architectures except for sh5 where it
> is set to either 32 or 64 depending on the bfd. I am not saying this
> is completely correct, note.
Hm. Well, I'm happy to change the OS/ABI stuff to "sh_osabi". Might be
more appropriate, anyway (eventually, I want to make the osabi stuff generic
and plop it into a common file).
> Is there any chance you could take a look at the sh5 patch I posted a
> while back, and see if/how your patch integrates (in principle, at least)?
> The patch is here:
> http://sources.redhat.com/ml/gdb-patches/2002-02/msg00218.html
Yah, I'll peek at it in a couple of hours.
> About your patch, I would prefer if the switch on the os_number used
> names instead of 0,1,2, is this possible? Same for this line:
> + if (elfosabi == 0)
Hm, are there manifest constants defined in our header files for the
GNU OS numbers? Heh, if not, I guess it wouldn't be hard to add them :-)
Anyway, I'll tweak this in a bit and re-post.
--
-- Jason R. Thorpe <thorpej@wasabisystems.com>
next prev parent reply other threads:[~2002-05-07 16:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-07 1:45 Jason R Thorpe
2002-05-07 8:18 ` Elena Zannoni
2002-05-07 9:29 ` Jason R Thorpe [this message]
2002-05-07 13:31 ` Jason R Thorpe
2002-05-07 13:35 ` Elena Zannoni
2002-05-08 7:54 ` Jason R Thorpe
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=20020507092902.K503@dr-evil.shagadelic.org \
--to=thorpej@wasabisystems.com \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@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