Ian Lance Taylor writes:
> gcc/testsuite/ChangeLog:
>
> 2013-11-03 Ian Lance Taylor
>
> * g++.dg/ext/sync-4.C: New test.
Tested on m68k-suse-linux and x86_64-suse-linux and installed as obvious.
Andreas.
* g++.dg/ext/sync-4.C: Require sync_long_long_runtime support.
diff --gi
On Mon, Nov 4, 2013 at 1:24 PM, Marc Glisse wrote:
> On Mon, 4 Nov 2013, Ian Lance Taylor wrote:
>
>> 2013-11-04 Ian Lance Taylor
>>
>> * builtins.def (ATTR_NOTHROWCALL_LEAF_LIST): Define.
>> * sync-builtins.def: Use ATTR_NOTHROWCALL_LEAF_LIST for all sync
>> builtins th
> I am seeing a bootstrap failure that seems related: ...
Me too,
Dominique
On Mon, 4 Nov 2013, Ian Lance Taylor wrote:
2013-11-04 Ian Lance Taylor
* builtins.def (ATTR_NOTHROWCALL_LEAF_LIST): Define.
* sync-builtins.def: Use ATTR_NOTHROWCALL_LEAF_LIST for all sync
builtins that take pointers.
* lto-opts.c (lto_write_options): Write -
Ian Lance Taylor wrote:
>On Mon, Nov 4, 2013 at 3:52 AM, Richard Biener
> wrote:
>> On Mon, Nov 4, 2013 at 7:01 AM, Ian Lance Taylor
>wrote:
>>> The middle-end currently marks all the sync builtins as nothrow.
>That
>>> is incorrect for most of them when using -fnon-call-exceptions. The
>>> -fn
On Mon, Nov 4, 2013 at 7:01 AM, Ian Lance Taylor wrote:
> The middle-end currently marks all the sync builtins as nothrow. That
> is incorrect for most of them when using -fnon-call-exceptions. The
> -fnon-call-exceptions option means that instructions that trap may throw
> exceptions. Most of
The middle-end currently marks all the sync builtins as nothrow. That
is incorrect for most of them when using -fnon-call-exceptions. The
-fnon-call-exceptions option means that instructions that trap may throw
exceptions. Most of the sync builtins access memory via pointers passed
by user code.
