Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: Always multi-arch the SPARC, dump sparclet?
Date: Mon, 25 Nov 2002 13:28:00 -0000	[thread overview]
Message-ID: <3DE295FE.4010805@redhat.com> (raw)
In-Reply-To: <20021125212132.GA21684@nevyn.them.org>

> On Mon, Nov 25, 2002 at 04:17:51PM -0500, Andrew Cagney wrote:
> 
>> Hello,
>> 
>> The SPARC target has a number of variants that don't yet build with 
>> multi-arch enabled (e.g., sparc-elf).
>> 
>> I'd like to propose that the switch simply be thrown and any 
>> non-multi-arch code be ripped out.  Acceptance criteria for such a 
>> change being simply `it still builds'.
>> 
>> This shouldn't affect things like GNU/Linux, which, I believe, do 
>> already build with multi-arch enabled.
>> 
>> This will, however, affect non-nulti-arch SPARC targets such as the 
>> sparclet potentially leading to breakage.
>> 
>> Thoughts?
> 
> 
> How's Solaris affected?  That's the only SPARC target that sees real
> use lately.
> 
> Not that it seems to work very well.

Shouldn't be affected (...):

$ grep 'define GDB_MULTI_ARCH' *
tm-linux.h:#define GDB_MULTI_ARCH GDB_MULTI_ARCH_PARTIAL
tm-nbsd.h:#define GDB_MULTI_ARCH GDB_MULTI_ARCH_PARTIAL
tm-sp64.h:#define GDB_MULTI_ARCH GDB_MULTI_ARCH_PARTIAL
tm-sun4sol2.h:#define GDB_MULTI_ARCH GDB_MULTI_ARCH_PARTIAL

Andrew



      reply	other threads:[~2002-11-25 21:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-25 13:17 Andrew Cagney
2002-11-25 13:21 ` Daniel Jacobowitz
2002-11-25 13:28   ` Andrew Cagney [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=3DE295FE.4010805@redhat.com \
    --to=ac131313@redhat.com \
    --cc=drow@mvista.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