From: Daniel Jacobowitz <drow@mvista.com>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: Edward Welbourne <eddy@opera.no>,
gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org,
"David S. Miller" <davem@redhat.com>,
Jakub Jelinek <jakub@redhat.com>
Subject: Re: PATCH for Re: installation instructions; glitchlet
Date: Fri, 27 Dec 2002 11:08:00 -0000 [thread overview]
Message-ID: <20021227163001.GA2948@nevyn.them.org> (raw)
In-Reply-To: <Pine.BSF.4.51.0212271636270.35773@naos.dbai.tuwien.ac.at>
On Fri, Dec 27, 2002 at 04:40:33PM +0100, Gerald Pfeifer wrote:
> On Tue, 10 Dec 2002, Edward Welbourne wrote:
> >> I have just committed the following patch to mainline, so that it
> >> will be part of GCC 3.3 (and later).
> > good. I note, however, that you still refer the reader back to the
> > configure script for `a complete list of supported models', though I
> > couldn't find such a list in the configure script; in particular, I
> > grepped for at least one of the names given in the `e.g.' and it
> > didn't show up. How does one find the list ?
>
> Sorry, I don't know (respectively, I couldn't find it). :-(
You can find it in config.gcc, It's around line 2665. However it only
works for a couple of platforms. Looks like ARM, PowerPC, SPARC, and
v850. For SPARC the list is:
case ".$with_cpu" in
.supersparc | .hypersparc | .ultrasparc | .v7 | .v8 | .v9)
[My patch to use --with-cpu across all architectures was never
reviewed and is now out of date again. I'll resubmit it when I feel
like being ignored next.]
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-12-27 16:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-02 3:43 Edward Welbourne
2002-12-06 15:50 ` PATCH for " Gerald Pfeifer
2002-12-10 1:32 ` Edward Welbourne
2002-12-27 9:33 ` Gerald Pfeifer
2002-12-27 11:08 ` Daniel Jacobowitz [this message]
2002-12-31 3:42 ` Gerald Pfeifer
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=20021227163001.GA2948@nevyn.them.org \
--to=drow@mvista.com \
--cc=davem@redhat.com \
--cc=eddy@opera.no \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=pfeifer@dbai.tuwien.ac.at \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).