This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
question about -fno-optimize-static-class-initialization
- From: Per Bothner <per at bothner dot com>
- To: Alexandre Petit-Bianco <apbianco at redhat dot com>
- Cc: java at gcc dot gnu dot org
- Date: Fri, 30 Nov 2001 12:52:45 -0800
- Subject: question about -fno-optimize-static-class-initialization
I'm in the process of changing check-init.c so it also
checks that final variables are definitely unassigned
when assigned, and also use the same framework to check
that final fields are assigned once and once only.
The preliminary "proof-of-concept" implementation seems
to be working, but now I need to fill in the missing pieces.
One big piece is that it appears that the code for
-fno-optimize-static-class-initialization seems to be
conncted with the definitive assignment code, but I
don't understand how. It would no doubt help if I
understood what it means to "optimize the way calls
into the runtime are made to initialize static classes
upon their first use" and how this would impact on
checking for definite assignment. Alex, can you help?
(Btw you're getting an extra copy of this because I
typed the wrong address for the list the first time.)
--
--Per Bothner
per@bothner.com http://www.bothner.com/per/