On 10/05/2015 05:00 AM, Andreas Schwab wrote:
Jason Merrill writes:
diff --git a/gcc/testsuite/g++.dg/tm/eh1.C b/gcc/testsuite/g++.dg/tm/eh1.C
new file mode 100644
index 000..1561211
--- /dev/null
+++ b/gcc/testsuite/g++.dg/tm/eh1.C
@@ -0,0 +1,10 @@
+// A handler can involve a transaction-
Jason Merrill writes:
> diff --git a/gcc/testsuite/g++.dg/tm/eh1.C b/gcc/testsuite/g++.dg/tm/eh1.C
> new file mode 100644
> index 000..1561211
> --- /dev/null
> +++ b/gcc/testsuite/g++.dg/tm/eh1.C
> @@ -0,0 +1,10 @@
> +// A handler can involve a transaction-safety conversion.
> +// { dg-do ru
On 10/02/2015 03:06 PM, Torvald Riegel wrote:
On Fri, 2015-10-02 at 14:13 -0400, Jason Merrill wrote:
The patch also doesn't attempt to do anything about the library. The
second patch sets transaction_safe on various built-ins, but without the
library support this just means references to undef
On Fri, 2 Oct 2015, Jason Merrill wrote:
> Since the transaction_safe attribute now affects type identity, I needed to
> change the C front end to allow declarations of built-ins to change whether
> the function is declared transaction_safe. Joseph, is that hunk (copied at
> the bottom) OK?
OK.
On Fri, 2015-10-02 at 14:13 -0400, Jason Merrill wrote:
> The patch also doesn't attempt to do anything about the library. The
> second patch sets transaction_safe on various built-ins, but without the
> library support this just means references to undefined symbols.
For some of the builtins,
This patch implements the front end bits of the transactional memory
technical specification: apart from parsing, that means treating
transaction_safe as part of the type and dealing with conversions,
mangling and such.
Since the transaction_safe attribute now affects type identity, I needed
