From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: Andrew Cagney <ac131313@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: delete non-multi-arch SPARC code?
Date: Fri, 27 Jun 2003 20:57:00 -0000 [thread overview]
Message-ID: <20030627205719.GA7408@nevyn.them.org> (raw)
In-Reply-To: <3EFCAE75.8030901@redhat.com>
On Fri, Jun 27, 2003 at 01:52:05PM -0700, Michael Snyder wrote:
> Andrew Cagney wrote:
> >>Andrew Cagney wrote:
> >>Hello,
> >>
> >>The sparc codebase contains lots of #ifdef not-multi-arch code. Can
> >>anyone think of a reason to not simply delete it?
> >>
> >>I'm talking mainline, not 6.0 branch mind :-)
> >>
> >>Can you be more specific? I don't find anything like "ifdef
> >>not-multi-arch" in sparc-tdep.c.
> >
> >
> >It's all in config/sparc/tm*.h.
>
> Still not with you...
> cd gdb/config/sparc
> grep ifdef tm*.h
> <nothing>
Most of those macros override multi-arch ones just by being defined...
but:
#if defined (GDB_MULTI_ARCH) && (GDB_MULTI_ARCH > 0)
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2003-06-27 20:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-27 13:44 Andrew Cagney
2003-06-27 17:56 ` Michael Snyder
2003-06-27 18:56 ` Andrew Cagney
2003-06-27 20:52 ` Michael Snyder
2003-06-27 20:57 ` Daniel Jacobowitz [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=20030627205719.GA7408@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@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