Displaying 3 results from an estimated 3 matches for "a_readnone_unwind_func".
2017 Jan 05
2
RFC: Allow readnone and readonly functions to throw exceptions
...ce we
> returned normally)
> *a = 30;
>
> and then DSE:
>
> *a = 10;
> call @readnone_may_unwind()
> // *a = 20;
> call @readnone_may_unwind() nounwind // only on this call
> *a = 30;
>
>
>> Also, if I have this:
>>
>> *a = 10;
>> b = a_readnone_unwind_func();
>> *a = 10;
>>
>> I can still conclude that this last store is redundant and can be removed. I
>> know that the readnone function does not touch it, and if it unwinds, than
>> the later store is dead. If I know that &*a has not escaped to where an
>> exc...
2017 Jan 05
2
RFC: Allow readnone and readonly functions to throw exceptions
...gt;> handlers separate from what the function itself might do.
>
> What useful things would you be able to deduce from an “unwind
> readnone” function under these conditions?
It is still only a function of its arguments, so it can be CSE'd.
Also, if I have this:
*a = 10;
b = a_readnone_unwind_func();
*a = 10;
I can still conclude that this last store is redundant and can be
removed. I know that the readnone function does not touch it, and if it
unwinds, than the later store is dead. If I know that &*a has not
escaped to where an exception handler might access it, then I know that...
2017 Jan 05
6
RFC: Allow readnone and readonly functions to throw exceptions
On 01/05/2017 12:17 PM, Reid Kleckner wrote:
> On Thu, Jan 5, 2017 at 9:19 AM, Hal Finkel via llvm-dev
> <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:
>
>
> On 01/05/2017 10:55 AM, Sanjoy Das wrote:
>
> Hi Hal,
>
> On Thu, Jan 5, 2017 at 6:12 AM, Hal Finkel <hfinkel at anl.gov
> <mailto:hfinkel