public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vsxo at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/24913] undocumented new CPU upgrade by -mpowerpc-gpopt overrides user-selected -mcpu= setting
Date: Thu, 17 Nov 2005 21:52:00 -0000 [thread overview]
Message-ID: <20051117215239.25761.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24913-11731@http.gcc.gnu.org/bugzilla/>
------- Comment #8 from vsxo at hotmail dot com 2005-11-17 21:52 -------
Of course, G4 and G5 are marketing names for *FreeScale* 74xx and IBM ppc970xx
cpus respectively. These are listed under the values that can be given to -mcpu
et al, but I can't find them in the list of cpus given under -mpowerpc-gpopt et
al.
> And order does not matter where it comes.
I give up. Are you contradicting what you just said earlier? In that case the
phrase I cited in #6 is wrong!
Gcc has so many convenience/t options that warn the programmer for doing unwise
things. Why not add a warning (or error) when requesting impossible cpu
features, or ones that are not available on the current host cpu?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24913
prev parent reply other threads:[~2005-11-17 21:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 16:47 [Bug target/24913] New: " gcc-bugzilla at gcc dot gnu dot org
2005-11-17 16:56 ` [Bug target/24913] " pinskia at gcc dot gnu dot org
2005-11-17 21:06 ` vsxo at hotmail dot com
2005-11-17 21:08 ` pinskia at gcc dot gnu dot org
2005-11-17 21:10 ` pinskia at gcc dot gnu dot org
2005-11-17 21:26 ` vsxo at hotmail dot com
2005-11-17 21:43 ` pinskia at gcc dot gnu dot org
2005-11-17 21:52 ` vsxo at hotmail dot com [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=20051117215239.25761.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).