[r696636] Workaround for two warnings treated as errors when compiling with
commit858287ae30a2d05d181dacc81a55e09e66ae1344
authorMark Hindess <mark.hindess@googlemail.com>
Thu, 18 Sep 2008 11:31:46 +0000 (18 11:31 +0000)
committerMark Hindess <mark.hindess@googlemail.com>
Thu, 18 Sep 2008 11:31:46 +0000 (18 11:31 +0000)
treed785798290826c7eb6c455e6ab265bdc2a119711
parentb4640e23f61bfe976334c99272a5d6f15f05b036
[r696636] Workaround for two warnings treated as errors when compiling with
the yet-to-be-released gcc-4.4.  The warnings are:

[compile-cc] working_vm/vm/jitrino/src/translator/java/JavaByteCodeTranslator.cpp: In member function 'virtual void Jitrino::JavaByteCodeTranslator::lookupswitch(Jitrino::JavaLookupSwitchTargetsIter*)':
[compile-cc] working_vm/vm/jitrino/src/translator/java/JavaByteCodeTranslator.cpp:1351: error: 'key' may be used uninitialized in this function

[compile-cc] working_vm/vm/jitrino/src/optimizer/abcd/abcd.cpp: In function 'void Jitrino::checkSSA(Jitrino::ControlFlowGraph*)':
[compile-cc] working_vm/vm/jitrino/src/optimizer/abcd/abcd.cpp:423: error: 'checkInst' is used uninitialized in this function
[compile-cc] working_vm/vm/jitrino/src/optimizer/abcd/abcd.cpp:447: note: 'checkInst' was declared here

The first is a false positive.  I've not really looked at the second one.
A less drastic workaround might be a good idea though.  Perhaps using a
gcc #pragma?
make/vm/jitrino.xml