[windows] work-around a compiler bug with VS 2022 v17.6.0#13071
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
|
Starting build on |
|
Did you have a look if that’s not already fixed in llvm upstream and possibly backport the fix/workaround? |
Yes, but the whole file is completely different |
|
Build failed on ROOT-ubuntu2204/nortcxxmod. |
The |
Fix a crash in root.exe due to a compiler bug with Visual Studio 2022 v17.6.0. The fix works the same way than it is supposed to do, since the (never reached) `default: break;` statement make the function returns `HasREX` anyway. To be reviewed and removed as soon as VS works again.
27fe257 to
e88a2f4
Compare
|
Starting build on |
hahnjo
left a comment
There was a problem hiding this comment.
I updated the monorepo and changed interpreter/llvm/llvm-project.tag, so should be good from that perspective.
I discussed with Bertrand, and this work-around is required to get ROOT compiling with the latest compiler. I think we should do this, even temporarily, until the compiler is fixed.
|
FYI, from the release notes of the last VS update (v17.6.5):
|
Fix a crash in root.exe due to a compiler bug with Visual Studio 2022 v17.6.0. The fix works the same way than it is supposed to do, since the (never reached)
default: break;statement make the function returnsHasREXanyway. To be reviewed and removed as soon as VS works again