DWARF2 only supports one section per compilation unit

[tpimh]

Same warnings as #607 when compiling ARM64 kernel using integrated assembler.

arch/arm64/kernel/vdso/vdso.S:14:2: warning: DWARF2 only supports one section per compilation unit
 .section .rodata
 ^

arch/arm64/kernel/head.S:62:2: warning: DWARF2 only supports one section per compilation unit
 .section ".head.text","ax"
 ^
/tmp/head-9725f8.s:1028:2: warning: DWARF2 only supports one section per compilation unit
 .section ".init.text","ax"
 ^
/tmp/head-9725f8.s:1275:2: warning: DWARF2 only supports one section per compilation unit
 .section ".idmap.text","awx"
 ^
<instantiation>:3:2: warning: DWARF2 only supports one section per compilation unit
 .section ___ksymtab+kimage_vaddr,"a"
 ^
/tmp/head-9725f8.s:1279:1: note: while in macro instantiation
___EXPORT_SYMBOL kimage_vaddr, kimage_vaddr,
^
<instantiation>:8:2: warning: DWARF2 only supports one section per compilation unit
 .section __ksymtab_strings,"a"
 ^
/tmp/head-9725f8.s:1279:1: note: while in macro instantiation
___EXPORT_SYMBOL kimage_vaddr, kimage_vaddr,
^
arch/arm64/kernel/head.S:662:2: warning: DWARF2 only supports one section per compilation unit
 .pushsection ".mmuoff.data.write", "aw"
 ^

<instantiation>:2:2: warning: DWARF2 only supports one section per compilation unit
 .pushsection .altinstructions, "a"
 ^
arch/arm64/mm/cache.S:42:1: note: while in macro instantiation
alternative_if 27
^
<instantiation>:5:2: warning: DWARF2 only supports one section per compilation unit
 .pushsection .altinstr_replacement, "ax"
 ^
arch/arm64/mm/cache.S:42:1: note: while in macro instantiation
alternative_if 27
^
<instantiation>:1:1: warning: DWARF2 only supports one section per compilation unit
.pushsection __ex_table, "a"
^
<instantiation>:5:20: note: while in macro instantiation
9999: ic ivau, x3; _asm_extable 9999b, 9f
                   ^
arch/arm64/mm/cache.S:61:2: note: while in macro instantiation
 invalidate_icache_by_line x0, x1, x2, x3, 9f
 ^

[nickdesaulniers]

@jcai19 so for this, the warning is not wrong but:

1. it's not named, so we can't turn it off explicitly.
2. without .cfi_* directives, I'm not sure that debug sections get created, so who cares about dwarf if we're not emitting debug info? (Maybe we are somehow, and I'm wrong).

[ihalip]

Old proposed fix: https://reviews.llvm.org/D6379

[nickdesaulniers]

Great find! Maybe I can "commandeer" that revision.

[nickdesaulniers]

Jotting down some notes:

1. the top level Makefile sets KBUILD_AFLAGS += -Wa,-gdwarf-2, so all assembly files are assembled in dwarf2 mode.
2. most .s/.S files don't use any assembler directives that would produce dwarf debug sections:
3. for f in $(find arch/ -name \*.S); do grep -l "cfi" $f; done produces 23 files that have any .cfi related directives. I'm not sure if there's other assembler directives other than the many .cfi ones that produce debug info. (More info on cfi directives.
4. the presence of these directives produces .debug_line, .debug_info, .debug_abbrev, .debug_aranges, .debug_str, and .eh_frame (and their .rela equivalents) in .o binaries.
5. without cfi directives, it seems the .debug_line is still produced.
6. these can be dumped with objdump -W foo.o. It seems that llvm-objdump doesn't implement -W :( Also, aarch64-linux-gnu-readelf --debug-dump=line for non cfi assembler files.

[m-gupta]

Chrome OS has moved to dwarf-4 (CONFIG_DEBUG_INFO_DWARF4=y). Does these warnings also trigger for dwarf4 ?

[nickdesaulniers]

No