libgcc2 versus x86_64 Ada

Jan Hubicka jh@suse.cz
Tue Aug 27 07:45:00 GMT 2002


On Tue, Aug 27, 2002 at 10:37:39AM -0400, David Edelsohn wrote:
> >>>>> Jan Hubicka writes:
> 
> Jan> Hmm, that is also possible.  I didn't noticed we do have IN_LIBGCC2.
> Jan> Is that considered cleaner approach than the former?
> Jan> (we do use the LIBGCC2_* macros for some other stuff and from some kind
> Jan> it looks to me cleaner to not reuse same macro for two different purposes)
> 
> 	Yes, I think using IN_LIBGCC2 is cleaner and it allows you to
> limit the modifications to i386.h only.  Such a change might even be
> considered "obvious".

OK, except that one thing I would like to see in future is not combining same header
for host and target compilation, so we would probably like to have two different headers
for each target and two macros for each of them.

I will make the patch shortly and commit it as obvious once the reload problem
is resolved.

Honza

> 
> 	I am planning to use that approach for PowerPC.  As I mentioned
> before, the Sparc port uses it as well.  There is no need for another
> macro in libgcc2.c.
> 
> David



More information about the Gcc-patches mailing list