This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: C++ demangler horrors
- From: Alexandre Oliva <aoliva at redhat dot com>
- To: "H. J. Lu" <hjl at lucon dot org>
- Cc: Gabriel Dos Reis <gdr at integrable-solutions dot net>, Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>, Oscar Fuentes <ofv at wanadoo dot es>, gcc at gcc dot gnu dot org
- Date: 01 Jul 2003 10:47:11 -0300
- Subject: Re: C++ demangler horrors
- Organization: GCC Team, Red Hat
- References: <20030626193433.GA22441@disaster.jaj.com><n0g460y3.fsf@wanadoo.es> <20030626203555.GA25243@lucon.org><4r2c5mov.fsf@wanadoo.es> <20030627014931.GA30139@lucon.org><y8zo3y0l.fsf@wanadoo.es><Pine.BSF.4.56.0306271411080.53800@naos.dbai.tuwien.ac.at><20030628013200.GA23878@lucon.org><m3isqqa6gi.fsf@uniton.integrable-solutions.net><20030628145900.GA2791@lucon.org> <20030628152805.GA3496@lucon.org>
On Jun 28, 2003, "H. J. Lu" <hjl@lucon.org> wrote:
> On Sat, Jun 28, 2003 at 07:59:00AM -0700, H. J. Lu wrote:
>> My patch doesn't requrie it. But some people don't like the way I solved
>> the problem with
>>
>> ar -d ....
>> ar rc ....
It's not about not liking. Consider a parallel build in which someone
is linking with libiberty while demangler goes and modifies it. Bad
idea. And splitting this into demangler like this won't fix it:
> all:
> $(MAKE) -C ../libiberty [new_demangler|old_demangler]
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer