public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Jan Hubicka <jh@suse.cz>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/10024 [3.3 regression] [HP-PA] inline optimization ICE
Date: Thu, 27 Mar 2003 01:06:00 -0000	[thread overview]
Message-ID: <20030327010600.4347.qmail@sources.redhat.com> (raw)

The following reply was made to PR optimization/10024; it has been noted by GNATS.

From: Jan Hubicka <jh@suse.cz>
To: Zack Weinberg <zack@codesourcery.com>
Cc: Jan Hubicka <jh@suse.cz>, gcc-gnats@gcc.gnu.org, tausq@debian.org
Subject: Re: optimization/10024 [3.3 regression] [HP-PA] inline optimization ICE
Date: Thu, 27 Mar 2003 01:57:36 +0100

 > >
 > > In 3.4 something different is happening -- we get a verify_flow_info
 > > failure, and this code path is never taken.  I will continue looking.
 > 
 > Jan, for background, this is an ICE caused by basic block reordering
 > having mangled the flow graph.
 > 
 > When reorder_basic_blocks is called, we have these basic blocks:
 > 
 > ;; Basic block 13, loop depth 0, count 0
 > ;; Predecessors:  12 [100.0%]  (fallthru) 7 [100.0%]  4 [100.0%] 
 > ;; Registers live at start: 2 [%r2] 20 [%r20] 30 [%r30]
 > (code_label 159 262 236 13 13 "" [2 uses])
 > (note 236 159 162 13 [bb 13] NOTE_INSN_BASIC_BLOCK)
 > (note 162 236 180 13 NOTE_INSN_DELETED)
 > (jump_insn 180 162 186 13 0x4001b65c (parallel [
 >             (set (pc)
 >                 (if_then_else (ge (reg/v:SI 20 %r20 [orig:123 <anonymous> ] [123])
 >                         (const_int 0 [0x0]))
 >                     (label_ref 186)
 >                     (pc)))
 >             (set (reg/v:SI 28 %r28 [orig:104 <anonymous> ] [104])
 >                 (reg/v:SI 20 %r20 [orig:123 <anonymous> ] [123]))
 >         ]) 232 {*pa.md:7408} (nil)
 >     (expr_list:REG_DEAD (reg/v:SI 20 %r20 [orig:123 <anonymous> ] [123])
 >         (expr_list:REG_BR_PROB (const_int 10000 [0x2710])
 >             (nil))))
 > ;; Registers live at end: 2 [%r2] 28 [%r28] 30 [%r30]
 > ;; Successors:  14 [100.0%]  (fallthru)
 > 
 > ;; Basic block 14, loop depth 0, count 0
 > ;; Predecessors:  13 [100.0%]  (fallthru) 1 [100.0%] 
 > ;; Registers live at start: 2 [%r2] 28 [%r28] 30 [%r30]
 > (code_label 186 180 241 14 19 "" [2 uses])
 > 
 > [snip]
 > 
 > 
 > Yes, that is an awful weird jump_insn, but the PA really can do that
 > in one machine instruction.  ("movb,>= %r20,%r28,.L25" is what it
 > would wind up looking like.)  Anyway, there is nothing that I see
 > wrong with this.
 
 Yes, these nasty condjumps jumping to next instructions are bringing me
 constant headaches.  I guess the attached fix to my previous fix to
 similar problem will help - I was having so many attempts to solve this
 problem somehow so I end up forgetting to remove bogus redirect.
 
 Won't be able to check the patch before tomorrow at least.
 
 Honza
 
 Index: cfglayout.c
 ===================================================================
 RCS file: /cvs/gcc/gcc/gcc/cfglayout.c,v
 retrieving revision 1.23.2.2
 diff -c -3 -p -r1.23.2.2 cfglayout.c
 *** cfglayout.c	25 Mar 2003 20:31:42 -0000	1.23.2.2
 --- cfglayout.c	27 Mar 2003 00:56:18 -0000
 *************** fixup_reorder_chain ()
 *** 478,485 ****
   
   		  e_fake = unchecked_make_edge (bb, e_fall->dest, 0);
   
 - 		  if (!redirect_jump (bb->end, block_label (bb), 0))
 - 		    abort ();
   		  note = find_reg_note (bb->end, REG_BR_PROB, NULL_RTX);
   		  if (note)
   		    {
 --- 478,483 ----


             reply	other threads:[~2003-03-27  1:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-27  1:06 Jan Hubicka [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-06 19:46 Zack Weinberg
2003-04-06 12:06 Jan Hubicka
2003-04-06  0:26 Zack Weinberg
2003-04-05 23:16 Richard Henderson
2003-03-26 20:46 Zack Weinberg
2003-03-26 18:45 Zack Weinberg
2003-03-26 18:36 Zack Weinberg
2003-03-14 15:14 optimization/10024: " ebotcazou

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=20030327010600.4347.qmail@sources.redhat.com \
    --to=jh@suse.cz \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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: link
Be 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).