public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: "Boehm, Hans" <hans.boehm@hp.com>,
	"Bryce McKinlay" <mckinlay@redhat.com>,
	        "Robert Schuster" <theBohemian@gmx.net>,
	<java-patches@gcc.gnu.org>
Subject: Re: FYI: Linker & Verifier fixes (really GC mark procedures)
Date: Wed, 01 Feb 2006 19:56:00 -0000	[thread overview]
Message-ID: <17377.4792.541126.597910@zapata.pink> (raw)
In-Reply-To: <m3k6cedg2c.fsf@localhost.localdomain>

Tom Tromey writes:
 > >>>>> "Andrew" == Andrew Haley <aph@redhat.com> writes:
 > 
 > Andrew> Indeed.  I have a patch in the pipeline that causes all objects of
 > Andrew> class Class to be properly allocated rather than statically allocated
 > Andrew> by the linker.  In turn, this has the potential to make _Jv_MarkObj
 > Andrew> eventually go away.
 > 
 > I did a little work on the gcjx branch in this area.  But it has
 > never been tested.  Anyway the idea was that the compiler could emit
 > real mark descriptors for Class, by special-casing it a bit in
 > boehm.c.
 > 
 > With your work we could just defer this to runtime like we do for
 > interpreted classes.  The goal would be to remove all the
 > Class-specific code from _Jv_MarkObj.

Right.  I've been trying to get this done all year, but I keep getting
sidetracked to fix other things.  Sigh...

But yeah, my plan is to remove almost all knowledge of the shape of an
instance of Class from the compiler, and then the runtime can do
whatever is convenient.  I'm a bit worried that this might result in
long startup times, so I'm going to be cautious -- at least to begin
with.

Andrew.

  reply	other threads:[~2006-02-01 19:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-01 18:22 Boehm, Hans
2006-02-01 18:43 ` Andrew Haley
2006-02-01 19:39   ` Bryce McKinlay
2006-02-01 19:44   ` Tom Tromey
2006-02-01 19:56     ` Andrew Haley [this message]
2006-02-01 20:09       ` Bryce McKinlay
2006-02-02 12:22         ` Andrew Haley
2006-02-03  1:22     ` Tom Tromey
2006-02-03  5:30       ` Hans Boehm
2006-02-03 16:56         ` Tom Tromey
2006-02-03 17:07           ` David Daney
2006-02-03 17:53       ` Bryce McKinlay
2006-02-03 18:09         ` David Daney
2006-02-03 18:12           ` Andrew Haley
2006-02-03 19:38           ` Bryce McKinlay
2006-02-01 19:42 ` Tom Tromey
2006-02-04  1:18 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=17377.4792.541126.597910@zapata.pink \
    --to=aph@redhat.com \
    --cc=hans.boehm@hp.com \
    --cc=java-patches@gcc.gnu.org \
    --cc=mckinlay@redhat.com \
    --cc=theBohemian@gmx.net \
    --cc=tromey@redhat.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).