Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
[libc++] Fix the behavior of throwing
operator new
under -fno-exceptions #69498[libc++] Fix the behavior of throwing
operator new
under -fno-exceptions #69498Changes from 9 commits
6f89b11
1b5144f
0f2b77f
82d3e73
3980914
e9863c3
f05c8a3
12e3239
170c592
14fe81e
cf6209a
64b2e5c
f416bf0
d1a0648
609ba8d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
@var-const This is a rare example of a case where I think it makes sense to unconditionally have a
_LIBCPP_ASSERT
-- this should be enabled regardless of the hardening mode IMO. It is similar to when we callstd::__throw_logic_error()
and friends with-fno-exceptions
-- that aborts the program regardless of the hardening mode.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.
I think you're forgetting how hot of a path this is. I don't think we want to be doing anything more than we need in the majority of cases.
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.
We could make this part of the
DEBUG_LITE
mode then, I guess. Would that address your concerns?