public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: Matthias Klose <doko@ubuntu.com>
Cc: NightStrike <nightstrike@gmail.com>,
	Ivan Maidanski <ivmai@mail.ru>,
	       Boehm GC <gc@linux.hpl.hp.com>,
	Kai Tietz <ktietz70@googlemail.com>,
	       GCJ-patches <java-patches@gcc.gnu.org>
Subject: Re: [Gc] Re: boehm-gc merge for GCC
Date: Tue, 20 Nov 2012 16:21:00 -0000	[thread overview]
Message-ID: <50ABADE0.9000305@redhat.com> (raw)
In-Reply-To: <50A6EE27.4000605@ubuntu.com>

On 11/17/2012 01:53 AM, Matthias Klose wrote:
> [CCing java-patches and Andrew too]
> 
> I'm currently striving for something for the 4.8 release. Not sure if relying on
> an external library is the right thing to do for the 4.8 release.

Probably not.

> Currently boehm-gc is linked to libgcj as a convenience library. I remember that
> trying to link boehm-gc as a shared library did cause some performance
> regressions (although I think I did only check this in the early 4.x times).
> 
> Please could you elaborate on the API changes in gcj?
> 
> There is also a second user of boehm-gc in GCC, when you configure with
> --enable-objc-gc. I didn't check yet which changes are needed for that.
> 
> Would it be possible to create a branch in the GCC svn, and then prepare the
> merge, and libjava and libobjc changes there?

Certainly.

Andrew.


  parent reply	other threads:[~2012-11-20 16:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1353097280.505328435@f161.mail.ru>
     [not found] ` <50A67667.7020600@ubuntu.com>
     [not found]   ` <CAF1jjLucRudE2a3gCZq6erkJKfs1nC+DicM+4f4moXJ5HPy9g@mail.gmail.com>
     [not found]     ` <1353099257.140499471@f123.mail.ru>
     [not found]       ` <CAF1jjLsA1nzLaJejMiAfzqZZ8btw37n0B3H7_qz-UrLvNQGqzA@mail.gmail.com>
2012-11-17  1:54         ` Matthias Klose
2012-11-18  7:52           ` NightStrike
2012-11-20 16:21           ` Andrew Haley [this message]
2012-11-26 15:08             ` Matthias Klose

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=50ABADE0.9000305@redhat.com \
    --to=aph@redhat.com \
    --cc=doko@ubuntu.com \
    --cc=gc@linux.hpl.hp.com \
    --cc=ivmai@mail.ru \
    --cc=java-patches@gcc.gnu.org \
    --cc=ktietz70@googlemail.com \
    --cc=nightstrike@gmail.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).