forked from llvm/llvm-project
-
Notifications
You must be signed in to change notification settings - Fork 344
Cherry-pick "[Modules] Record whether VarDecl initializers contain side effects (#143739)" #10925
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
ravikandhadai
merged 2 commits into
swiftlang:swift/release/6.2
from
hnrklssn:cherry-pick-vardecl-side-effects
Jun 30, 2025
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
// Tests referencing variable with initializer containing side effect across module boundary | ||
// | ||
// RUN: rm -rf %t | ||
// RUN: mkdir -p %t | ||
// RUN: split-file %s %t | ||
|
||
// RUN: %clang_cc1 -std=c++20 -emit-module-interface %t/Foo.cppm \ | ||
// RUN: -o %t/Foo.pcm | ||
|
||
// RUN: %clang_cc1 -std=c++20 -emit-module-interface \ | ||
// RUN: -fmodule-file=Foo=%t/Foo.pcm \ | ||
// RUN: %t/Bar.cppm \ | ||
// RUN: -o %t/Bar.pcm | ||
|
||
// RUN: %clang_cc1 -std=c++20 -emit-obj \ | ||
// RUN: -main-file-name Bar.cppm \ | ||
// RUN: -fmodule-file=Foo=%t/Foo.pcm \ | ||
// RUN: -x pcm %t/Bar.pcm \ | ||
// RUN: -o %t/Bar.o | ||
|
||
//--- Foo.cppm | ||
export module Foo; | ||
|
||
export { | ||
class S {}; | ||
|
||
inline S s = S{}; | ||
} | ||
|
||
//--- Bar.cppm | ||
export module Bar; | ||
import Foo; | ||
|
||
S bar() { | ||
return s; | ||
} | ||
|
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.
I'd expect this kind of change to also involve an update to
VERSION_MAJOR
, but it seems that doesn't happen much for Clang serialization changes? If it's not needed, that's fine.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 don't know if we've ever written down a policy for this, and we've been inconsistent about it in the past. In general, we don't try to read a pch/module if
getClangFullRepositoryVersion
doesn't match, and we check that in the same record that we checkVERSION_MAJOR
. @Bigcheese or @jansvoboda11 any opinion?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've always treated Clang as needing an exact commit hash match to consider modules as valid. This probably should have updated
VERSION_MAJOR
, but also I don't think it's a problem for us if it doesn't.