[PATCH] D22205: Update the LangRef description of the 'returned' attribute
Hal Finkel via llvm-commits
llvm-commits at lists.llvm.org
Sun Jul 10 14:47:28 PDT 2016
hfinkel created this revision.
hfinkel added reviewers: majnemer, chandlerc, reames.
hfinkel added a subscriber: llvm-commits.
Herald added a subscriber: mcrosier.
The description of the 'returned' attribute says that it is only used when code-generating the caller. I'd like to make the optimizer smarter about looking through functions with returned arguments (generally, but motivated by my llvm.noalias work). As David pointed out in the review of D22202, the LangRef should be updated to make its expanded uses clearer.
@@ -1060,12 +1060,13 @@
This indicates that the function always returns the argument as its return
- value. This is an optimization hint to the code generator when generating
- the caller, allowing tail call optimization and omission of register saves
- and restores in some cases; it is not checked or enforced when generating
- the callee. The parameter and the function return type must be valid
- operands for the :ref:`bitcast instruction <i_bitcast>`. This is not a
- valid attribute for return values and can only be applied to one parameter.
+ value. This is a hint to the optimizer and code generator used when
+ generating the caller, allowing value propagation, tail call optimization,
+ and omission of register saves and restores in some cases; it is not
+ checked or enforced when generating the callee. The parameter and the
+ function return type must be valid operands for the
+ :ref:`bitcast instruction <i_bitcast>`. This is not a valid attribute for
+ return values and can only be applied to one parameter.
This indicates that the parameter or return pointer is not null. This
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 1312 bytes
Desc: not available
More information about the llvm-commits