-
Notifications
You must be signed in to change notification settings - Fork 14.2k
[clang] Implement a bitwise_copyable builtin type trait. #86512
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
34 changes: 34 additions & 0 deletions
34
clang/test/SemaCXX/builtin-is-bitwise-cloneable-fsanitize.cpp
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
// RUN: %clang_cc1 -triple x86_64-unknown-linux -DSANITIZER_ENABLED -fsanitize=address -fsanitize-address-field-padding=1 %s | ||
// RUN: %clang_cc1 -triple x86_64-unknown-linux %s | ||
|
||
struct S { | ||
~S() {} | ||
virtual void foo() {} | ||
|
||
int buffer[1]; | ||
int other_field = 0; | ||
}; | ||
|
||
union U { | ||
S s; | ||
}; | ||
|
||
struct Derived : S {}; | ||
|
||
static_assert(!__is_trivially_copyable(S)); | ||
#ifdef SANITIZER_ENABLED | ||
// Don't allow memcpy when the struct has poisoned padding bits. | ||
// The sanitizer adds posion padding bits to struct S. | ||
static_assert(sizeof(S) > 16); | ||
static_assert(!__is_bitwise_cloneable(S)); | ||
static_assert(sizeof(U) == sizeof(S)); // no padding bit for U. | ||
static_assert(!__is_bitwise_cloneable(U)); | ||
static_assert(!__is_bitwise_cloneable(S[2])); | ||
static_assert(!__is_bitwise_cloneable(Derived)); | ||
#else | ||
static_assert(sizeof(S) == 16); | ||
static_assert(__is_bitwise_cloneable(S)); | ||
static_assert(__is_bitwise_cloneable(U)); | ||
static_assert(__is_bitwise_cloneable(S[2])); | ||
static_assert(__is_bitwise_cloneable(Derived)); | ||
#endif |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,8 @@ | ||
// RUN: %clang_cc1 -fsyntax-only -verify %s | ||
// | ||
struct DynamicClass { virtual int Foo(); }; | ||
static_assert(!__is_trivially_copyable(DynamicClass)); | ||
static_assert(__is_bitwise_cloneable(DynamicClass)); | ||
hokein marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
struct InComplete; // expected-note{{forward declaration}} | ||
static_assert(!__is_bitwise_cloneable(InComplete)); // expected-error{{incomplete type 'InComplete' used in type trait expression}} |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
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 wanted to note that because we aren't caching results of the computations for classes, the running time may end up expontential for some examples.
A synthetic example would be:
I don't think this would matter much in practice, but at least leaving a FIXME for the future would be useful.
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.
Good point, added a FIXME (we could use an extra bit in the class definition class to cache the result).