public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Peter Bergner <bergner@vnet.ibm.com>
To: Torvald Riegel <triegel@redhat.com>,
	       GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Jason Merrill <jason@redhat.com>, Richard Henderson <rth@redhat.com>
Subject: Re: [PATCH] Transactional Memory: Support __cxa_free_exception and fix exception handling.
Date: Thu, 19 Nov 2015 17:18:00 -0000	[thread overview]
Message-ID: <1447953481.4375.6.camel@vnet.ibm.com> (raw)
In-Reply-To: <1447888923.25500.108.camel@localhost.localdomain>

On Thu, 2015-11-19 at 09:35 -0600, Torvald Riegel wrote:
> Tested using the libitm testsuite on x86_64-linux.

Tested on powerpc64le-linux with no regressions and I confirmed
the new eh-5.C test case passes.

Peter


  parent reply	other threads:[~2015-11-19 17:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-18 23:22 Torvald Riegel
2015-11-19 15:40 ` Peter Bergner
2015-11-19 17:18 ` Peter Bergner [this message]
2015-11-19 17:33   ` Torvald Riegel
2015-11-19 17:35     ` Jeff Law
2015-11-19 18:30 ` Jason Merrill

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1447953481.4375.6.camel@vnet.ibm.com \
    --to=bergner@vnet.ibm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jason@redhat.com \
    --cc=rth@redhat.com \
    --cc=triegel@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).