From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Clifton To: xinant@cognigine.com (Xinan Tang) Cc: binutils@sources.redhat.com Subject: Re: "--gstabs and certain file names cause assembler error messages" Date: Fri, 24 Aug 2001 09:50:00 -0000 Message-id: References: <3B82C60E.3090603@cognigine.com> X-SW-Source: 2001-08/msg00565.html 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