This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Detect obstacks in libc
- To: Zack Weinberg <zack at wolery dot cumb dot org>
- Subject: Re: Detect obstacks in libc
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Fri, 07 Jul 2000 06:58:36 -0600
- cc: gcc-patches at gcc dot gnu dot org
- Reply-To: law at cygnus dot com
In message <20000706104920.L284@wolery.cumb.org>you write:
> > > No makefile fragment that I can find overrides OBSTACK.
> > On what do we gain by using obstack in the system C library?
>
> As I said, with this change we don't bother building the "host"
> version of obstack.o in a native build.
I don't see that as a significant benefit.
> > How do you arrange to make sure that you do include libiberty/obstack.h
> > which might be incompatible with the system obstack implementation
> > (yes, it does matter).
>
> libiberty/obstack.c already contains code which detects a system
> obstack implementation. If found, it #ifdefs out all its code. I
> used the exact same test in configure, so we'll have a problem iff we
> already have a problem.
Does it also manage to ifdef out the obstack.h included all over the compiler?
This really seems bad to me.
jeff
>
> zw
>