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 03:16:00 -0000 [thread overview] Message-ID: <20021221111602.9726.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: 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, jh@suse.cz Subject: Re: optimization/8492: [3.3 regression] GCC spins forever compiling loop Date: Sat, 21 Dec 2002 12:14:29 +0100 > > The mainline regression reported in PR optimization/8492 > > (an infinite loop in the compiler) showed up starting with > > this patch: > > > > Sun Jul 21 00:54:54 CEST 2002 Jan Hubicka <jh@suse.cz> > > > > * gcse.c: Include cselib.h > > (constptop_register): Break out from ... > > (cprop_insn): ... here; kill basic_block argument. > > (do_local_cprop, local_cprop_pass): New functions. > > (one_cprop_pass): Call local_cprop_pass. > > > > Ha! I understand now... see the analysis: > http://gcc.gnu.org/ml/gcc/2002-12/msg00039.html > > I think the CFG should be cleaned up between the local cprop pass and the > global cprop pass, but I guess doing so won't particularly speed up the > compiler, to say the least. I think deleting unreachable blocks is cheap enought to do in the case conditional jump was eliminated. Alternatively we may prevent first local cprop pass from modifying CFG. I will try to get into this tonight. Thanks! Honza > > -- > Eric Botcazou
next reply other threads:[~2002-12-21 11:16 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-21 3:16 Jan Hubicka [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-01-14 20:07 ebotcazou 2002-12-21 15:46 Jan Hubicka 2002-12-21 4:46 Eric Botcazou 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=20021221111602.9726.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: 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).