public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: java@gcc.gnu.org
Subject: Re: RFD: Precompile ecj [Was Re: GCCMain not found & test suite errors    fatal?]
Date: Wed, 06 Jan 2010 17:26:00 -0000	[thread overview]
Message-ID: <4B44C7AC.5030809@redhat.com> (raw)
In-Reply-To: <4B44C18E.2020607@caviumnetworks.com>

On 01/06/2010 04:59 PM, David Daney wrote:
> Andrew Haley wrote:
>> This makes ecj1 (and therefore gcj with Java source) much faster but
>> takes 1m30s of CPU on a very fast computer.  It doesn't really seem to
>> make the build longer on a multi-CPU box, since it runs in parallel with
>> the rest of the build AFAICS.  Do you think we can get away with this?
>>
> 
> Seems reasonable to me.
> 
> 
>> Andrew.
>>
>>
>> 2010-01-06  Andrew Haley  <aph@redhat.com>
>>
>> 	* Makefile.am (ecjx_LDFLAGS): Always precompile AWT.
> 
> 
> This changelog mentions AWT.  Is that correct?

Almost certainly not.  :-)

Thanks,
Andrew.

      reply	other threads:[~2010-01-06 17:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-31 17:17 GCCMain not found & test suite errors fatal? John Poole
2010-01-03 16:28 ` Andrew Haley
2010-01-03 18:14   ` John Poole
2010-01-03 18:31     ` Andrew Haley
2010-01-03 18:45       ` John Poole
2010-01-03 19:00         ` Andrew Haley
     [not found]           ` <7230133d1001040328x4557cd0cn8eba6443e8c74616@mail.gmail.com>
2010-01-04 11:41             ` Andrew Haley
2010-01-05  2:43             ` John Poole
2010-01-05 10:17               ` Andrew Haley
2010-01-06 16:39                 ` RFD: Precompile ecj [Was Re: GCCMain not found & test suite errors fatal?] Andrew Haley
2010-01-06 17:01                   ` David Daney
2010-01-06 17:26                     ` Andrew Haley [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=4B44C7AC.5030809@redhat.com \
    --to=aph@redhat.com \
    --cc=java@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).