Displaying 5 results from an estimated 5 matches for "readnone_mayunwind_fn".
2017 Jan 05
3
RFC: Allow readnone and readonly functions to throw exceptions
...zed that there's an annoying corner case to this scheme --
>>> I can't DSE stores across readnone maythrow function calls because the
>>> exception handler could read memory. That is, in:
>>>
>>> try {
>>> *a = 10;
>>> call void @readnone_mayunwind_fn();
>>> *a = 20;
>>> } catch (...) {
>>> assert(*a == 10);
>>> }
>>>
>>> I can't DSE the `*a = 10` store.
>>>
>>> As far as I can tell, the most restrictive memory attribute for a
>>> potentially throwing fu...
2017 Jan 05
6
RFC: Allow readnone and readonly functions to throw exceptions
...scheme --
> I can't DSE stores across readnone maythrow function
> calls because the
> exception handler could read memory. That is, in:
>
> try {
> *a = 10;
> call void @readnone_mayunwind_fn();
> *a = 20;
> } catch (...) {
> assert(*a == 10);
> }
>
> I can't DSE the `*a = 10` store.
>
> As far as I can tell, the most restrictive memory
>...
2017 Jan 05
2
RFC: Allow readnone and readonly functions to throw exceptions
..., Sanjoy Das via llvm-dev wrote:
> I just realized that there's an annoying corner case to this scheme --
> I can't DSE stores across readnone maythrow function calls because the
> exception handler could read memory. That is, in:
>
> try {
> *a = 10;
> call void @readnone_mayunwind_fn();
> *a = 20;
> } catch (...) {
> assert(*a == 10);
> }
>
> I can't DSE the `*a = 10` store.
>
> As far as I can tell, the most restrictive memory attribute for a
> potentially throwing function is readonly. "readnone may-unwind" does
> not make se...
2017 Jan 03
3
RFC: Allow readnone and readonly functions to throw exceptions
On Tue, Jan 3, 2017 at 10:47 AM, Michael Kuperstein via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
>
>
> On Tue, Jan 3, 2017 at 9:59 AM, Sanjoy Das via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
>> Hi Michael,
>>
>> On Mon, Jan 2, 2017 at 11:49 PM, Michael Kuperstein
>> <michael.kuperstein at gmail.com> wrote:
>> > This
2017 Jan 05
2
RFC: Allow readnone and readonly functions to throw exceptions
...tores across readnone maythrow function
>>> calls because the
>>> exception handler could read memory. That is, in:
>>>
>>> try {
>>> *a = 10;
>>> call void @readnone_mayunwind_fn();
>>> *a = 20;
>>> } catch (...) {
>>> assert(*a == 10);
>>> }
>>>
>>> I can't DSE the `*a = 10` store.
>>>
>>> As far...