From: Andrew Haley <aph@redhat.com>
To: "Boehm, Hans" <hans.boehm@hp.com>
Cc: "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 18:43:00 -0000 [thread overview]
Message-ID: <17377.429.589338.838921@zapata.pink> (raw)
In-Reply-To: <65953E8166311641A685BDF71D8658266C1BC4@cacexc12.americas.cpqcorp.net>
Boehm, Hans writes:
> I haven't been following the details here, but some of the suggested
> directions scare me a bit.
>
> The present issue aside, I think we're in general far better off
> allocating collectable memory for anything that interacts with the
> collector, and making the mark descriptors conservative, and eventually
> correct. (If we know that fields will contain either small integers or
> pointers, just allocating it as potentially pointer-containing would
> also currently work fine.) Certainly I think we should be moving in
> that direction.
>
> The code in _Jv_MarkObj that directly traces objects referenced from
> class objects (instead of pushing them on the mark stack) is on very
> thin ice. That's not how mark procedures are supposed to work. In my
> opinion, if we could make it go away, that would be great.
Indeed. I have a patch in the pipeline that causes all objects of
class Class to be properly allocated rather than statically allocated
by the linker. In turn, this has the potential to make _Jv_MarkObj
eventually go away.
Andrew.
next prev parent reply other threads:[~2006-02-01 18:43 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 [this message]
2006-02-01 19:39 ` Bryce McKinlay
2006-02-01 19:44 ` Tom Tromey
2006-02-01 19:56 ` Andrew Haley
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.429.589338.838921@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 \
/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).