Skip to content

Remove libc++ from Tested Standard C++ API Reference #2086

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

Conversation

SergeyKopienko
Copy link
Contributor

@SergeyKopienko SergeyKopienko commented Feb 27, 2025

In this PR we remove libc++ from Tested Standard C++ API Reference
This PR has been made specially for 2022.8 release.

…api.rst - remove libc++ standard library from tested API
@SergeyKopienko SergeyKopienko changed the title Remove libc++ from the list of tested API Remove libc++ from Tested Standard C++ API Reference Feb 27, 2025
timmiesmith
timmiesmith previously approved these changes Feb 27, 2025
Copy link
Contributor

@timmiesmith timmiesmith left a comment

Choose a reason for hiding this comment

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

LGTM. Thank you.

@akukanov
Copy link
Contributor

I would also cherry-pick #2051 - not sure why it is not in the branch.

# Conflicts:
#	documentation/library_guide/api_for_sycl_kernels/tested_standard_cpp_api.rst
@SergeyKopienko
Copy link
Contributor Author

I would also cherry-pick #2051 - not sure why it is not in the branch.

Done.

Copy link
Contributor

@timmiesmith timmiesmith left a comment

Choose a reason for hiding this comment

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

Thanks for the update. LGTM.

@SergeyKopienko SergeyKopienko merged commit d723ac3 into release/2022.8.0 Feb 27, 2025
2 checks passed
@SergeyKopienko SergeyKopienko deleted the dev/skopienko/remove_libc++_from_tested_api_for_2022_8_release branch February 27, 2025 14:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants