public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dhazeghi at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/64364] New: gcc ICE on min() on Intel Sandy Bridge CPU if compiler built on Haswell
Date: Fri, 19 Dec 2014 18:39:00 -0000	[thread overview]
Message-ID: <bug-64364-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64364

            Bug ID: 64364
           Summary: gcc ICE on min() on Intel Sandy Bridge CPU if compiler
                    built on Haswell
           Product: gcc
           Version: 4.9.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dhazeghi at yahoo dot com

Created attachment 34302
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34302&action=edit
failing pre-processed source

I have a freshly bootstrapped gcc 4.9.2 that I built on CentOS 5.8 on an Intel
Haswell processor (4th gen Core i5).  I transferred the build over to an older
machine - same OS but running a Sandy Bridge processor (2nd gen Core i5).

Compiler crashes compiling 'min()' in limits on the SB machine, but of course
compiles fine on the Haswell one.

$ cat foo.cc 
#include <limits>

$ g++ -c ~/foo.cc 
In file included from /auto/home.nas02/dhazeghi/foo.cc:1:0:
/usr/local/gcc-4.9/include/c++/4.9.2/limits:1558:7: internal compiler error:
Illegal instruction
       min() _GLIBCXX_USE_NOEXCEPT { return __FLT_MIN__; }
       ^
0x9918ff crash_signal
        ../../gcc-4.9.2/gcc/toplev.c:337
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.


$ g++ -v
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/usr/local/gcc-4.9/libexec/gcc/x86_64-unknown-linux-gnu/4.9.2/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: ../gcc-4.9.2/configure --enable-languages=c,c++ --enable-lto
--prefix=/usr/local/gcc-4.9 --with-gmp=/usr/local/gcc-4.9
--with-mpfr=/usr/local/gcc-4.9 --with-mpc=/usr/local/gcc-4.9
--with-isl=/usr/local/gcc-4.9 --with-cloog=/usr/local/gcc-4.9
Thread model: posix
gcc version 4.9.2 (GCC)


             reply	other threads:[~2014-12-19 18:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-19 18:39 dhazeghi at yahoo dot com [this message]
2014-12-19 18:40 ` [Bug target/64364] " dhazeghi at yahoo dot com
2014-12-20 11:46 ` mikpelinux 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-64364-4@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).