public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/13032] New: CPP_CPU_ARCH_SPEC confusion
@ 2003-11-13  1:50 wilson at gcc dot gnu dot org
  2003-11-13  5:16 ` [Bug target/13032] " pinskia at gcc dot gnu dot org
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: wilson at gcc dot gnu dot org @ 2003-11-13  1:50 UTC (permalink / raw)
  To: gcc-bugs

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


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2005-02-11  0:37 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-11-13  1:50 [Bug target/13032] New: CPP_CPU_ARCH_SPEC confusion wilson at gcc dot gnu dot org
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

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).