This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: "--gstabs and certain file names cause assembler error messages"
- To: xinant at cognigine dot com (Xinan Tang)
- Subject: Re: "--gstabs and certain file names cause assembler error messages"
- From: Nick Clifton <nickc at cambridge dot redhat dot com>
- Date: 24 Aug 2001 17:47:21 +0100
- Cc: binutils at sources dot redhat dot com
- References: <3B82C60E.3090603@cognigine.com>
Hi Xinan,
> I am using GNU assembler version 2.10 using BFD version 2.10 and
That is an old version. Can you check to see if the problem still
exists in the latest version (2.11.2).
> if I do:
>
> as mau.s
>
> it runs correctly. However, if I do:
>
> as --gstabs mau.s
>
> it complains:
> ___________________________________________________________
> mau.s: Assembler messages:
> mau.s:7: Error: local label "0" (instance number 0 of a dollar label)
> is not defined
> ______________________________________________
>
> First, the error message is incorrect since there is such a
> label.
Where ? The error message is referring to a special local label
created by the stabs code, not to any label in your source program.
> Second, even though there is an undefined symbol, I do expect the
> linker will report the error not the assembler.
No local labels must be resolved during assembly, their resolution
cannot wait until link time.
> Furthermore, if I change the file name from `mau.s' to `mau_1.s',
> both `as' and `as --gstabs' run correctly and the error disappeared.
This is most strange. Are you running gas under Cygwin by any chance?
This is the only host environment where I have heard of this kind of
thing happening.
Please could you give us more information about your problem. For
example what host and target are involved ? What configure options
were used to build gas ?
Cheers
Nick