From: Eric Botcazou <ebotcazou@adacore.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gcc@gcc.gnu.org, brobecker@adacore.com, gdb@sourceware.org
Subject: Re: DWARF register numbering discrepancy on SPARC between GCC and GDB
Date: Wed, 21 Jan 2009 14:22:00 -0000 [thread overview]
Message-ID: <200901211522.19829.ebotcazou@adacore.com> (raw)
In-Reply-To: <200901211237.n0LCb2wB017368@brahms.sibelius.xs4all.nl>
> Obviously the GCC folks broke backwards compatibility with themselves.
> So unless we find evidence that contradicts the wiki page you cite, I
> think GCC needs to be fixed.
Yes, the SVR4 definition used to be masked by that of the sol2.h file on
Solaris and is not anymore. But the SVR4 definition is the one used for
the various BSD variants.
> OpenBSD and Linux are fine; they use 32-63 to number f0-f31.
Linux is fine, OpenBSD is not, at least in the FSF tree.
--
Eric Botcazou
next prev parent reply other threads:[~2009-01-21 14:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 11:09 Joel Brobecker
2009-01-21 12:00 ` Rainer Orth
2009-01-21 12:37 ` Mark Kettenis
2009-01-21 14:22 ` Eric Botcazou [this message]
2009-01-21 20:14 ` David Miller
2009-01-22 11:51 ` Eric Botcazou
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=200901211522.19829.ebotcazou@adacore.com \
--to=ebotcazou@adacore.com \
--cc=brobecker@adacore.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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