search for: rezy5m1tt3

Displaying 5 results from an estimated 5 matches for "rezy5m1tt3".

RFC: Allow readnone and readonly functions to throw exceptions
2017 Jan 03
2
RFC: Allow readnone and readonly functions to throw exceptions
...tirely > clear w.r.t readonly. However, apparently, they don't imply nothrow. I've > actually always thought they *do* imply it - and said so on-list :-) - but > it looks like GCC itself doesn't interpret them that way. 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 th...
RFC: Allow readnone and readonly functions to throw exceptions
2017 Jan 03
3
RFC: Allow readnone and readonly functions to throw exceptions
...parently, they don't imply nothrow. >> I've >> > actually always thought they *do* imply it - and said so on-list :-) - >> but >> > it looks like GCC itself doesn't interpret them that way. 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 &g...
RFC: Allow readnone and readonly functions to throw exceptions
2017 Jan 05
2
RFC: Allow readnone and readonly functions to throw exceptions
...gt;>>> I've >>>>> actually always thought they *do* imply it - and said so on-list :-) - >>>>> but >>>>> it looks like GCC itself doesn't interpret them that way. 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. >>>> >&g...
RFC: Allow readnone and readonly functions to throw exceptions
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
RFC: Allow readnone and readonly functions to throw exceptions
2017 Jan 05
3
RFC: Allow readnone and readonly functions to throw exceptions
...y always thought they *do* imply it - and said so on-list :-) - >>>>>>> but >>>>>>> it looks like GCC itself doesn't interpret them that way. 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 b...