RFC: micro-libgcj merge proposal

[David Daney]

Tom Tromey wrote:
>>>>>>"Per" == Per Bothner <per@bothner.com> writes:
> 
> 
>>>I cannot use micro-libgcj if it contains too small a sub-set of
>>>libgcj.  Likewise I don't want it to be too big.  My requirements do
>>>not cleanly fit into any of Sun's J2ME profiles so I don't want that
>>>either.
> 
> 
> Per> That is why we need pre-processing.  At configure time you select a
> Per> "profile" - either a "standard" named profile or a custom profile.
> 
> Adopting preprocessing in libgcj would put the maintenance cost on the
> wrong people -- those doing a merge and trying to make a full J2SE,
> not those wanting an unusual custom build.
> 
> So, I think preprocessing would have to be accepted upstream first.
>

If I were to do it (which I may), I would do most of the early 
development on a branch in GCC's svn.  After we had something working we 
could generate two patches.  One for libgcj specific changes , and one 
for the more general classpath changes.

Bringing the classpath specific parts back into libgcj could then be 
done with a normal classpath merge.

David Daney