java/2279: Verify bytecode after creating it

[tromey at redhat dot com]

>Number:         2279
>Category:       java
>Synopsis:       Verify bytecode after creating it
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Tue Mar 13 12:26:00 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     Tom Tromey
>Release:        unknown-1.0
>Organization:
>Environment:

>Description:
On more than one occasion we've had bugs in
the bytecode generator which caused verification
errors in not only the JDK verifier but also in
our own.

I think we should change gcj to optionally run
bytecode verification on the bytecode we generate.
That way such bugs will be caught early.

I think we should have a new `-fverify-bytecode'
option which enables this.  This option should 
default to `on' when --enable-checking is used.
Furthermore we should always specify this option
when building libgcj.  (This is important because
we don't actually ever check to make sure that the
`gcj -C' output in the libjava build tree is any
good.)
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: