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/8492: [3.3 regression] GCC spins forever compiling loop
Date: Sat, 21 Dec 2002 15:46:00 -0000	[thread overview]
Message-ID: <20021221234602.15788.qmail@sources.redhat.com> (raw)

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

From: Jan Hubicka <jh@suse.cz>
To: Eric Botcazou <ebotcazou@libertysurf.fr>
Cc: Jan Hubicka <jh@suse.cz>, janis187@us.ibm.com,
	gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org,
	nobody@gcc.gnu.org, thorpej@shagadelic.org
Subject: Re: optimization/8492: [3.3 regression] GCC spins forever compiling loop
Date: Sun, 22 Dec 2002 00:43:50 +0100

 > > I think deleting unreachable blocks is cheap enought to do in the case
 > > conditional jump was eliminated.
 > 
 > Ok. But then the GCSE code needs to be (at least partially) re-initialized 
 > because the number of basic blocks may change. I've attached a naive patch I 
 > wrote some time ago: while fixing the PR (and doing some housekeeping work), 
 > it introduces many regressions because of this problem.
 > 
 > > Alternatively we may prevent first local cprop pass from modifying CFG.
 > 
 > I don't know enough of the global organization of optimization passes to 
 > comment. Will the optimizations missed at that point be caught elsewhere ?
 
 Yes, there are examples where removing the conditional would allow more
 PRE to happen, but I guess it is not that common.  We already disable
 the transformation for global CPROP and in fact I am quite surprised
 that I didn't the same for local pass.  I guess I just forgot about
 that.
 
 Honza
 > 
 > -- 
 > Eric Botcazou
 


             reply	other threads:[~2002-12-21 23:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-21 15:46 Jan Hubicka [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-14 20:07 ebotcazou
2002-12-21  4:46 Eric Botcazou
2002-12-21  3:16 Jan Hubicka
2002-12-21  3:16 Eric Botcazou
2002-12-20 14:56 Janis Johnson
2002-11-25  7:56 bangerth

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=20021221234602.15788.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).