Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eric Botcazou <ebotcazou@adacore.com>
To: David Miller <davem@davemloft.net>
Cc: gcc@gcc.gnu.org,  mark.kettenis@xs4all.nl,
	 brobecker@adacore.com,  gdb@sourceware.org
Subject: Re: DWARF register numbering discrepancy on SPARC between GCC and  GDB
Date: Thu, 22 Jan 2009 11:51:00 -0000	[thread overview]
Message-ID: <200901221251.06894.ebotcazou@adacore.com> (raw)
In-Reply-To: <20090121.121450.204277610.davem@davemloft.net>

> Ok, so it seems the fix is to reinstate the override in sol2.h,
> right?

This wouldn't change anything except for Solaris.  The fix is probably to wipe 
out the SVR4 definition (and consequently all definitions in config/sparc 
since the remaining ones will duplicate the default).

-- 
Eric Botcazou


      reply	other threads:[~2009-01-22 11:51 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
2009-01-21 20:14     ` David Miller
2009-01-22 11:51       ` Eric Botcazou [this message]

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=200901221251.06894.ebotcazou@adacore.com \
    --to=ebotcazou@adacore.com \
    --cc=brobecker@adacore.com \
    --cc=davem@davemloft.net \
    --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