-
Notifications
You must be signed in to change notification settings - Fork 13.4k
[Clang] Handle structs with inner structs and no fields #89126
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
Changes from all commits
36ddb58
fbb22e6
4c4046f
350550b
d3eda51
dad1c32
1613ce6
f9b3bf3
1b79233
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,40 @@ | ||
// NOTE: Assertions have been autogenerated by utils/update_cc_test_checks.py UTC_ARGS: --version 4 | ||
// RUN: %clang_cc1 -triple x86_64-unknown-linux-gnu -O2 -Wno-missing-declarations -emit-llvm -o - %s | FileCheck %s | ||
|
||
struct foo { | ||
int x,y,z; | ||
struct bar { | ||
int count; | ||
int array[] __attribute__((counted_by(count))); | ||
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. Ideally, we should be able to compute the size here; would need to change the way we compute the "outer" type. Can leave that for a followup, I guess. 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. We can, if handling 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. The only reason foo is relevant in the first place is that getOuterLexicalRecordContext() skips over bar. 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. I see what you mean. I'd like to leave it for a followup, since this change is meant to fix an ICE. |
||
}; | ||
}; | ||
|
||
void init(void * __attribute__((pass_dynamic_object_size(0)))); | ||
|
||
// CHECK-LABEL: define dso_local void @test1( | ||
// CHECK-SAME: ptr noundef [[P:%.*]]) local_unnamed_addr #[[ATTR0:[0-9]+]] { | ||
// CHECK-NEXT: entry: | ||
// CHECK-NEXT: [[ARRAY:%.*]] = getelementptr inbounds i8, ptr [[P]], i64 4 | ||
// CHECK-NEXT: tail call void @init(ptr noundef nonnull [[ARRAY]], i64 noundef -1) #[[ATTR2:[0-9]+]] | ||
// CHECK-NEXT: ret void | ||
// | ||
void test1(struct bar *p) { | ||
init(p->array); | ||
} | ||
|
||
struct mux { | ||
int count; | ||
int array[] __attribute__((counted_by(count))); | ||
}; | ||
|
||
struct bux { struct mux x; }; | ||
|
||
// CHECK-LABEL: define dso_local void @test2( | ||
// CHECK-SAME: ptr noundef [[P:%.*]]) local_unnamed_addr #[[ATTR0]] { | ||
// CHECK-NEXT: entry: | ||
// CHECK-NEXT: tail call void @init(ptr noundef [[P]], i64 noundef -1) #[[ATTR2]] | ||
// CHECK-NEXT: ret void | ||
// | ||
void test2(struct bux *p) { | ||
init(p); | ||
} |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
// NOTE: Assertions have been autogenerated by utils/update_cc_test_checks.py UTC_ARGS: --version 4 | ||
// RUN: %clang_cc1 -triple x86_64-unknown-linux-gnu -O2 -Wall -emit-llvm -o - %s | FileCheck %s | ||
|
||
struct foo { | ||
struct bar { | ||
int array[]; | ||
bar(); | ||
}; | ||
}; | ||
|
||
void init(void * __attribute__((pass_dynamic_object_size(0)))); | ||
|
||
// CHECK-LABEL: define dso_local void @_ZN3foo3barC1Ev( | ||
// CHECK-SAME: ptr noundef nonnull align 4 dereferenceable(1) [[THIS:%.*]]) unnamed_addr #[[ATTR0:[0-9]+]] align 2 { | ||
// CHECK-NEXT: entry: | ||
// CHECK-NEXT: tail call void @_Z4initPvU25pass_dynamic_object_size0(ptr noundef nonnull [[THIS]], i64 noundef -1) #[[ATTR2:[0-9]+]] | ||
// CHECK-NEXT: ret void | ||
// | ||
foo::bar::bar() { | ||
init(array); | ||
} |
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.
Minor question I thought of looking at this one more time for the backport; why are we checking the name of the FieldDecl, instead just checking pointer equality? The caller has a FieldDecl, I think.
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 I did it this way to support searching from either a pointer to the whole struct or pointer to the FAM. I suppose running this when we know we're pointing to the FAM is a bit redundant. And yes, using a
FieldDecl
pointer instead is almost certainly better here.I think what I want to do though is rework some of the code so that we support
__builtin_dynamic_object_size
for more than just pointing to either the FAM or struct. I'll make that change as well.