For now, we have not parse section flag Info in asm file. When we emit a section with info flag to asm, then compile asm to obj we will lose the Info flag for the section.
The motivation of this change is ARM64EC's hybmp$x section. If we lose the Info flag MSVC link will report a warning:
warning LNK4078: multiple '.hybmp' sections found with different attributes
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
llvm/test/MC/COFF/section.s | ||
---|---|---|
40 | Is this a section flag that GNU as also supports, or is this flag a new invention (which hopefully doesn’t collide with something elder in GNU as)? |
It looks in llvm-nm, it use "i" for the flag.
https://github.com/llvm/llvm-project/blob/67957368ae9776ec25db80c69f772e40c75ed690/llvm/tools/llvm-nm/llvm-nm.cpp#L941
Can you provider some detail link for that? I try to search IMAGE_SCN_LNK_INFO in git://sourceware.org/git/binutils-gdb.git, but haven't find anything.
Oh, sorry, I got confused. binutils apparently treats "e" as an alias for "n".
"i" doesn't appear to conflict with any existing usage, so should be fine.
llvm/test/MC/COFF/section.s | ||
---|---|---|
40 | How can I configure binutils for Windows to check this? |
llvm/test/MC/COFF/section.s | ||
---|---|---|
40 | Not sure what exactly you're asking, but possible answers:
|
llvm/test/MC/COFF/section.s | ||
---|---|---|
40 | Debian/Ubuntu based linux distros provide binutils targeting mingw in packages named e.g. binutils-mingw-w64-x86-64 (and full toolchains pulled in by e.g. gcc-mingw-w64-x86-64). And you can build binutils yourself with e.g. ../binutils-gdb/configure --target=x86_64-w64-mingw32 --disable-werror --disable-gdb. |
Is this a section flag that GNU as also supports, or is this flag a new invention (which hopefully doesn’t collide with something elder in GNU as)?