public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rmansfield at qnx dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/40409] [LTO] ICE in expand_shift, at expmed.c:2263 Date: Thu, 17 Sep 2009 02:01:00 -0000 [thread overview] Message-ID: <20090917020129.1260.qmail@sourceware.org> (raw) In-Reply-To: <bug-40409-11406@http.gcc.gnu.org/bugzilla/> [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1983 bytes --] ------- Comment #8 from rmansfield at qnx dot com 2009-09-17 02:01 ------- I hit the PR41173 using an updated powerpc-unknown-linux-gnu configuration. The x86 ICE is still reproducible using a reduced testcase and a mismatch of optimizations levels. $ ./xgcc -v Using built-in specs. COLLECT_GCC=./xgcc Target: i686-pc-linux-gnu Configured with: ../configure --enable-languages=c++ --enable-lto --disable-bootstrap Thread model: posix gcc version 4.5.0 20090914 (experimental) [lto revision 151753] (lto merged with rev 150842) $ cat ice.i typedef long double _Complex _Lcomplex; _Lcomplex (casinhl)(_Lcomplex x) { long double re = creall(x); long double im = cimagl(x); const short errx = _LDtest(&re); const short erry = _LDtest(&im); long double u, v; if (errx == 2) if (erry == 2 || erry == 0) { const _Lcomplex w = csqrtl(_LCbuild(1.0L - im, re)); const _Lcomplex z = csqrtl(_LCbuild(1.0L + im, -re)); v = atan2l(im, creall(((w) * (z)))); } } $ ./xgcc -B. -O -flto -lto-test ice.i -c ice.i: In function âcasinhlâ: ice.i:3:20: warning: incompatible implicit declaration of built-in function âcreallâ ice.i:4:20: warning: incompatible implicit declaration of built-in function âcimaglâ ice.i:9:25: warning: incompatible implicit declaration of built-in function âcsqrtlâ ice.i:11:9: warning: incompatible implicit declaration of built-in function âatan2lâ $ ./xgcc -B. -shared -flto ice.o -flto In file included from ice.i:69:0, from :5: ice.i: In function âcasinhlâ: ice.i:11:32: internal compiler error: in expand_mult, at expmed.c:3253 Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. lto-wrapper: ././xgcc returned 1 exit status collect2: lto-wrapper returned 1 exit status Also, has -lto-test (mentioned in the LTO_Driver wiki page) been removed or was it ever added? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40409
next prev parent reply other threads:[~2009-09-17 2:01 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-06-10 21:26 [Bug lto/40409] New: " rmansfield at qnx dot com 2009-06-10 21:54 ` [Bug lto/40409] " rmansfield at gmail dot com 2009-06-11 2:58 ` rmansfield at qnx dot com 2009-06-11 3:01 ` rmansfield at qnx dot com 2009-07-09 5:40 ` bje at gcc dot gnu dot org 2009-09-16 13:29 ` rguenth at gcc dot gnu dot org 2009-09-16 13:59 ` rmansfield at qnx dot com 2009-09-16 14:02 ` rmansfield at qnx dot com 2009-09-17 2:01 ` rmansfield at qnx dot com [this message] 2009-09-17 9:44 ` rguenth at gcc dot gnu dot org 2009-09-28 18:57 ` rmansfield at qnx dot com 2009-10-14 19:49 ` rguenth at gcc dot gnu dot org 2009-12-11 16:40 ` [Bug lto/40409] [LTO] ICE in expand_shift, at expmed.c:2263, -O0 vs -Ox misses tree lowering phases rguenth at gcc dot gnu dot org 2010-01-10 21:38 ` rguenth at gcc dot gnu dot 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=20090917020129.1260.qmail@sourceware.org \ --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).