public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wilson at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/13032] New: CPP_CPU_ARCH_SPEC confusion
Date: Thu, 13 Nov 2003 01:50:00 -0000	[thread overview]
Message-ID: <20031113015047.13032.wilson@gcc.gnu.org> (raw)

CPP_CPU_ARCH_SPEC handles about 40 different -march= choices, but cc1 only
accepts about 9 of them.  The other 31 or so are cores which are not valid for
-march.  The fact that cc1 doesn't accept them makes it useless to have them in
cpp spec.

Also, I see that there is one arch armv6j which is in all_architectures, but not
CPP_CPU_ARCH_SPEC.

The specs for -march/-mcpu/-mtune should be checked for consistency against
all_architectures and all_cores.

-- 
           Summary: CPP_CPU_ARCH_SPEC confusion
           Product: gcc
           Version: 3.4
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: target
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: wilson at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org
GCC target triplet: arm-elf


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13032


             reply	other threads:[~2003-11-13  1:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-13  1:50 wilson at gcc dot gnu dot org [this message]
2003-11-13  5:16 ` [Bug target/13032] " pinskia at gcc dot gnu dot org
2004-01-01 21:28 ` pinskia at gcc dot gnu dot org
2005-02-11 10:47 ` rearnsha at gcc dot gnu dot org
2005-02-11 11:10 ` pinskia at gcc dot gnu dot org

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=20031113015047.13032.wilson@gcc.gnu.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).