From: Jeffrey A Law <law@redhat.com>
To: Steven Bosscher <stevenb@suse.de>
Cc: Andrew MacLeod <amacleod@redhat.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
Diego Novillo <dnovillo@redhat.com>
Subject: Re: Fix a tcb crash and a potential bug on mainline
Date: Wed, 27 Oct 2004 16:27:00 -0000 [thread overview]
Message-ID: <1098894128.5943.3.camel@localhost.localdomain> (raw)
In-Reply-To: <200410242159.59802.stevenb@suse.de>
On Sun, 2004-10-24 at 21:59 +0200, Steven Bosscher wrote:
> On Friday 22 October 2004 21:50, Jeffrey A Law wrote:
> > Cool. Let me know how it goes.
>
> Bootstrapped and tested on i686-suse-linux-gnu, and I
> verified with GDB that the PHI is still removed at least
> for emptyif.f90.
>
> Gr.
> Steven
>
> * tree-phinodes.c (remove_phi_arg_num): Don't remove PHIs
> without any PHI arguments left. Make sure the argument that
> we're supposed to remove exists at all.
Looks good to me. Thanks for your patience.
jeff
next prev parent reply other threads:[~2004-10-27 16:22 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-18 21:09 Steven Bosscher
2004-10-18 22:06 ` Andrew MacLeod
2004-10-18 22:18 ` Andrew Pinski
2004-10-19 20:58 ` Jeffrey A Law
2004-10-19 21:29 ` Steven Bosscher
2004-10-19 22:08 ` Jeffrey A Law
2004-10-19 22:27 ` Daniel Berlin
2004-10-19 22:35 ` Jeffrey A Law
2004-10-19 23:08 ` Daniel Berlin
2004-10-19 23:14 ` Daniel Berlin
2004-10-21 2:33 ` Jeffrey A Law
2004-10-19 22:36 ` Steven Bosscher
2004-10-19 22:41 ` Diego Novillo
2004-10-19 23:16 ` Jeffrey A Law
2004-10-20 13:17 ` Andrew MacLeod
2004-10-20 13:32 ` Steven Bosscher
2004-10-20 13:47 ` Andrew MacLeod
2004-10-20 14:30 ` Steven Bosscher
2004-10-20 16:53 ` Andrew MacLeod
2004-10-20 17:33 ` Daniel Berlin
2004-10-22 19:15 ` Jeffrey A Law
2004-10-22 19:33 ` Steven Bosscher
2004-10-22 19:37 ` Jeffrey A Law
2004-10-22 19:40 ` Steven Bosscher
2004-10-22 21:08 ` Jeffrey A Law
2004-10-24 21:20 ` Steven Bosscher
2004-10-27 16:27 ` Jeffrey A Law [this message]
2004-10-22 19:10 ` Jeffrey A Law
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=1098894128.5943.3.camel@localhost.localdomain \
--to=law@redhat.com \
--cc=amacleod@redhat.com \
--cc=dnovillo@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=stevenb@suse.de \
/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).