public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "spear at cse dot lehigh.edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/59463] Illegal Instruction: min() _GLIBCXX_USE_NOEXCEPT { return __FLT_MIN__; } Date: Wed, 11 Dec 2013 03:33:00 -0000 [thread overview] Message-ID: <bug-59463-4-VQ27NfBf0E@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59463-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59463 Mike Spear <spear at cse dot lehigh.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |spear at cse dot lehigh.edu --- Comment #1 from Mike Spear <spear at cse dot lehigh.edu> --- Bug appears to be triggered by the following simpler testcase: 1 - Put the following line in an empty file: #include <thread> 2 - Compile g++ foo.cc -std=c++11 Bug is appearing for following build from trunk (trunk is a few days old): g++ -v Using built-in specs. COLLECT_GCC=g++ COLLECT_LTO_WRAPPER=/proj/spear0/sw/libexec/gcc/x86_64-unknown-linux-gnu/4.9.0/lto-wrapper Target: x86_64-unknown-linux-gnu Configured with: /proj/spear1/admin/src/gcc_trunk/configure --prefix=/proj/spear0/sw --with-gmp=/proj/spear0/sw --with-mpc=/proj/spear0/sw --with-mpfr=/proj/spear0/sw --enable-languages=c,c++,lto --enable-lto --enable-multilib Thread model: posix gcc version 4.9.0 20131204 (experimental) (GCC) I'll update trunk and check if the bug remains.
next prev parent reply other threads:[~2013-12-11 3:33 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-10 23:46 [Bug c++/59463] New: " walkerboh1213 at gmail dot com 2013-12-11 3:33 ` spear at cse dot lehigh.edu [this message] 2013-12-11 15:07 ` [Bug c++/59463] " spear at cse dot lehigh.edu 2014-01-24 11:14 ` paolo.carlini at oracle 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-59463-4-VQ27NfBf0E@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: linkBe 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).