Skip to content
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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

glandium
Copy link

@glandium glandium commented Aug 3, 2023

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
  • Required: Issue filed: https://unicode-org.atlassian.net/browse/ICU-22450
  • Required: The PR title must be prefixed with a JIRA Issue number.
  • Required: The PR description must include the link to the Jira Issue, for example by completing the URL in the first checklist item
  • Required: Each commit message must be prefixed with a JIRA Issue number.
  • Issue accepted (done by Technical Committee after discussion)
  • Tests included, if applicable
  • API docs and/or User Guide docs changed or added, if applicable

@CLAassistant
Copy link

CLAassistant commented Aug 3, 2023

CLA assistant check
All committers have signed the CLA.

@yumaoka
Copy link
Member

yumaoka commented Aug 3, 2023

@glandium Can you sign CLA? Otherwise, we cannot look at your changes.

@glandium
Copy link
Author

glandium commented Aug 3, 2023

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.
@jira-pull-request-webhook
Copy link

Hooray! The files in the branch are the same across the force-push. 😃

~ Your Friendly Jira-GitHub PR Checker Bot

@glandium
Copy link
Author

glandium commented Aug 9, 2023

The CLA should be sorted out.

@yumaoka yumaoka removed the cla-needed label Sep 7, 2023
@yumaoka yumaoka self-assigned this Sep 7, 2023
@yumaoka yumaoka self-requested a review September 7, 2023 16:07
Copy link
Member

@yumaoka yumaoka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@glandium
Copy link
Author

Can this be merged?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants