This is the mail archive of the
mailing list for the GCC project.
Re: assembler debug_line support (was Re: [v3] -pedantic-errors vs. extern template)
- From: Gabriel Dos Reis <gdr at codesourcery dot com>
- To: Jason Merrill <jason at redhat dot com>
- Cc: Gabriel Dos Reis <gdr at codesourcery dot com>, David Edelsohn <dje at watson dot ibm dot com>, bkoz at redhat dot com, gcc at gcc dot gnu dot org
- Date: 18 Feb 2002 15:18:04 +0100
- Subject: Re: assembler debug_line support (was Re: [v3] -pedantic-errors vs. extern template)
- Organization: CodeSourcery, LLC
- References: <200202180151.UAA26664@makai.watson.ibm.com> <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org>
Jason Merrill <email@example.com> writes:
| >>>>> "Gabriel" == Gabriel Dos Reis <firstname.lastname@example.org> writes:
| > Jason Merrill <email@example.com> writes:
| > | What does the bad assembly look like?
| > .file 1 "/home/gdr/work/egcs/gcc/libgcc2.c"
| Looks like your assembler doesn't support the dwarf2 directives. configure
| checks for this with 'assembler dwarf2 debug_line support'; can you
| investigate why that test succeeds?
Now that you marked out the problem, I could see the possible source:
1) During configuration, configure determines /usr/bin/as as the
assembler to use:
checking what assembler to use... /usr/bin/as
On my system, that version happens so support dwarf2 directives:
checking assembler dwarf2 debug_line support... yes
2) During building xgcc is invoking the assembler that happens to
come first in my $PATH (here a version I installed in $HOME/bin
long time before my system assembler version becomes newer),
-not- that determined during configuration. That ressembles a
problem encountered when building GCC on Solaris boxes -- where the
So I have two questions:
a) Shouldn't xgcc use the assembler found by configure?
b) Why are xgcc and configure finding different assembler to use?
Thanks for your patience,