This is the mail archive of the java@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: FYI: submitted ecj patch upstream

From: Tom Tromey <tromey at redhat dot com>
To: Joel Dice <dicej at mailsnare dot net>
Cc: GCC Java <java at gcc dot gnu dot org>
Date: 09 Oct 2006 12:18:36 -0600
Subject: Re: FYI: submitted ecj patch upstream
References: <200610091742.k99HgZe8026643@earth.phy.uc.edu> <Pine.LNX.4.62.0610091143450.5287@joeldicepc.ecovate.com>
Reply-to: tromey at redhat dot com

>>>>> "Joel" == Joel Dice <dicej@mailsnare.net> writes:

Joel> Are there any legal or technical barriers to maintaining GCCMain.java
Joel> in the GCC source tree and generating ecj1.jar during the build
Joel> process?

We could change the build to assume an upstream-style ecj when we're
generating class files.

However... this may be a little fragile as we don't know whether the
upstream .jar will change in a way that breaks GCCMain.  One nice
thing about keeping our own download is that we have more control over
changes.

Another nice thing about the current approach is that it provides a
smoke test of the gcj spec file processing code.

I don't know whether there are legal barriers.

Tom

References:
- Re: FYI: submitted ecj patch upstream
  - From: Andrew Pinski
- Re: FYI: submitted ecj patch upstream
  - From: Joel Dice

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