Re: Assembler problem while trying to integrate D iompiler in GCC suite

["Gerrit P. Haase" <gerrit@familiehaase.de>]

Dave Korn wrote:

> ----Original Message----
> 
>>From: Gerrit P. Haase
>>Sent: 07 June 2005 11:59
> 
> 
>>Hi all,
>>
>>I'm trying to integrate the D frontend for GCC in the GCC 3.4.4 release,
> 
> 
>>What is new in the source regarding this problem is this patch which
>>gives me the error cited below:
> 
> 
[...]
>>+   ASM_GENERATE_INTERNAL_LABEL (buf, "LTHUNK", thunk_labelno);
> 
> 
> 
> 
>>Gives me this error now:
>>
>>$ /gcc/gcc-3.4.4/gcc-3.4.4-1/.build/gcc/gdc -save-temps
>>-B/gcc/gcc-3.4.4/gcc-3.4.4-1/.build/gcc/ -B/usr/i686-pc-cygwin/bin/
>>-B/usr/i686-pc-cy>
>>gdc: warning: -pipe ignored because -save-temps specified
>>socketstream.s: Assembler messages:
>>socketstream.s:1416: Error: Local symbol `LTHUNK0' can't be equated to
>>undefined symbol `__D3std6stream6Stream9readExactFPvkZv'
> 
> 
>   So what happens if you use a label that doesn't begin with an 'L'?  Frex
> 
> 
> 
>>+   ASM_GENERATE_INTERNAL_LABEL (buf, "__LTHUNK", thunk_labelno);

Given the magic which is included in creating binaries that computers
can understand and do s.th. that the binaries want the computer to do,
this is a valid idea.  Or what do you really think is the difference , 
whether an assembler label starts with A,B or C or even L?


Gerrit
-- 
=^..^=