This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: Object alignment, was: cygwin failures - assertion "!(addr & FLAGS)" failed:
- From: Tom Tromey <tromey at redhat dot com>
- To: Randall R Schulz <rrschulz at cris dot com>
- Cc: "Boehm, Hans" <hans_boehm at hp dot com>, java at gcc dot gnu dot org
- Date: 06 May 2002 15:39:51 -0600
- Subject: Re: Object alignment, was: cygwin failures - assertion "!(addr & FLAGS)" failed:
- References: <5.1.0.14.2.20020506133047.00b04ea8@pop3.cris.com>
- Reply-to: tromey at redhat dot com
>>>>> "Randall" == Randall R Schulz <rrschulz@cris.com> writes:
Randall> Is stack-based object allocation really feasible for Java
Randall> outside of some very narrow special cases (i.e., when the
Randall> reference to the instance can be proved never to propagate
Randall> outside the method in which it's created)?
Only if you do whole program analysis. See the IBM Jalapeno paper on
escape analysis for the details. I suppose it is possible that the
special cases are still interesting.
I doubt gcj will have stack allocation any time soon. As far as I
know nobody is working on it. And my guess is there are easier ways
to get performance boosts, for instance type-based optimization on the
trees.
Tom