-
Notifications
You must be signed in to change notification settings - Fork 13.5k
Reapply "[Clang][Sema] placement new initializes typedef array with correct size (#83124)" #89036
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
Show all changes
8 commits
Select commit
Hold shift + click to select a range
56c2b4f
[Clang][Sema] placement new initializes typedef array with correct si…
mahtohappy bdd7f66
[Clang][Sema] placement new initializes typedef array with correct si…
mahtohappy 71f00c3
Fix test from #83124 and #88902
erichkeane c64cd9d
[Clang][Sema] placement new initializes typedef array with correct size
mahtohappy 1a73ca6
Reapply "[Clang][Sema] placement new initializes typedef array with c…
mahtohappy f95562d
Merge branch 'main' into temp_new
mahtohappy 0f14d8f
Merge branch 'main' into temp_new
mahtohappy c9fbaf3
build trigger
mahtohappy 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
// RUN: %clang --target=x86_64-pc-linux -S -fno-discard-value-names -emit-llvm -o - %s | FileCheck %s | ||
|
||
namespace std { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Tests STILL haven't changed from the original patch. Please add the regression to this test as well. |
||
using size_t = decltype(sizeof(int)); | ||
}; | ||
void* operator new[](std::size_t, void*) noexcept; | ||
|
||
// CHECK: call void @llvm.memset.p0.i64(ptr align 1 %x, i8 0, i64 8, i1 false) | ||
// CHECK: call void @llvm.memset.p0.i64(ptr align 16 %x, i8 0, i64 32, i1 false) | ||
template <typename TYPE> | ||
void f() | ||
{ | ||
typedef TYPE TArray[8]; | ||
|
||
TArray x; | ||
new(&x) TArray(); | ||
} | ||
|
||
template <typename T> | ||
void f1() { | ||
int (*x)[1] = new int[1][1]; | ||
} | ||
template void f1<char>(); | ||
void f2() { | ||
int (*x)[1] = new int[1][1]; | ||
} | ||
|
||
int main() | ||
{ | ||
f<char>(); | ||
f<int>(); | ||
} |
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.
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.
does Value dependence matter?
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.
Yes, it does. Both the original testcase from @slackito and simpler version of @dwblaikie are working now.
normal arrays with new initializer also were passing the check and their type was correct earlier so need for modification for them.
typedef TYPE TArray[8]; TArray x;
here type of array was Tarray which should be Type* so the check only for type dependent case.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.
Note I asked about VALUE dependence, not TYPE dependence. I see why type dependence would matter, but expressions can be both type and value dependent.
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.
No, it doesn't have value dependence.