This is the mail archive of the java-patches@gcc.gnu.org mailing list for the Java project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH PING] unreviewed tree-slimming patches


>>>>> "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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]