public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aldot at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/29788] [Optimization] ICE in var_ann, at tree-flow-inline.h:130 Date: Thu, 09 Nov 2006 23:42:00 -0000 [thread overview] Message-ID: <20061109234158.11673.qmail@sourceware.org> (raw) In-Reply-To: <bug-29788-6318@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from aldot at gcc dot gnu dot org 2006-11-09 23:41 ------- Created an attachment (id=12583) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12583&action=view) slightly smaller testcase Confirmed. Works on x86_64, ICEs on i686. Also ICEs with gcc version 4.2.0 20061018 (experimental) 4.3.0 20061109 (experimental) gives Breakpoint 1, var_ann (t=0xa7d911b8) at ../../../src/gcc-4.3/gcc/tree-flow-inline.h:130 130 gcc_assert (!t->common.ann || t->common.ann->common.type == VAR_ANN); (gdb) p *t->common.ann $9 = {common = {type = VAR_ANN, aux = 0x0, value_handle = 0x0}, vdecl = {common = { type = VAR_ANN, aux = 0x0, value_handle = 0x0}, out_of_ssa_tag = 0, root_var_processed = 0, is_aliased = 1, used = 1, need_phi_state = NEED_PHI_STATE_MAYBE, in_vuse_list = 0, in_v_may_def_list = 0, is_heapvar = 0, symbol_mem_tag = 0x0, may_aliases = 0x0, partition = 0, root_index = 0, current_def = 0xa7b583f0, subvars = 0x0, escape_mask = 136}, fdecl = {common = {type = VAR_ANN, aux = 0x0, value_handle = 0x0}, reference_vars_info = 0x2c}, stmt = {common = {type = VAR_ANN, aux = 0x0, value_handle = 0x0}, modified = 0, has_volatile_ops = 0, makes_clobbering_call = 1, bb = 0x0, operands = {def_ops = 0x0, use_ops = 0x0, maydef_ops = 0x0, vuse_ops = 0xa7b583f0, mustdef_ops = 0x0}, addresses_taken = 0x88, uid = 1, histograms = 0x0}} (gdb) c Continuing. ./gfcbug4x-pr29788.f90: In function 'try_fit': ./gfcbug4x-pr29788.f90:31: internal compiler error: in var_ann, at tree-flow-inline.h:130 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29788
next prev parent reply other threads:[~2006-11-09 23:42 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-11-09 21:26 [Bug fortran/29788] New: " anlauf at gmx dot de 2006-11-09 21:27 ` [Bug fortran/29788] " anlauf at gmx dot de 2006-11-09 23:42 ` aldot at gcc dot gnu dot org [this message] 2006-11-09 23:42 ` [Bug tree-optimization/29788] " aldot at gcc dot gnu dot org 2006-11-10 2:06 ` pinskia at gcc dot gnu dot org 2006-11-10 2:09 ` pinskia at gcc dot gnu dot org 2006-11-10 2:38 ` pinskia at gcc dot gnu dot org 2006-11-10 2:41 ` pinskia at gcc dot gnu dot org 2006-11-10 10:40 ` [Bug tree-optimization/29788] [4.1/4.2/4.3 Regression] " rguenth at gcc dot gnu dot org 2006-11-11 14:36 ` amacleod at redhat dot com 2006-11-11 14:40 ` pinskia at gcc dot gnu dot org 2006-11-12 2:29 ` pinskia at gcc dot gnu dot org 2006-11-12 2:30 ` pinskia at gcc dot gnu dot org 2006-11-12 21:34 ` mmitchel at gcc dot gnu dot org 2006-11-12 23:59 ` amacleod at redhat dot com 2006-11-15 17:05 ` pinskia at gcc dot gnu dot org 2006-11-15 17:07 ` [Bug tree-optimization/29788] [4.1/4.2 " pinskia at gcc dot gnu dot org 2006-11-16 17:14 ` pinskia at gcc dot gnu dot org 2006-11-17 15:09 ` [Bug tree-optimization/29788] [4.1 " pinskia at gcc dot gnu dot org 2006-11-17 15:10 ` pinskia at gcc dot gnu dot org 2006-12-01 2:04 ` 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=20061109234158.11673.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).