From: Tom Tromey <tromey@redhat.com>
To: Nathan Froyd <froydnj@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org, Jason Merrill <jason@redhat.com>,
"Joseph S. Myers" <joseph@codesourcery.com>,
java-patches@gcc.gnu.org,
Richard Guenther <richard.guenther@gmail.com>
Subject: Re: [PATCH PING] unreviewed tree-slimming patches
Date: Wed, 25 May 2011 19:31:00 -0000 [thread overview]
Message-ID: <m3y61uwt70.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4DDD0B95.40308@codesourcery.com> (Nathan Froyd's message of "Wed, 25 May 2011 10:00:53 -0400")
>>>>> "Nathan" == Nathan Froyd <froydnj@codesourcery.com> writes:
Nathan> (C, Java, middle-end)
Nathan> [PATCH 18/18] make TS_BLOCK a substructure of TS_BASE
Nathan> http://gcc.gnu.org/ml/gcc-patches/2011-03/msg00564.html
The Java parts are ok.
I think these sorts of changes should be obvious once approved from a
middle-end perspective, at least assuming that there are no regressions.
I say this because I think that once the core change has been decided
on, there is often just one way to go about fixing up the users; at
least, in a case like this where the consequence amounts to deleting
assignments.
I mentioned this idea before but I didn't see any discussion of it. I
am happy to continue looking at patches like this if that is what the
more active maintainers would prefer.
Tom
next prev parent reply other threads:[~2011-05-25 18:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 14:33 Nathan Froyd
2011-05-25 14:40 ` Jason Merrill
2011-05-26 8:47 ` Nathan Froyd
2011-05-26 14:00 ` Jason Merrill
2011-05-26 14:34 ` Nathan Froyd
2011-05-26 14:36 ` Jason Merrill
2011-05-27 4:54 ` Nathan Froyd
2011-05-27 8:14 ` Jason Merrill
2011-05-25 14:42 ` Richard Guenther
2011-05-25 17:44 ` Joseph S. Myers
2011-05-25 19:31 ` Tom Tromey [this message]
2011-05-25 19:36 ` Nathan Froyd
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=m3y61uwt70.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=froydnj@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=java-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=richard.guenther@gmail.com \
/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).