Displaying 3 results from an estimated 3 matches for "16e3f860".
2013 Jan 14
0
[LLVMdev] [cfe-dev] RFC: Codifying (but not formalizing) the optimization levels in LLVM and Clang
On 1/14/2013 4:57 PM, Chandler Carruth wrote:
>
> I absolutely think that when a function has an optimization attribute,
> that applies to the code in the function and all code inlined into the
> function. If foo calls bar then foo's optimization level should be valid
> for bar, or bar should be marked noinline, or something else.
That's going way too far.
For example, if
2013 Jan 14
2
[LLVMdev] [cfe-dev] RFC: Codifying (but not formalizing) the optimization levels in LLVM and Clang
On Mon, Jan 14, 2013 at 2:21 PM, Krzysztof Parzyszek <
kparzysz at codeaurora.org> wrote:
> On 1/14/2013 3:23 PM, Chandler Carruth wrote:
>
>>
>> This is a great question. My plan would be: inlining doesn't impact the
>> attributes. The inliner will be free to look at both the caller and the
>> callee's attributes to choose the best inlining decision.
2013 Jan 19
3
[LLVMdev] [cfe-dev] RFC: Codifying (but not formalizing) the optimization levels in LLVM and Clang
...this is more of a theoretical invariant. If we discover such a
situation is is likely either invalid code or invalid optimizations, not an
invalid model.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130118/16e3f860/attachment.html>