public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/42511] bootstrap error in stage3 on alpha-linux-gnu Date: Tue, 05 Jan 2010 14:21:00 -0000 [thread overview] Message-ID: <20100105142122.11284.qmail@sourceware.org> (raw) In-Reply-To: <bug-42511-5724@http.gcc.gnu.org/bugzilla/> ------- Comment #8 from ubizjak at gmail dot com 2010-01-05 14:21 ------- It looks that tree loop IM FUBARs the compilation. All testcases compile OK with -O2 -fno-tree-loop-im. The dump for _.c.099t.lim1 looks quite strange (it resembles _.c.024t.ssa): --cut here-- ;; Function alpha_fallback_frame_state (alpha_fallback_frame_state) Symbols to be put in SSA form { .MEM fs___regfs__I_I__howfs___regfs__I_I_I.3 } Incremental SSA update started at block: 0 Number of blocks in CFG: 6 Number of blocks to update: 5 ( 83%) SSA replacement table N_i -> { O_1 ... O_j } means that N_i replaces O_1, ..., O_j fs___regfs__I_I__howfs___regfs__I_I_I.3_10 -> { fs___regfs__I_I__howfs___regfs__I_I_I.3_9 } Number of virtual NEW -> OLD mappings: 0 Number of real NEW -> OLD mappings: 1 Number of total NEW -> OLD mappings: 1 Number of virtual symbols: 0 Incremental SSA update started at block: 3 Number of blocks in CFG: 6 Number of blocks to update: 2 ( 33%) alpha_fallback_frame_state (struct _Unwind_FrameState * fs) { int fs___regfs__I_I__howfs___regfs__I_I_I.3; long int pretmp.2; long int i; long int D.2028; <bb 2>: D.2028_3 = i_11 + 32; fs___regfs__I_I__howfs___regfs__I_I_I.3_8 = fs_4(D)->reg[D.2028_3].how; <bb 3>: # i_11 = PHI <i_5(4), 0(2)> fs___regfs__I_I__howfs___regfs__I_I_I.3_9 = 0; i_5 = i_11 + 1; if (i_5 <= 30) goto <bb 4>; else goto <bb 5>; <bb 4>: goto <bb 3>; <bb 5>: # fs___regfs__I_I__howfs___regfs__I_I_I.3_10 = PHI <fs___regfs__I_I__howfs___regfs__I_I_I.3_9(3)> fs_4(D)->reg[D.2028_3].how = fs___regfs__I_I__howfs___regfs__I_I_I.3_10; return; } --cut here-- -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42511
next prev parent reply other threads:[~2010-01-05 14:21 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-12-26 18:01 [Bug bootstrap/42511] New: boostrap " debian-gcc at lists dot debian dot org 2009-12-26 18:01 ` [Bug bootstrap/42511] " debian-gcc at lists dot debian dot org 2009-12-31 15:19 ` rguenth at gcc dot gnu dot org 2010-01-04 17:42 ` [Bug bootstrap/42511] bootstrap " debian-gcc at lists dot debian dot org 2010-01-05 12:30 ` ubizjak at gmail dot com 2010-01-05 13:52 ` ubizjak at gmail dot com 2010-01-05 13:53 ` rguenth at gcc dot gnu dot org 2010-01-05 14:16 ` debian-gcc at lists dot debian dot org 2010-01-05 14:21 ` ubizjak at gmail dot com [this message] 2010-01-05 14:27 ` ubizjak at gmail dot com 2010-01-05 15:36 ` rguenth at gcc dot gnu dot org 2010-01-05 16:25 ` ubizjak at gmail dot com 2010-01-05 20:47 ` ubizjak at gmail dot com 2010-01-05 21:15 ` ubizjak at gmail dot com 2010-01-06 10:44 ` ubizjak at gmail dot com 2010-01-06 10:45 ` ubizjak at gmail dot com 2010-01-06 11:32 ` [Bug rtl-optimization/42511] [4.5 Regression] " rguenth at gcc dot gnu dot org 2010-01-06 15:17 ` ubizjak at gmail dot com 2010-01-06 18:14 ` ubizjak at gmail dot com 2010-01-06 23:16 ` ubizjak at gmail dot com 2010-01-07 0:00 ` ebotcazou at gcc dot gnu dot org 2010-01-07 7:29 ` ubizjak at gmail dot com 2010-01-07 7:39 ` ebotcazou at gcc dot gnu dot org 2010-01-07 8:02 ` ubizjak at gmail dot com 2010-01-07 8:22 ` ebotcazou at gcc dot gnu dot org 2010-01-07 8:50 ` ubizjak at gmail dot com 2010-01-07 9:18 ` ubizjak at gmail dot com 2010-01-07 9:23 ` ubizjak at gmail dot com 2010-01-07 11:22 ` ubizjak at gmail dot com 2010-01-07 11:55 ` debian-gcc at lists dot debian dot org 2010-01-07 13:03 ` uros at gcc dot gnu dot org 2010-01-07 14:45 ` rguenth at gcc dot gnu dot org 2010-01-07 15:00 ` uros at gcc dot gnu dot org 2010-01-07 17:32 ` uros at gcc dot gnu dot org 2010-01-08 7:33 ` ubizjak at gmail dot com
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=20100105142122.11284.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).