In fact, there seems to be a proposal to merge Jacks with Mauve. That would be really neat. I hope it is kept as a separate module within the Mauve CVS repository though, as compiler and runtime testsuites ought to be kept separate, in my opinion.
As an aside, I found that GCJX gives different results (as is to be expected) when run against Jacks and different values for the --source option. For example, the construct Object foo = 1; now seems to be valid due to automatic boxing. Perhaps Jacks should be modified to tailor the status of testcase executions based on the language level targetted by the compiler being tested. Or perhaps it can just target the latest language specification.
Talking of GCJX, a simple clarification I asked for on the GCC mailing list resulted in a big thread - thankfully, the patch I suggested to work around the issue was approved, so that the part of GCC used by GCJX can now be compiled by a C++ compiler once again.
(Originally posted on Advogato.)
|
Tweet |
|
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.