public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tbm at cyrius dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/28915] New: [4.2 regression] ICE: tree check: expected class 'constant', have 'declaration' (var_decl) in build_vector, at tree.c:973 Date: Thu, 31 Aug 2006 12:24:00 -0000 [thread overview] Message-ID: <bug-28915-12387@http.gcc.gnu.org/bugzilla/> (raw) ICE/tree check with ftree-vectorize -O2: (sid)44:tbm@usurper: ~] x86_64-unknown-linux-gnu-gcc -ftree-vectorize -O2 -c xskat-xdial.c xskat-xdial.c: In function 'di_eigenertisch': xskat-xdial.c:9694: internal compiler error: tree check: expected class 'constant', have 'declaration' (var_decl) in build_vector, at tree.c:973 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. zsh: exit 1 x86_64-unknown-linux-gnu-gcc -ftree-vectorize -O2 -c xskat-xdial.c (sid)45:tbm@usurper: ~] x86_64-unknown-linux-gnu-gcc -ftree-vectorize -O1 -c xskat-xdial.c (sid)46:tbm@usurper: ~] x86_64-unknown-linux-gnu-gcc -O3 -c xskat-xdial.c (sid)47:tbm@usurper: ~] -- Summary: [4.2 regression] ICE: tree check: expected class 'constant', have 'declaration' (var_decl) in build_vector, at tree.c:973 Product: gcc Version: 4.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: tbm at cyrius dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28915
next reply other threads:[~2006-08-31 12:24 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-08-31 12:24 tbm at cyrius dot com [this message] 2006-08-31 12:30 ` [Bug tree-optimization/28915] " tbm at cyrius dot com 2006-08-31 16:13 ` pinskia at gcc dot gnu dot org 2006-08-31 19:15 ` uros at kss-loka dot si 2006-08-31 19:21 ` pinskia at gcc dot gnu dot org 2006-08-31 19:28 ` tbm at cyrius dot com 2006-09-01 6:27 ` pinskia at gcc dot gnu dot org 2006-09-01 22:32 ` mmitchel at gcc dot gnu dot org 2006-09-04 17:07 ` [Bug middle-end/28915] " pinskia at gcc dot gnu dot org 2006-09-05 4:20 ` pinskia at gcc dot gnu dot org 2006-09-06 6:30 ` pinskia at gcc dot gnu dot org 2006-09-06 6:33 ` pinskia at gcc dot gnu dot org 2006-09-06 15:27 ` roger at eyesopen dot com 2006-09-06 15:37 ` roger at eyesopen dot com 2006-09-09 6:44 ` jason at gcc dot gnu dot org 2006-09-10 0:48 ` jason at gcc dot gnu dot org 2006-09-22 4:36 ` rsandifo at gcc dot gnu dot org 2006-10-01 4:33 ` [Bug middle-end/28915] [4.1/4.2 " pinskia at gcc dot gnu dot org 2006-11-11 2:19 ` [Bug middle-end/28915] [4.1/4.2/4.3 " roger at eyesopen dot com 2006-11-13 8:16 ` jason at gcc dot gnu dot org 2006-11-13 8:19 ` jason at gcc dot gnu dot org 2006-11-13 14:41 ` [Bug middle-end/28915] [4.1 " pinskia at gcc dot gnu dot org 2006-11-13 18:53 ` hjl at gcc dot gnu dot org 2006-11-13 18:55 ` hjl at gcc dot gnu dot org 2006-11-13 23:31 ` jason at gcc dot gnu dot org 2006-11-13 23:42 ` jason at gcc dot gnu dot org 2006-11-14 9:30 ` jakub at gcc dot gnu dot org 2006-11-14 10:02 ` Andrew Pinski 2006-11-14 10:03 ` pinskia at gmail dot com 2006-12-01 1:09 ` chaoyingfu 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-28915-12387@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).