public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Jan Hubicka <jh@suse.cz> To: hubicka@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/10024: [3.4 regression] [HP-PA] inline optimization ICE Date: Fri, 11 Apr 2003 17:06:00 -0000 [thread overview] Message-ID: <20030411170600.10834.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/10024; it has been noted by GNATS. From: Jan Hubicka <jh@suse.cz> To: John David Anglin <dave@hiauly1.hia.nrc.ca> Cc: Jan Hubicka <jh@suse.cz>, zack@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, tausq@debian.org Subject: Re: optimization/10024: [3.4 regression] [HP-PA] inline optimization ICE Date: Fri, 11 Apr 2003 18:58:20 +0200 > > > It appears that the addition of the following patch > > > > > > Mon Apr 7 15:56:30 CEST 2003 Jan Hubicka <jh@suse.cz> > > > > > > PR opt/10024 > > > Revert Zack's change > > > * cfglayout.c (cfg_layout_redirect_edge): > > > Redirect any branch edges unified with the fallthru one. > > > * cfgrtl.c (force_nonfallthru_and_redirect): Do not special > > > case fallthru edges when called via cfglayout.c > > > > > > causes gcc.c-torture/compile/20030405-1.c to fail on > > > hppa2.0w-hp-hpux11.11 on the 3.3 branch at -O2 and above. > > The failure only exists on 3.3, so I suspect the fix must already > be in the trunk. Actually it is not. Only trunk has different reordering alrotihm. I've never heard back about the bootstrap sucess/failure with my proposed patch. Will try to check the archives. Honza > > Dave > -- > J. David Anglin dave.anglin@nrc-cnrc.gc.ca > National Research Council of Canada (613) 990-0752 (FAX: 952-6602)
next reply other threads:[~2003-04-11 17:06 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-11 17:06 Jan Hubicka [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-21 19:36 John David Anglin 2003-04-14 17:27 hubicka 2003-04-13 3:56 John David Anglin 2003-04-11 17:46 John David Anglin 2003-04-08 20:36 John David Anglin 2003-04-06 0:47 zack
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=20030411170600.10834.qmail@sources.redhat.com \ --to=jh@suse.cz \ --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).