public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jan Hubicka <jh@suse.cz>
To: Olivier Hainque <hainque@ACT-Europe.FR>
Cc: Jan Hubicka <jh@suse.cz>, Michael Matz <matz@suse.de>, gcc@gcc.gnu.org
Subject: Re: Question on fixup_abnormal_edges
Date: Tue, 01 Oct 2002 07:02:00 -0000	[thread overview]
Message-ID: <20021001140254.GY29411@kam.mff.cuni.cz> (raw)
In-Reply-To: <20021001154929.D16040@berlin.int.act-europe.fr>

> 
> 
> Jan Hubicka wrote:
> > I think we should make reload to recognize that given insn never
> > fallsthru and avoid it from generating such dead code.  Even in case of
> > USE it is wrong and here as well.  What is the last insn in the basic
> > block?
> 
> The same as the previous one:
> 
> Breakpoint 2, fixup_abnormal_edges () at ../../src/gcc/reload1.c:9522
> 9522    && insn != bb->head)
> 
> (gdb) list
> 
> 9518    /* Get past the new insns generated. Allow notes, as the insns may
> 9519       be already deleted.  */
> 9520    while ((GET_CODE (insn) == INSN || GET_CODE (insn) == NOTE)
> 9521           && !can_throw_internal (insn)
> 9522           && insn != bb->head)
> 9523      insn = PREV_INSN (insn);
> 9524    if (GET_CODE (insn) != CALL_INSN && !can_throw_internal (insn))
> 9525      abort ();
> 9526    bb->end = insn;
> 
> (gdb) p e
> $1 = 0x0
> 
> (gdb) pr bb->end
> (insn 2134 444 445 (set (reg:DI 22 $22)
>         (mem:DI (plus:DI (reg/f:DI 29 $29)
>       (const_int 640 [0x280])) [48 S8 A64])) 244 {*movdi_nofix} (nil)
>     (nil))

Can you print the whole BB using debug_bb?  This still looks like
reloading, so the instruction requiring the reload is probably earlier.
What target do you use?

Honza
> 
> 
> 
> Olivier

  reply	other threads:[~2002-10-01 14:02 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-01  2:06 Olivier Hainque
2002-10-01  2:08 ` Jan Hubicka
2002-10-01  2:57   ` Olivier Hainque
2002-10-01  3:00   ` Michael Matz
2002-10-01  3:03     ` Michael Matz
2002-10-01  3:40       ` Olivier Hainque
2002-10-01  4:23         ` Jan Hubicka
2002-10-01  6:49           ` Olivier Hainque
2002-10-01  7:02             ` Jan Hubicka [this message]
2002-10-01  7:08               ` Olivier Hainque
2002-10-01  7:12                 ` Jan Hubicka
2002-10-01  8:44                   ` Olivier Hainque
2002-10-01  9:08                     ` Jan Hubicka
2002-10-01  9:46                       ` Olivier Hainque
2002-10-01 12:24                         ` Michael Matz
2002-10-02 14:11                           ` Olivier Hainque
2002-10-03  6:20                             ` Jan Hubicka
2002-10-03  6:26                               ` Olivier Hainque
2002-10-03  6:51                                 ` Jan Hubicka
2002-10-03  8:06                                   ` Olivier Hainque
2002-10-03  8:19                                     ` Jan Hubicka
2002-10-15  5:35                                       ` Olivier Hainque
2002-10-15 17:03                                         ` Richard Henderson
2002-10-16  2:58                                           ` Olivier Hainque
2002-10-16  4:02                                           ` Michael Matz
2002-10-16  4:06                                             ` Jan Hubicka
2002-10-16  4:45                                               ` Michael Matz
2002-10-16  5:01                                                 ` Jan Hubicka
2002-10-16 10:29                                                   ` Richard Henderson
2002-10-16 10:26                                             ` Richard Henderson
2002-10-01  4:43         ` Michael Matz
2002-10-01  4:46           ` Jan Hubicka
2002-10-15  6:10 Richard Kenner
2002-10-15  7:47 ` Michael Matz
2002-10-15  9:25   ` Michael Matz
2002-10-16  0:31 Richard Kenner
2002-10-16  2:31 ` Richard Henderson
2002-10-16  7:08 Richard Kenner
2002-10-21 11:50 ` Jeff Law
2002-10-21 11:54   ` David S. Miller
2002-10-16  7:12 Richard Kenner

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=20021001140254.GY29411@kam.mff.cuni.cz \
    --to=jh@suse.cz \
    --cc=gcc@gcc.gnu.org \
    --cc=hainque@ACT-Europe.FR \
    --cc=matz@suse.de \
    /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).