This is the mail archive of the java-patches@gcc.gnu.org mailing list for the Java project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Why don't *you* add the command line flag after I check in my patch? The patch clearly shows where add the extra logic in enable_assertions.
My patch is an improvement over the current situation, and is designed to support for a future flag can just plug. I might do that, if I feel like it.
It would probably be a code generation flag. How about -fassertions and -fno-assertions or -fenable-assertions and -fdisable-assertions ?
Of course we also need the ability to turn them off at runtime with a flag to the runtime.
I guess you don't read java@gcc.gnu.org. See: http://gcc.gnu.org/ml/java/2004-03/msg00031.html
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |