This is the mail archive of the gcc-patches@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: RFC: Make a standalone GNU V3 C++ demangler


On Thu, Apr 24, 2003 at 11:59:51AM -0400, DJ Delorie wrote:
> 
> > I tried and it didn't work for gcc. When you bootstrap gcc natively
> > with C++ enabled, the C++ compiler with <vector> isn't available before
> > libstdc++ is finished. As the result, the target libiberty will use the
> > old demangler. Also if you don't have the C++ compiler installed, the
> > old demangler will always be used even if you enable C++ in gcc build.
> > I don't believe that is what we want.
> 
> I was thinking about the host libiberty, not the target libiberty.
> Can we just -I to the libstdc++ headers?

Some of the libstdc++ header files are created during libstdc++
configure/build time and libstdc++ is configured/built after the
target libiberty was compiled. If we have to do it for target anyway,
why not to use the same for host?


H.J.


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