I tried to report a bug against llvm for not properly handling the
section attribute but they claim that it's not the intention for gcc to
work this way.
I reported it as an X86 problem because it's more generally
understandable to people but actually the problem occurs when mips16
generates stubs for floating point interoperability with mips32.
The gcc documentation ways that the section attribute takes the section
name.
What is the real rule?
Is this "feature" used by other ports except for gcc mips16?
TIA.
Reed
Here is what I reported:
Consider the following code:
void x(int i) __attribute((section(".mySection,\"aw\",@progbits#")));
void x(int i) {
}
If you compile this with gcc you get:
.file "sectbug.c"
.section .mySection,"aw",@progbits#,"ax",@progbits
.globl x
With Clang you get
.file "sectbug.c"
.section ".mySection,\"aw\",@progbits#","ax",@progbits
.globl x
