public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bernd Schmidt <bernds@codesourcery.com>
To: Nicola Pero <nicola.pero@meta-innovation.com>
Cc: Paul Brook <paul@codesourcery.com>,
	Matthias Klose <doko@ubuntu.com>,  Andrew Haley <aph@redhat.com>,
	gcc-patches@gcc.gnu.org, GCC Java <java@gcc.gnu.org>
Subject: Re: [patch] C6X unwinding/exception handling
Date: Thu, 20 Oct 2011 12:29:00 -0000	[thread overview]
Message-ID: <4EA0140C.50402@codesourcery.com> (raw)
In-Reply-To: <1318860655.826721257@www2.webmail.us>

On 10/17/11 16:10, Nicola Pero wrote:
>>> I checked the attached patch, test results at
>>> http://gcc.gnu.org/ml/gcc-testresults/2011-10/msg01377.html
>>>
>>> which are the same as with my suggested patch.
>>>
>>> Ok for the trunk?
>>
>> I probably don't have authority to approve this, but looks OK to me.
> 
> The libobjc bits are Ok for trunk.

This is just making sure libjava/libobjc match libsupc++, correct? OK if
Andrew doesn't object in the next day or so.


Bernd

      reply	other threads:[~2011-10-20 12:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201108041531.58790.paul@codesourcery.com>
     [not found] ` <201109131348.13087.paul@codesourcery.com>
2011-10-09 11:10   ` Matthias Klose
2011-10-10 10:33     ` Andrew Haley
2011-10-10 11:27       ` Matthias Klose
2011-10-10 12:23         ` Paul Brook
2011-10-17 11:01           ` Matthias Klose
2011-10-17 11:21             ` Andrew Haley
2011-10-17 11:27               ` Matthias Klose
2011-10-17 13:49             ` Paul Brook
2011-10-17 14:11               ` Nicola Pero
2011-10-20 12:29                 ` Bernd Schmidt [this message]

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=4EA0140C.50402@codesourcery.com \
    --to=bernds@codesourcery.com \
    --cc=aph@redhat.com \
    --cc=doko@ubuntu.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=java@gcc.gnu.org \
    --cc=nicola.pero@meta-innovation.com \
    --cc=paul@codesourcery.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).