public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vincenzo.innocente at cern dot ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/44897] -flto + ipa-sra misoptimize sqlite (non-plugin only)
Date: Thu, 19 May 2011 08:42:00 -0000 [thread overview]
Message-ID: <bug-44897-4-ZDmlNTtcu8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-44897-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44897
vincenzo Innocente <vincenzo.innocente at cern dot ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vincenzo.innocente at cern
| |dot ch
--- Comment #16 from vincenzo Innocente <vincenzo.innocente at cern dot ch> 2011-05-19 08:12:20 UTC ---
I'm getting a whole bunch of
lto1: internal compiler error: Floating point exception
using
g++ -v
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/x86_64-unknown-linux-gnu/4.6.1/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: ./configure -enable-gold=yes --enable-lto --with-fpmath=avx
--with-build-config=bootstrap-lto --with-gmp-lib=/usr/local/lib64
--with-mpfr-lib=/usr/local/lib64 -with-mpc-lib=/usr/local/lib64
Thread model: posix
gcc version 4.6.1 20110513 (prerelease) (GCC)
before submitting a new bug report I would like to know if the patch by Honza
quoted below is already in it or still pending
next prev parent reply other threads:[~2011-05-19 8:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-44897-4@http.gcc.gnu.org/bugzilla/>
2010-10-02 14:13 ` [Bug tree-optimization/44897] -fwhopr + ipa-sra misoptimize sqlite hubicka at gcc dot gnu.org
2010-12-15 1:51 ` hubicka at gcc dot gnu.org
2011-01-10 15:29 ` hubicka at gcc dot gnu.org
2011-01-10 16:40 ` [Bug tree-optimization/44897] -flto + ipa-sra misoptimize sqlite (non-plugin only) hubicka at gcc dot gnu.org
2011-01-10 22:34 ` hubicka at gcc dot gnu.org
2011-03-10 16:07 ` markus at trippelsdorf dot de
2011-03-10 16:26 ` hubicka at ucw dot cz
2011-03-10 18:39 ` markus at trippelsdorf dot de
2011-03-10 19:14 ` markus at trippelsdorf dot de
2011-04-03 9:00 ` hubicka at gcc dot gnu.org
2011-05-19 8:42 ` vincenzo.innocente at cern dot ch [this message]
2011-05-19 9:24 ` hubicka at ucw dot cz
2011-05-25 12:04 ` hubicka at gcc dot gnu.org
2011-05-25 12:27 ` hubicka at gcc dot gnu.org
2011-06-02 1:13 ` hubicka at gcc dot gnu.org
2011-06-02 16:11 ` markus at trippelsdorf dot de
2011-06-02 21:52 ` hubicka at gcc dot gnu.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=bug-44897-4-ZDmlNTtcu8@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).