public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mkgnu at mkgnu dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/31925] New: Internal compiler error in `store_bit_field', at expmed.c:277 Date: Mon, 14 May 2007 21:02:00 -0000 [thread overview] Message-ID: <bug-31925-6833@http.gcc.gnu.org/bugzilla/> (raw) Internal compiler error in `store_bit_field', at expmed.c:277. It seems that I've come across a case where compiling with gcc 2.95.4 (from the Debian package 2.95.4-22) using -O3 crashes, while compiling with no optimization does not crash. I will attach the .i file produced with -save-temps. I'm experiencing: $ gcc -O3 -c bm_kiss_double.cil.i ... ./bm_kiss_double.cil.c: In function `hcu_restore_frame_of___sgnl_v1': ./bm_kiss_double.cil.c:4273: Internal compiler error: ./bm_kiss_double.cil.c:4273: Internal compiler error in `store_bit_field', at expmed.c:277 Please submit a full bug report. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. I'm using the gcc 2.95.x series in a performance evaluation of various compilers. I did not try to reproduce with gcc 2.96 or gcc 2.97 (I don't see them being available for Debian). I confirmed that gcc 3.3.5 does not have this problem. -- Summary: Internal compiler error in `store_bit_field', at expmed.c:277 Product: gcc Version: 2.95.4 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: mkgnu at mkgnu dot net http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31925
next reply other threads:[~2007-05-14 21:02 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-05-14 21:02 mkgnu at mkgnu dot net [this message] 2007-05-14 21:03 ` [Bug tree-optimization/31925] " mkgnu at mkgnu dot net 2007-05-14 21:05 ` mkgnu at mkgnu dot net 2007-05-14 21:06 ` pinskia 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=bug-31925-6833@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).