Re: [libitm] eh specifications are lax

2020-05-12 Thread Jeff Law via Gcc-patches
On Tue, 2020-05-05 at 16:08 -0400, Nathan Sidwell wrote: > I discovered that libitm: > (a) declares __cxa_allocate_exception and friends directly, > (b) doesn't mark them as 'throw()' > (c) doesn't mark the replacment fns _ITM_$foo as nothrow either > > We happen to get away with it because of cod

Re: [libitm] eh specifications are lax

2020-05-11 Thread Nathan Sidwell
ping? On 5/5/20 4:08 PM, Nathan Sidwell wrote: I discovered that libitm: (a) declares __cxa_allocate_exception and friends directly, (b) doesn't mark them as 'throw()' (c) doesn't mark the replacment fns _ITM_$foo as nothrow either We happen to get away with it because of code in the compiler t

[libitm] eh specifications are lax

2020-05-05 Thread Nathan Sidwell
I discovered that libitm: (a) declares __cxa_allocate_exception and friends directly, (b) doesn't mark them as 'throw()' (c) doesn't mark the replacment fns _ITM_$foo as nothrow either We happen to get away with it because of code in the compiler that, although it checks the parameter types, doe