-
Notifications
You must be signed in to change notification settings - Fork 15.9k
[IR] Support constructing dead_on_return without an argument
#177272
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
Conversation
|
cc @nikic - you just saw rust-lang/rust#151469 which inspired this. |
|
Thank you for submitting a Pull Request (PR) to the LLVM Project! This PR will be automatically labeled and the relevant teams will be notified. If you wish to, you can add reviewers by using the "Reviewers" section on this page. If this is not working for you, it is probably because you do not have write permissions for the repository. In which case you can instead tag reviewers by name in a comment by using If you have received no comments on your PR for a week, you can request a review by "ping"ing the PR by adding a comment “Ping”. The common courtesy "ping" rate is once a week. Please remember that you are asking for valuable time from other developers. If you have further questions, they may be answered by the LLVM GitHub User Guide. You can also ask questions in a comment on this PR, on the LLVM Discord or on the forums. |
|
@llvm/pr-subscribers-llvm-ir Author: Matthew Maurer (maurer) ChangesAfter #171712, Add the additional method Full diff: https://github.com/llvm/llvm-project/pull/177272.diff 2 Files Affected:
diff --git a/llvm/include/llvm/IR/Attributes.h b/llvm/include/llvm/IR/Attributes.h
index ec451f6b08695..534d96d2c46e5 100644
--- a/llvm/include/llvm/IR/Attributes.h
+++ b/llvm/include/llvm/IR/Attributes.h
@@ -212,6 +212,8 @@ class Attribute {
MemoryEffects ME);
LLVM_ABI static Attribute getWithNoFPClass(LLVMContext &Context,
FPClassTest Mask);
+ LLVM_ABI static Attribute getWithDeadOnReturnInfo(LLVMContext &Context,
+ DeadOnReturnInfo DI);
LLVM_ABI static Attribute getWithCaptureInfo(LLVMContext &Context,
CaptureInfo CI);
diff --git a/llvm/lib/IR/Attributes.cpp b/llvm/lib/IR/Attributes.cpp
index f156202ce6775..ccf0248c3dabc 100644
--- a/llvm/lib/IR/Attributes.cpp
+++ b/llvm/lib/IR/Attributes.cpp
@@ -310,6 +310,11 @@ Attribute Attribute::getWithVScaleRangeArgs(LLVMContext &Context,
return get(Context, VScaleRange, packVScaleRangeArgs(MinValue, MaxValue));
}
+Attribute Attribute::getWithDeadOnReturnInfo(LLVMContext &Context,
+ DeadOnReturnInfo DI) {
+ return get(Context, DeadOnReturn, DI.toIntValue());
+}
+
Attribute::AttrKind Attribute::getAttrKindFromName(StringRef AttrName) {
return StringSwitch<Attribute::AttrKind>(AttrName)
#define GET_ATTR_NAMES
|
After llvm#171712, `dead_on_return` takes an optional argument indicating the number of bytes known dead. The existing clang callsite uses the attribute builder interface directly which supports the optional argument through `DeadOnReturnInfo`. However, users constructing the Attribute directly (e.g. `rustc`) were using `Attribute::get` which will now default to providing a 0 value to the optional argument. Add the additional method `Attribute::getWithDeadOnReturnInfo` to allow users which produce explicit `Attribute` values to continue to indicate `dead_on_return` without an argument.
boomanaiden154
left a comment
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.
LGTM.
|
@maurer You need to configure your Github account to use your actual email address for landing commits. Right now it defaults to the Github noreply email. |
|
Email should be valid now. |
|
@maurer Congratulations on having your first Pull Request (PR) merged into the LLVM Project! Your changes will be combined with recent changes from other authors, then tested by our build bots. If there is a problem with a build, you may receive a report in an email or a comment on this PR. Please check whether problems have been caused by your change specifically, as the builds can include changes from many authors. It is not uncommon for your change to be included in a build that fails due to someone else's changes, or infrastructure issues. How to do this, and the rest of the post-merge process, is covered in detail here. If your change does cause a problem, it may be reverted, or you can revert it yourself. This is a normal part of LLVM development. You can fix your changes and open a new PR to merge them again. If you don't get any reports, no action is required from you. Your changes are working as expected, well done! |
…177272) After llvm#171712, `dead_on_return` takes an optional argument indicating the number of bytes known dead. The existing clang callsite uses the attribute builder interface directly which supports the optional argument through `DeadOnReturnInfo`. However, users constructing the Attribute directly (e.g. `rustc`) were using `Attribute::get` which will now default to providing a 0 value to the optional argument. Add the additional method `Attribute::getWithDeadOnReturnInfo` to allow users which produce explicit `Attribute` values to continue to indicate `dead_on_return` without an argument.
…177272) After llvm#171712, `dead_on_return` takes an optional argument indicating the number of bytes known dead. The existing clang callsite uses the attribute builder interface directly which supports the optional argument through `DeadOnReturnInfo`. However, users constructing the Attribute directly (e.g. `rustc`) were using `Attribute::get` which will now default to providing a 0 value to the optional argument. Add the additional method `Attribute::getWithDeadOnReturnInfo` to allow users which produce explicit `Attribute` values to continue to indicate `dead_on_return` without an argument.
After #171712,
dead_on_returntakes an optional argument indicating the number of bytes known dead. The existing clang callsite uses the attribute builder interface directly which supports the optional argument throughDeadOnReturnInfo. However, users constructing the Attribute directly (e.g.rustc) were usingAttribute::getwhich will now default to providing a 0 value to the optional argument.Add the additional method
Attribute::getWithDeadOnReturnInfoto allow users which produce explicitAttributevalues to continue to indicatedead_on_returnwithout an argument.