-
Notifications
You must be signed in to change notification settings - Fork 699
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
remove disable flag for RTTI in snappy v1.1.9 #15099
remove disable flag for RTTI in snappy v1.1.9 #15099
Conversation
@boegelbot: please test @ generoso |
Test report by @lexming |
@lexming: Request for testing this PR well received on login1 PR test command '
Test results coming soon (I hope)... - notification for comment with ID 1063017188 processed Message to humans: this is just bookkeeping information for me, |
Test report by @boegelbot |
Test report by @casparvl |
The only thing I was concerned about with this PR is what the reason was that RTTI might have been disabled - if we re-enable it and it was disabled for good reason, we might shoot ourselves in the foot. I did a deep-dive into the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might be good to mention the specific software that hit the RTTI issue. Other than that, looks good to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Going in, thanks @lexming! |
@boegelbot please test @ jsc-zen2 |
@lexming: Request for testing this PR well received on jsczen2l1.int.jsc-zen2.easybuild-test.cluster PR test command '
Test results coming soon (I hope)... - notification for comment with ID 1295042240 processed Message to humans: this is just bookkeeping information for me, |
Test report by @boegelbot |
(created using
eb --new-pr
)Version 1.1.9 of snappy forcefully disables RTTI in GCC, which breaks software still looking for the RTTI symbols. This patch just sets RTTI back to its default.
I hit this issue with dm-reverb v0.7.0 (#15104). However, disabling RTTI will be disruptive in general until all software downstream updates to not rely on
typeinfo
symbols. Rolling back to have RTTI enabled is very safe as it just adds extra symbols, so software programmed for-fno-rtti
should still work, and it is also the default behaviour of GCC.On a side note, it seems that this change was motivated due to issues with Clang, which is not used in this toolchain. See commit google/snappy@c98344f and its parents.