Re: [BC] Patch: FYI: verifier -vs- uninitialized types

[Mark Wielaard <mark at klomp dot org>]

Hi,

On Mon, 2004-11-01 at 19:32, Tom Tromey wrote:
> I'm checking this in on the BC branch.
> [...]
> As a practical matter this is important since the Eclipse java
> compiler generates code that violates this constraint.
> [...]
> Index: libjava/ChangeLog
> from  Tom Tromey  <tromey@redhat.com>
> 
> 	* verify.cc (state::check_no_uninitialized_objects): Removed.
> 	(push_jump): Updated.
> 	(push_exception_jump): Likewise.
> 	(handle_ret_insn): Likewise.
> 	(handle_jsr_insn): Likewise.

Would it be OK to check in this patch also on the trunk?
As stated above (and tested by me) it makes eclipse 3.0 work out of the
box (with a rhug compiled xalan). If the BC branch is going to be merged
soon anyway or if it makes merging back the BC branch into the trunk
harder it isn't that important. But it is nice to have this just work on
the trunk.

Cheers,

Mark

Attachment: signature.asc
Description: This is a digitally signed message part