public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dirtyepic at gentoo dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/44046]  New: Intel Core i5 M520 CPU detected as atom with -march=native
Date: Sun, 09 May 2010 04:47:00 -0000	[thread overview]
Message-ID: <bug-44046-10406@http.gcc.gnu.org/bugzilla/> (raw)

We have a user that is getting illegal instruction errors while building
xulrunner.

/var/tmp/portage/net-libs/xulrunner-1.9.2.3-r1/work/mozilla-1.9.2/dist/bin/xpidl
-m typelib -w -I. -I../../dist/idl -e _xpidlgen/nsIConsoleListener.xpt -d
.deps/nsIConsoleListener.pp nsIConsoleListener.idl
make[4]: *** [_xpidlgen/nsIConsoleListener.xpt] Illegal instruction

It turns out that using -march=native with his Core i5 processor results in
-march=atom being used, specifically:

gcc version 4.5.0 (Gentoo 4.5.0 p1.0) 
COLLECT_GCC_OPTIONS= '-v' '-o' 'test'
 /usr/libexec/gcc/x86_64-pc-linux-gnu/4.5.0/cc1 -quiet -v test.c
-D_FORTIFY_SOURCE=2 -march=atom -mcx16 -msahf -maes -mpclmul -mpopcnt -msse4.2
--param l1-cache-size=32 --param l1-cache-line-size=64 --param
l2-cache-size=3072 -mtune=core2 -quiet -dumpbase test.c -auxbase test -version
-o /tmp/ccmAagyo.s

I believe the issue is that this processor doesn't support mmovbe, which
-march=atom enables (the error doesn't occur w/ -march=atom -mno-movbe).  Am I
right in guessing that it should instead be using -march=core2 + a bunch of -m
flags?

I will attach his /proc/cpuinfo.  Let me know what other info you need.

http://bugs.gentoo.org/317513


-- 
           Summary: Intel Core i5 M520 CPU detected as atom with -
                    march=native
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: dirtyepic at gentoo dot org
 GCC build triplet: x86_64-pc-linux-gnu
  GCC host triplet: x86_64-pc-linux-gnu
GCC target triplet: x86_64-pc-linux-gnu


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


             reply	other threads:[~2010-05-09  4:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-09  4:47 dirtyepic at gentoo dot org [this message]
2010-05-09  4:48 ` [Bug target/44046] " dirtyepic at gentoo dot org
2010-05-09  7:26 ` ubizjak at gmail dot com
2010-05-09 14:43 ` hjl dot tools at gmail dot com
2010-05-09 14:50 ` hjl at gcc dot gnu dot org
2010-05-09 14:53 ` hjl at gcc dot gnu dot org
2010-05-09 15:43 ` hjl dot tools at gmail dot com
2010-05-09 18:39 ` dirtyepic at gentoo dot org
2010-05-09 18:44 ` dirtyepic at gentoo dot org
2010-05-10  3:53 ` hjl dot tools at gmail dot com
2010-08-11 18:44 ` jakub at gcc dot gnu dot org
2010-08-11 19:12 ` hjl dot tools at gmail dot com
2010-08-11 20:31 ` hjl dot tools at gmail dot com

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=bug-44046-10406@http.gcc.gnu.org/bugzilla/ \
    --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).