This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libgcj/13606] need extra runtime verification of compiled code
- From: "tromey at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 10 Aug 2004 21:09:58 -0000
- Subject: [Bug libgcj/13606] need extra runtime verification of compiled code
- References: <20040107190708.13606.tromey@gcc.gnu.org>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From tromey at gcc dot gnu dot org 2004-08-10 21:09 -------
If a class fails a static assertion (e.g., stack overflow in a method),
gcj should not fail outright. Instead it should continue to generate
code which throws a verification failure at the appropriate time.
At least, this is what we want for gcj-jit. Otherwise, if gcj does
exit with a failure, we will just fall back on the bytecode and
uselessly verify it a second time.
This can easily be done by adding an always-fail assertion to the
assertion table. Either a special assert(0), or just assert something
that can't be true, like "Object extends String"
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13606