From: Tom Tromey <tromey@redhat.com>
To: "Boehm, Hans" <hans_boehm@hp.com>
Cc: "'java@gcc.gnu.org'" <java@gcc.gnu.org>
Subject: Re: Gcj build instructions
Date: Fri, 19 Apr 2002 17:10:00 -0000 [thread overview]
Message-ID: <873cxr44hw.fsf@creche.redhat.com> (raw)
In-Reply-To: "Boehm, Hans"'s message of "Fri, 19 Apr 2002 11:30:36 -0700"
>>>>> "Hans" == Boehm, Hans <hans_boehm@hp.com> writes:
Hans> Should the gcj build instructions also mention
Hans> --enable-parallel-mark?
Yes, definitely. Which instructions in particular?
gcc/doc/install.texi? Are there otehrs?
Hans> I haven't done a systematic study with gcj recently, but my
Hans> impression is that it's a substantial win for multiprocessor
Hans> servers, and a mild loss for uniprocessors. I believe it works
Hans> reliably on at least X86 and IA64 Linux. I thought others had
Hans> also used it on other platforms?
If you can dig up the information I'll be happy to write the patch.
Tom
next prev parent reply other threads:[~2002-04-20 0:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-19 11:54 Boehm, Hans
2002-04-19 17:10 ` Tom Tromey [this message]
2002-04-26 23:46 Boehm, Hans
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=873cxr44hw.fsf@creche.redhat.com \
--to=tromey@redhat.com \
--cc=hans_boehm@hp.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).