This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC 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: gcc-in-cxx branch created


On Thu, 19 Jun 2008, Ian Lance Taylor wrote:

> "Kaveh R. GHAZI" <ghazi@caip.rutgers.edu> writes:
>
> > I'd like to avoid stomping on each other and duplicating work.  Can you
> > tell me what you've already done and/or plan to do?
>
> I have a bunch of patches, but as far as getting them into mainline
> I'm limited by the time it takes to run a bootstrap and test run (I'm
> at the summit and am just working on my laptop).  Right now I am
> testing the appended patch for mainline; that should clear up a lot of
> enum warnings.  I recommend applying this patch to your working
> directory, and look at the warnings that remain.
>
> Other than that, everything I've done is minor stuff like the message
> to which you refer.  I don't know how to avoid duplicating work at
> that level.  If you want to pick a set of files to start with, that
> works for me.

Okay, looks like you have the enum problem under control.  I'm attacking
the void*->T* problem on mainline.  So far I've got most of the java
directory, the objc directory and a few top level files (gcc.c,
collect2.c, tlink.c) done and it's undergoing regtesting.  I'll install as
"obvious" on mainline since it's just casting and/or using the libiberty
C++ macros created explicitly for this purpose.

I'll do fortran next, then some top level files.  I'll post in this thread
which ones so we don't overlap.  Please do the same.

		Thanks,
		--Kaveh
--
Kaveh R. Ghazi			ghazi@caip.rutgers.edu


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