llvm dev - May 2017 - clang assembler keeps .Linfo_string symbols?

Hi,

When I use -S to generate an assembly file (ARM target) .Linfo_string 
symbols are generated. I would expect the clang assembler to treat these 
as locals (i.e not appear in the object file) but they do. Using the GNU 
assembler the symbols don't appear in the object file.

Why are .Linfo_string symbols treated differently to other local labels 
by the clang assembler?

Using the integrated clang assembler the symbols don't appear either. Is 
there a command line option to the clang assembler that I'm missing that 
treats these symbols as locals?

Regards
Michael

Can you provide a .s file that shows the difference?

Thanks,
Rafael

Michael Johnson via llvm-dev <llvm-dev at lists.llvm.org> writes:
> Hi,
>
> When I use -S to generate an assembly file (ARM target) .Linfo_string 
> symbols are generated. I would expect the clang assembler to treat these 
> as locals (i.e not appear in the object file) but they do. Using the GNU 
> assembler the symbols don't appear in the object file.
>
> Why are .Linfo_string symbols treated differently to other local labels 
> by the clang assembler?
>
> Using the integrated clang assembler the symbols don't appear either.
Is
> there a command line option to the clang assembler that I'm missing
that
> treats these symbols as locals?
>
> Regards
> Michael
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

On 3 May 2017 at 08:01, Rafael Avila de Espindola via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> Can you provide a .s file that shows the difference?
I managed to reproduce it by compiling 'char *var =
"whatever";' in
debug mode (so clang -target arm-none-eabi tmp.c -g"). Direct compile
leaves no assembler-local strings, but for some reason going via -S
does. I've not investigated further I'm afraid.

Tim.