public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "paolo dot bonzini at lu dot unisi dot ch" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/32758] [4.3 Regression] ecj1 hangs Date: Wed, 29 Aug 2007 12:16:00 -0000 [thread overview] Message-ID: <20070829121548.27440.qmail@sourceware.org> (raw) In-Reply-To: <bug-32758-10129@http.gcc.gnu.org/bugzilla/> ------- Comment #24 from paolo dot bonzini at lu dot unisi dot ch 2007-08-29 12:15 ------- Subject: Re: [4.3 Regression] ecj1 hangs > Here is what I will try to regtest (already verified it fixes the testcase). This is wrong, because local_live changes during execution of dce_process_block. The {eh,regular}_block_artificial_uses must always be set (they are live throughout, not just at the bottom of the basic block). > Alternatively, artificial_live could be a pointer bitmap which would just > point to one of the &df->*_block_artificial_uses bitmap, though not sure > if that ever could or in some register that wasn't originally set in > local_live. Much better, and would have the same effect as dce_simulate_fixup_sets. > Certainly calling df_has_eh_preds just once per bb rather than per insn is IMHO > worthwhile. A patch to do so if preapproved if you add a comment saying /* Calling df_simulate_fixup_sets has the disadvantage of calling df_has_eh_preds once per insn, so we cache the information here. */ before the place where you set artificial_live. Thanks! -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32758
next prev parent reply other threads:[~2007-08-29 12:16 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-07-13 18:28 [Bug java/32758] New: " dir at lanl dot gov 2007-07-15 21:04 ` [Bug java/32758] " pinskia at gcc dot gnu dot org 2007-07-16 12:32 ` dir at lanl dot gov 2007-07-16 12:35 ` dir at lanl dot gov 2007-07-16 12:49 ` dir at lanl dot gov 2007-07-24 14:33 ` tromey at gcc dot gnu dot org 2007-07-25 12:56 ` dir at lanl dot gov 2007-08-03 14:03 ` dir at lanl dot gov 2007-08-06 20:34 ` andreast at gcc dot gnu dot org 2007-08-08 8:48 ` aph at gcc dot gnu dot org 2007-08-14 1:11 ` [Bug middle-end/32758] [4.3 Regression] " pinskia at gcc dot gnu dot org 2007-08-24 21:06 ` andreast at gcc dot gnu dot org 2007-08-26 21:28 ` andreast at gcc dot gnu dot org 2007-08-27 7:57 ` andreast at gcc dot gnu dot org 2007-08-27 7:58 ` andreast at gcc dot gnu dot org 2007-08-28 11:44 ` aph at gcc dot gnu dot org 2007-08-28 12:17 ` rguenth at gcc dot gnu dot org 2007-08-28 18:44 ` andreast at gcc dot gnu dot org 2007-08-28 19:39 ` jakub at gcc dot gnu dot org 2007-08-28 21:01 ` andreast at gcc dot gnu dot org 2007-08-29 8:07 ` jakub at gcc dot gnu dot org 2007-08-29 8:52 ` jakub at gcc dot gnu dot org 2007-08-29 11:19 ` jakub at gcc dot gnu dot org 2007-08-29 11:41 ` jakub at gcc dot gnu dot org 2007-08-29 11:47 ` paolo dot bonzini at lu dot unisi dot ch 2007-08-29 12:16 ` paolo dot bonzini at lu dot unisi dot ch [this message] 2007-08-29 13:27 ` jakub at gcc dot gnu dot org 2007-08-29 13:56 ` jakub at gcc dot gnu dot org 2007-08-29 14:12 ` bonzini at gnu dot org 2007-08-29 14:15 ` bonzini at gnu dot org 2007-08-29 14:17 ` bonzini at gnu dot org 2007-08-29 15:34 ` zadeck at naturalbridge dot com 2007-08-29 20:17 ` andreast at gcc dot gnu dot org 2007-08-30 8:27 ` jakub at gcc dot gnu dot org 2007-08-30 8:44 ` jakub at gcc dot gnu dot org
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=20070829121548.27440.qmail@sourceware.org \ --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).