Skip to contentSkip to conversation

"Bad or missing .orc_unwind table. Disabling unwinder." Clang 19 problem? 6.12.8 problem?

DISCUSSION Josh Poimboeuf 3 participants 5 messages Jan 13, 2025 – May 29, 2025 2 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): 20250113214122.g4lluwpzj3tnamx3@jpoimboe

#2 lore raw
Quoted 22 lines · Josh Poimboeuf
Quoted 12 lines · Klaus Kusche

Hello,

I've submitted a bug report to kernel bugzilla, but it was closed with a hint that I should contact the maintainers and LKML.

https://bugzilla.kernel.org/show_bug.cgi?id=219685

You are listed as the maintainers for x86 stack unwinding. Any ideas about that problem before I submit it to LKML?

Quoted 6 lines

Is it possibly related to

https://bugzilla.kernel.org/show_bug.cgi?id=219686

which appeared at the same time?
Should it go to the clang maintainers?

Hi Klaus,

Quoted 7 lines

Thanks for reporting it. Indeed it's probably related to the build warning:

vmlinux.o: warning: objtool: start_unlink_intr+0xb7: can't find switch jump table

It's probably a kernel bug, possibly triggered by the new compiler. I'll see if I can recreate.

[adding some folks]

Nathan, I think this is a Clang 19 issue, where one of the jump table entries is pointing past the end of the function. When we saw this in the past I think it was due to some leftover optimization, where the jump table entry ended up unused so it was harmless. Are you aware of any recent bugs in that area?

Maybe objtool should just ignore such entries?

Signature · 1 line
Josh
#3 lore raw

Hi Josh,

Quoted 26 lines · Josh Poimboeuf
Quoted 25 lines · Josh Poimboeuf
Quoted 12 lines · Klaus Kusche

Hello,

I've submitted a bug report to kernel bugzilla, but it was closed with a hint that I should contact the maintainers and LKML.

https://bugzilla.kernel.org/show_bug.cgi?id=219685

You are listed as the maintainers for x86 stack unwinding. Any ideas about that problem before I submit it to LKML?

Quoted 6 lines

Is it possibly related to

https://bugzilla.kernel.org/show_bug.cgi?id=219686

which appeared at the same time?
Should it go to the clang maintainers?

Hi Klaus,

Thanks for reporting it. Indeed it's probably related to the build warning:

Quoted 6 lines
Quoted 4 lines

vmlinux.o: warning: objtool: start_unlink_intr+0xb7: can't find switch jump table

It's probably a kernel bug, possibly triggered by the new compiler. I'll see if I can recreate.

[adding some folks]

Thanks for the CC, there was also an issue filed on our GitHub but I have not had the chance to reply to it yet.

https://github.com/ClangBuiltLinux/linux/issues/2064

Quoted 5 lines

Nathan, I think this is a Clang 19 issue, where one of the jump table entries is pointing past the end of the function. When we saw this in the past I think it was due to some leftover optimization, where the jump table entry ended up unused so it was harmless. Are you aware of any recent bugs in that area?

I am not aware of any recent bugs there but if you or Klaus have a configuration file that triggers this, I would be happy to bisect LLVM to see what change introduced it to give us a better understanding of what is happening here.

Quoted 1 line

Maybe objtool should just ignore such entries?

This may be worth doing, especially in the face of the --Werror flag that is being proposed.

Cheers,
Nathan

#4 lore raw

Hello,

Quoted 8 lines · Nathan Chancellor

Hi Josh,

Quoted 5 lines

Nathan, I think this is a Clang 19 issue, where one of the jump table entries is pointing past the end of the function. When we saw this in the past I think it was due to some leftover optimization, where the jump table entry ended up unused so it was harmless. Are you aware of any recent bugs in that area?

Quoted 4 lines

I am not aware of any recent bugs there but if you or Klaus have a configuration file that triggers this, I would be happy to bisect LLVM to see what change introduced it to give us a better understanding of what is happening here.

Kernel .config files are attached to both

https://bugzilla.kernel.org/show_bug.cgi?id=219685

https://bugzilla.kernel.org/show_bug.cgi?id=219686

Signature · 5 lines
Prof. Dr. Klaus Kusche
Privat: Söllmnitz 32 d, D-07554 Gera/Söllmnitz
036695/859909 [email protected] https://www.computerix.info
Dienstlich: DHGE Gera, Weg der Freundschaft 4, D-07546 Gera
0365/4341-306 [email protected] https://www.dhge.de
#5 lore raw
Quoted 12 lines · Klaus Kusche
Quoted 10 lines · Nathan Chancellor
Quoted 5 lines

Nathan, I think this is a Clang 19 issue, where one of the jump table entries is pointing past the end of the function. When we saw this in the past I think it was due to some leftover optimization, where the jump table entry ended up unused so it was harmless. Are you aware of any recent bugs in that area?

I am not aware of any recent bugs there but if you or Klaus have a configuration file that triggers this, I would be happy to bisect LLVM to see what change introduced it to give us a better understanding of what is happening here.

Quoted 5 lines

Kernel .config files are attached to both

https://bugzilla.kernel.org/show_bug.cgi?id=219685

https://bugzilla.kernel.org/show_bug.cgi?id=219686

Thanks a lot, I missed that since I do not interact with Bugzilla much.

I bisected this change in behavior to LLVM commit 64ed699b3d81 ("Reland "[SimplifyCFG] When only one case value is missing, replace default with that case (#76669)"") [1]. I can see how that would cause this issue but I am not sure how it is specifically interacting with this particular kernel code. I am going to try and tease out a reproducer for this and report it upstream but it would still probably be good to consider if objtool could handle this, especially in the face of the upcoming --Werror.

[1]: https://github.com/llvm/llvm-project/commit/64ed699b3d811407e5a9f1111f63e11dc7f7dd80

Cheers,
Nathan