Ian Lance Taylor i...@google.com writes:
gcc/testsuite/ChangeLog:
2013-11-03 Ian Lance Taylor i...@google.com
* 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
On Mon, Nov 4, 2013 at 7:01 AM, Ian Lance Taylor i...@google.com 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
Ian Lance Taylor i...@google.com wrote:
On Mon, Nov 4, 2013 at 3:52 AM, Richard Biener
richard.guent...@gmail.com wrote:
On Mon, Nov 4, 2013 at 7:01 AM, Ian Lance Taylor i...@google.com
wrote:
The middle-end currently marks all the sync builtins as nothrow.
That
is incorrect for most of them
On Mon, 4 Nov 2013, Ian Lance Taylor wrote:
2013-11-04 Ian Lance Taylor i...@google.com
* 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
I am seeing a bootstrap failure that seems related: ...
Me too,
Dominique
On Mon, Nov 4, 2013 at 1:24 PM, Marc Glisse marc.gli...@inria.fr wrote:
On Mon, 4 Nov 2013, Ian Lance Taylor wrote:
2013-11-04 Ian Lance Taylor i...@google.com
* builtins.def (ATTR_NOTHROWCALL_LEAF_LIST): Define.
* sync-builtins.def: Use ATTR_NOTHROWCALL_LEAF_LIST for all
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
