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
ICU-22450 Disable the type_info workaround on newer versions of libstdc++ #2539
base: main
Are you sure you want to change the base?
Conversation
@glandium Can you sign CLA? Otherwise, we cannot look at your changes. |
I'm sorting this out through my employer. (an email has been sent to member-services at unicode.org about this. My work email is different than the one in the current commit, though, so I'll update that. |
…dc++ The workaround for http://llvm.org/bugs/show_bug.cgi?id=13364 is related to an ancient version of libstdc++ (4.6). On the flip side, with more recent versions of GCC, the workaround can cause problems under some conditions. The _GLIBCXX_RELEASE macro was introduced in libstdc++ 7, checking for it not being defined to enable the workaround makes it disabled with libstdc++ >= 7, which don't need the workaround in the first place.
Hooray! The files in the branch are the same across the force-push. 😃 ~ Your Friendly Jira-GitHub PR Checker Bot |
The CLA should be sorted out. |
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
Can this be merged? |
The workaround for http://llvm.org/bugs/show_bug.cgi?id=13364 is related to an ancient version of libstdc++ (4.6). On the flip side, with more recent versions of GCC, the workaround can cause problems under some conditions.
The _GLIBCXX_RELEASE macro was introduced in libstdc++ 7, checking for it not being defined to enable the workaround makes it disabled with libstdc++ >= 7, which don't need the workaround in the first place.
Checklist