Displaying 5 results from an estimated 5 matches for "smf4c9".
2017 Jan 03
2
RFC: Allow readnone and readonly functions to throw exceptions
...E.g. see John
> Regher's example here: https://t.co/REzy5m1tT3
> So there's at least one use-case for possibly throwing readonly/readnone.
One important thing to note then: clang marks const and pure functions
as nounwind *explicitly*. That needs to be fixed.
https://godbolt.org/g/SMF4C9
> As a side note, I'm slightly less optimistic about the amount of required
> code fixes. One thing that comes to mind is that we need to make sure we
> mark all(?) the intrinsics currently marked readonly/argmemonly/readnone as
> nothrow. This should be mostly mechanical, I hope,...
2017 Jan 03
3
RFC: Allow readnone and readonly functions to throw exceptions
...Ezy5m1tT3
>> > So there's at least one use-case for possibly throwing
>> readonly/readnone.
>>
>> One important thing to note then: clang marks const and pure functions
>> as nounwind *explicitly*. That needs to be fixed.
>>
>> https://godbolt.org/g/SMF4C9
>>
>>
> Hah. So it does.
> Eric, this was originally your change. Do I understand GCC's behavior
> incorrectly?
>
No, but I was in the office when Kenny wrote ipa-pure-const, which is the
equivalent to llvm's pass to find function attributions, and it mostly
wasn...
2017 Jan 05
2
RFC: Allow readnone and readonly functions to throw exceptions
...9;s at least one use-case for possibly throwing
>>>>> readonly/readnone.
>>>> One important thing to note then: clang marks const and pure functions
>>>> as nounwind *explicitly*. That needs to be fixed.
>>>>
>>>> https://godbolt.org/g/SMF4C9
>>>>
>>> Hah. So it does.
>>> Eric, this was originally your change. Do I understand GCC's behavior
>>> incorrectly?
>>
>> No, but I was in the office when Kenny wrote ipa-pure-const, which is the
>> equivalent to llvm's pass to find...
2017 Jan 05
3
RFC: Allow readnone and readonly functions to throw exceptions
...hrowing
>>>>>>> readonly/readnone.
>>>>>> One important thing to note then: clang marks const and pure functions
>>>>>> as nounwind *explicitly*. That needs to be fixed.
>>>>>>
>>>>>> https://godbolt.org/g/SMF4C9
>>>>>>
>>>>> Hah. So it does.
>>>>> Eric, this was originally your change. Do I understand GCC's behavior
>>>>> incorrectly?
>>>>
>>>> No, but I was in the office when Kenny wrote ipa-pure-const, which is the...
2017 Jan 03
4
RFC: Allow readnone and readonly functions to throw exceptions
LLVM today does not clearly specify if a function specified to not
write to memory (i.e. readonly or readnone) is allowed to throw
exceptions.
LangRef is ambiguous on this issue. The normative statement is
"[readnone/readonly functions] cannot unwind exceptions by calling the
C++ exception throwing methods" which does not decide an answer for
non C++ languages. It used to say (h/t