public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com> To: hubicka@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/10024 [3.3 regression] [HP-PA] inline optimization ICE Date: Sun, 06 Apr 2003 19:46:00 -0000 [thread overview] Message-ID: <20030406194600.31559.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/10024; it has been noted by GNATS. From: Zack Weinberg <zack@codesourcery.com> To: Jan Hubicka <jh@suse.cz> Cc: Richard Henderson <rth@redhat.com>, gcc-patches@gcc.gnu.org, gcc-gnats@gcc.gnu.org, tausq@debian.org Subject: Re: optimization/10024 [3.3 regression] [HP-PA] inline optimization ICE Date: Sun, 06 Apr 2003 12:38:00 -0700 Jan Hubicka <jh@suse.cz> writes: >> On Wed, Mar 26, 2003 at 10:27:54AM -0800, Zack Weinberg wrote: >> > * cfgrtl.c (force_nonfallthru_and_redirect): If e is the edge >> > we want, use it. >> >> Yes, this is ok for 3.3. > I am attaching the fix I sent some time ago. It fixes the checking > failure as well and fixes force_nonfallthru_and_redirect slightly > differently - it just bypass the code when redirection is noop. I > beleive it is slightly more safe as still we may have instruction with > multiple outgoing edges where Zacks code would result in misscompilation > (mine would die, not much better) Dying is definitely better than silently miscompiling. I say go ahead and back out my change and apply yours on both mainline and branch (but don't bother with the test case, I already applied it). ... > PR opt/10024 > * cfglayout.c (cfg_layout_redirect_edge): Update the jump. This changelog entry means nothing to me. Better to say what you say in the comment below. > * cfgrtl.c (force_nonfallthru_and_redirect): Do not special > case the fallthru edges when called via cfglayout.c There should be no "the" in this sentence. > + /* Redirect also the branch edges unified with the fallthru one. */ Better to say "Redirect any branch edges ..." > + /* We may be called from cfglayout when the fallthru edges can go > + arbitarily. */ > + && e->src->next_bb == e->dest /* When called from cfglayout, fallthru edges do not necessarily go to the next block. */ zw
next reply other threads:[~2003-04-06 19:46 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-06 19:46 Zack Weinberg [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-06 12:06 Jan Hubicka 2003-04-06 0:26 Zack Weinberg 2003-04-05 23:16 Richard Henderson 2003-03-27 1:06 Jan Hubicka 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=20030406194600.31559.qmail@sources.redhat.com \ --to=zack@codesourcery.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=hubicka@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).