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 tree-optimization/23509] New: [4.0 regression] ICE with ivopts Date: Sun, 21 Aug 2005 21:19:00 -0000 [thread overview] Message-ID: <20050821211705.23509.falk@debian.org> (raw) Test case: void block_diffs_C(int *ss, int *new, int ns, int *newp) { int x, y, s = 0; for (x = 0; x < 8; x++) { newp = new++; for (y = 0; y < 4; y++) s += *newp++; *ss = s; } } With GNU C version 4.1.0 20050810 (experimental) (alphaev68-unknown-linux-gnu) at -O3, I get: 363.c: In function 'block_diffs_C': 363.c:1: internal compiler error: tree check: expected ssa_name, have error_mark in verify_ssa, at tree-ssa.c:746 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. -fno-ivopts makes it go away. -- Summary: [4.0 regression] ICE with ivopts Product: gcc Version: 4.1.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P2 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: falk at debian dot org CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23509
next reply other threads:[~2005-08-21 21:17 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-08-21 21:19 falk at debian dot org [this message] 2005-08-21 22:20 ` [Bug tree-optimization/23509] [4.1 " pinskia at gcc dot gnu dot org 2005-08-24 12:35 ` rakdver at gcc dot gnu dot org 2005-08-27 12:20 ` rakdver at gcc dot gnu dot org 2005-08-29 19:29 ` pinskia at gcc dot gnu dot org 2005-08-31 23:10 ` qrczak at knm dot org dot pl 2005-09-03 20:16 ` mec at google dot com 2005-09-09 16:17 ` cvs-commit at gcc dot gnu dot org 2005-09-09 17:59 ` 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=20050821211705.23509.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).