From: Diego Novillo <dnovillo@redhat.com>
To: Mark Mitchell <mark@codesourcery.com>
Cc: Andrew Pinski <pinskia@physics.uc.edu>,
Daniel Berlin <dberlin@dberlin.org>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Andrew Macleod <amacleod@redhat.com>
Subject: Re: [PATCH]: Implement must-def kill operand
Date: Sat, 23 Oct 2004 12:56:00 -0000 [thread overview]
Message-ID: <1098507722.27985.27.camel@localhost.localdomain> (raw)
In-Reply-To: <4179B31F.4020905@codesourcery.com>
On Fri, 2004-10-22 at 21:25, Mark Mitchell wrote:
> Andrew Pinski wrote:
>
> >
> > On Oct 17, 2004, at 10:00 PM, Daniel Berlin wrote:
> >
> >> [Diego, if this isn't accepted for mainline, i'd still like to put it
> >> on TCB, so if you could take a look at it, i'd appreciate it]
> >
> I've reviewed the PR and this thread, and I'd definitely like to see the
> (finished) version of this patch go in. I think that Daniel and Diego
> are converging nicely to a solution.
>
Yes, I failed to make it explicit in my previous messages, but once Dan
finishes the latest tweaks to the patch, I will recommend that it be
applied on mainline.
Diego.
prev parent reply other threads:[~2004-10-23 5:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-18 2:29 Daniel Berlin
2004-10-20 17:41 ` Diego Novillo
2004-10-20 17:56 ` Daniel Berlin
2004-10-20 18:08 ` Diego Novillo
2004-10-20 18:28 ` Daniel Berlin
2004-10-20 20:36 ` Diego Novillo
2004-10-20 20:49 ` Daniel Berlin
2004-10-20 20:57 ` Diego Novillo
2004-10-20 21:01 ` Daniel Berlin
[not found] ` <531813B6-22DA-11D9-B310-000D93B1B044@dberlin.org>
2004-10-20 21:04 ` Diego Novillo
2004-10-20 21:27 ` Daniel Berlin
2004-10-20 22:23 ` Andrew Pinski
2004-10-23 5:02 ` Mark Mitchell
2004-10-23 12:56 ` Diego Novillo [this message]
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=1098507722.27985.27.camel@localhost.localdomain \
--to=dnovillo@redhat.com \
--cc=amacleod@redhat.com \
--cc=dberlin@dberlin.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=mark@codesourcery.com \
--cc=pinskia@physics.uc.edu \
/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).