This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: libgcc2 versus x86_64 Ada
- From: Jan Hubicka <jh at suse dot cz>
- To: David Edelsohn <dje at watson dot ibm dot com>
- Cc: Jan Hubicka <jh at suse dot cz>, gcc-patches at gcc dot gnu dot org,Richard Henderson <rth at redhat dot com>, geert at gnat dot com
- Date: Tue, 27 Aug 2002 16:39:46 +0200
- Subject: Re: libgcc2 versus x86_64 Ada
- References: <jh@suse.cz> <20020827120447.F8777@chimera.suse.cz> <200208271437.KAA05132@makai.watson.ibm.com>
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