public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "falk at debian dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug optimization/12628] New: [3.4 regression] Segfault with -fno-expensive-optimizations -fno-rerun-loop-opt Date: Wed, 15 Oct 2003 22:19:00 -0000 [thread overview] Message-ID: <20031015221857.12628.falk@debian.org> (raw) PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12628 Summary: [3.4 regression] Segfault with -fno-expensive- optimizations -fno-rerun-loop-opt Product: gcc Version: 3.4 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: critical Priority: P2 Component: optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: falk at debian dot org CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: alphaev68-unknown-linux-gnu GCC host triplet: alphaev68-unknown-linux-gnu GCC target triplet: alphaev68-unknown-linux-gnu GNU C version 3.4 20031012 (experimental) (alphaev68-unknown-linux-gnu) falk@juist:/tmp% cat min2.c int outbuf[100]; int outcnt; int bi_buf; void send_bits(void) { bi_buf = 0; outbuf[outcnt++] = 8; outbuf[outcnt++] = 8; if (outcnt) bi_buf = 1; } falk@juist:/tmp% gcc -O2 -c -fno-expensive-optimizations -fno-rerun-loop-opt min2.c min2.c: In function `send_bits': min2.c:11: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. Also happens on tree-ssa.
next reply other threads:[~2003-10-15 22:19 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-10-15 22:19 falk at debian dot org [this message] 2003-10-18 18:44 ` [Bug optimization/12628] " pinskia at gcc dot gnu dot org 2003-12-01 2:55 ` pinskia at gcc dot gnu dot org 2003-12-01 2:55 ` pinskia at gcc dot gnu dot org 2003-12-01 21:17 ` cvs-commit at gcc dot gnu dot org 2003-12-01 23:07 ` 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=20031015221857.12628.falk@debian.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).