From: Andrew Haley <aph@redhat.com>
To: java-patches@gcc.gnu.org
Subject: Re: libjava patches for RTEMS
Date: Tue, 05 Jul 2011 20:49:00 -0000 [thread overview]
Message-ID: <4E1378D1.5030705@redhat.com> (raw)
In-Reply-To: <CALUNu-p6K34gqVASwMZSAwg_TrUtpXtO21G+bLQkbH6Z5XBBnQ@mail.gmail.com>
On 05/07/11 17:35, Bryce McKinlay wrote:
> On Tue, Jul 5, 2011 at 3:14 PM, Andrew Haley <aph@redhat.com> wrote:
>
>>> As the testsuite result is good enough, I think it's time to get the
>>> patch reviewed and merged into gcc. The patch is attached. :)
>>
>> Ah, 94 failures?
Perhaps, but it would be interesting to know why there are so many
failures, and what they are. If this is the first stage of a work
in progress, that's fine, but I hope that some of these will be fixed.
Andrew.
next prev parent reply other threads:[~2011-07-05 20:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 0:14 Jie Liu
2011-07-05 14:14 ` Andrew Haley
2011-07-05 16:36 ` Bryce McKinlay
2011-07-05 20:49 ` Andrew Haley [this message]
2011-07-08 11:11 ` Jie Liu
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=4E1378D1.5030705@redhat.com \
--to=aph@redhat.com \
--cc=java-patches@gcc.gnu.org \
/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).