public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/13709] [tree-ssa] compiler fails to bootstrap on ia64 Date: Sat, 17 Jan 2004 16:38:00 -0000 [thread overview] Message-ID: <20040117163853.23720.qmail@sources.redhat.com> (raw) In-Reply-To: <20040116160520.13709.bbooth@redhat.com> ------- Additional Comments From hubicka at ucw dot cz 2004-01-17 16:38 ------- Subject: Re: [tree-ssa] compiler fails to bootstrap on ia64 > > ------- Additional Comments From dnovillo at gcc dot gnu dot org 2004-01-17 16:19 ------- > > Jan, > > We die in flow.c:init_propagate_block_info because even though the basic block > is a conditional jump, it seemingly has no successors. Something is either > messing up or not building the RTL CFG properly. > > Program received signal SIGSEGV, Segmentation fault. > init_propagate_block_info (bb=0x2000000002892a00, live=0x60000000000edac0, > local_set=0x0, cond_local_set=0x0, flags=0) > at /home/cygnus/dnovillo/tree-ssa-01/src.ia64/gcc/flow.c:1848 > 1848 bb_true = bb->succ->dest; > (gdb) ptbb bb > ;; basic block 16, loop depth 0, count 0 > ;; prev block 8, next block 9 > ;; pred: > ;; succ: > ;; Registers live at start: 1 [r1] 8 [r8] 9 [r9] 12 [r12] 32 [r36] 33 [r37] > (note 147 55 56 16 [bb 16] NOTE_INSN_BASIC_BLOCK) > (jump_insn 56 147 62 16 > /home/cygnus/dnovillo/tree-ssa-01/src.ia64/gcc/libgcc2.c:93 (set (pc) > (if_then_else (ne (reg:BI 262 p6 [360]) > (const_int 0 [0x0])) > (label_ref 66) > (pc))) 218 {*br_true} (insn_list 55 (nil)) > (expr_list:REG_DEAD (reg:BI 262 p6 [360]) > (expr_list:REG_BR_PROB (const_int 5000 [0x1388]) > (nil)))) > ;; Registers live at end: 1 [r1] 8 [r8] 9 [r9] 12 [r12] 32 [r36] 33 [r37] > (gdb) p bb->succ > $1 = 0x0 > > > > There were a couple of changes from you that affected the CFG. Could you take a > look? Hmm, i did no changes in this area, as you didn't approved my CFG transparent expansion patch yet :) I will look into it. If you do have ia64 build, can you pass me preprocessed source so I don't need to get binutils for the crosscompiler? Honza > > > Thanks. Diego. > > -- > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |dnovillo at gcc dot gnu dot > | |org > AssignedTo|dnovillo at gcc dot gnu dot |hubicka at gcc dot gnu dot > |org |org > > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13709 > > ------- You are receiving this mail because: ------- > You are the assignee for the bug, or are watching the assignee. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13709
next prev parent reply other threads:[~2004-01-17 16:38 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-01-16 16:05 [Bug bootstrap/13709] New: " bbooth at redhat dot com 2004-01-16 16:05 ` [Bug bootstrap/13709] " bbooth at redhat dot com 2004-01-16 16:36 ` dnovillo at gcc dot gnu dot org 2004-01-16 16:50 ` pinskia at gcc dot gnu dot org 2004-01-16 18:33 ` pinskia at gcc dot gnu dot org 2004-01-17 16:19 ` dnovillo at gcc dot gnu dot org 2004-01-17 16:38 ` hubicka at ucw dot cz [this message] 2004-01-17 16:49 ` dnovillo at redhat dot com 2004-01-17 17:18 ` schwab at suse dot de 2004-01-18 14:06 ` schwab at suse dot de
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=20040117163853.23720.qmail@sources.redhat.com \ --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).