X-Authentication-Warning:	acp3bf.physik.rwth-aachen.de: broeker owned process doing -bs
Date:	Thu, 9 Sep 1999 18:30:03 +0200 (MET DST)
From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
X-Sender:	broeker AT acp3bf
To:	DJGPP-WORKERS <djgpp-workers AT delorie DOT com>
Subject:	Re: gcc-2.95
In-Reply-To:	<199909091439.QAA20898@propus.lu.erisoft.se>
Message-ID:	<Pine.LNX.3.93.990909182429.8972J-100000@acp3bf>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Thu, 9 Sep 1999, Martin Stromberg wrote:

> Andris said:
> > ------------------  assembler code generated by gcc-2.95
> >         leal -16(%ecx),%ebx
> >         movl $-1,%eax
> >         leal 8(%ebx),%edx
> > /APP
> >         .byte 0xf0, 0x0f, 0xc1, 0x02
> > /NO_APP
> >         cmpl $1,%eax
> >         jne L712

The marks /APP and /NO_APP usually enclose assembly coming from inline
assembly found in the C++ source. I.e. this particular line may well exist
as a verbatim 'asm' statement, in the compiled source. 

> > <_replace__t12basic_string3ZcZt18string_char_traits1ZcZt24__defaul
> > t_alloc_template2b0i0UlUlPCcUl+0x1e4>

Use of the '-C' flag would have demangled this C++ mangled name, I think.

> Any chance of identifying the C++ source that causes this to be 
> generated?

If nothing else helps, let 'as' generate a mixed C(++) and assembly
source listing, by compiling with:
	
	gcc -c -g3 -Wa,-alh

(and more options, if needed...)

Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -