This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: [patch] Java definite assignment


Alexandre Petit-Bianco <apbianco@cygnus.com> writes:

> Per Bothner writes:
> 
> > Without this patch gcj complains that
> > "Variable `xx' may not have been initialized":
> 
> Any ideas on how we could have
> 
>       String x; try { x = new String (); } finally {} x.toString ();
> 
> not to report a similar error message?

I don't understand your question.  What does the checked-in code
do in this case?  I assume my patch does not change this, since
the change was only in LOOP_EXPR, and there should be no LOOP_EXPR
for your sample code.

If the compiler complains about this code, then there is another,
presumably unrelated bug.
-- 
	--Per Bothner
per@bothner.com   http://www.bothner.com/~per/

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]