From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Edward Welbourne <eddy@opera.no>
Cc: 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 09:33:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.51.0212271636270.35773@naos.dbai.tuwien.ac.at> (raw)
In-Reply-To: <E18LgbC-00041r-00@whorl.intern.opera.no>
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). :-(
David, Jakub, in gcc/doc/install.texi we have
@item --with-cpu=@var{cpu}
Specify which cpu variant the
compiler should generate code for by default. This is currently
only supported on some ports, specifically arm, powerpc, and
SPARC@. If configure does not recognize the model name (e.g.@: arm700,
603e, or ultrasparc) you provide, please check the configure script
for a complete list of supported models.
but this doesn't seem to work; is there any possibility to find the
actual cpu variant for SPARCs, for example?
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.pfeifer.com/gerald/
next prev parent reply other threads:[~2002-12-27 15:40 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 [this message]
2002-12-27 11:08 ` Daniel Jacobowitz
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=Pine.BSF.4.51.0212271636270.35773@naos.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=davem@redhat.com \
--cc=eddy@opera.no \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jakub@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).