This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: PATCH partial gcj support for disabling assertion
- From: Tom Tromey <tromey at redhat dot com>
- To: Per Bothner <per at bothner dot com>
- Cc: David Daney <ddaney at avtrex dot com>, gcc-patches at gcc dot gnu dot org, java-patches at gcc dot gnu dot org
- Date: 04 Mar 2004 09:29:49 -0700
- Subject: Re: PATCH partial gcj support for disabling assertion
- References: <404630FA.2090306@bothner.com> <40464D44.3030709@avtrex.com><404654AB.60102@bothner.com>
- Reply-to: tromey at redhat dot com
>>>>> "Per" == Per Bothner <per@bothner.com> writes:
David> I want the enabling and disabling of assertions to be
David> independent of optimization settings.
Per> My patch is an improvement over the current situation, and is designed
Per> to support for a future flag can just plug. I might do that, if I feel
Per> like it.
It is an improvement internally, but to the user it just looks like a
change of defaults. Right now you can't disable assertions, with the
patch you can't enable them with optimization.
javac and jikes support both -source and -target command-line options
to control things like this, plus jikes has the additional --noassert
option to indicate that you don't want asserts regardless of the
version you're targeting. This seems like a good approach to me.
This is just one of several areas where gcj could use a face lift :-(
Tom