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?


git-svn-id: https://svn.apache.org/repos/asf/harmony/enhanced/drlvm/trunk@696636 13f79535-47bb-0310-9956-ffa450edef68
1 file changed
tree: e2c3f8ba40ec7b25f53b0b84182a1ed0929f4fc1
  1. build/
  2. make/
  3. src/
  4. vm/
  5. build.xml
  6. COPYRIGHT
  7. LICENSE
  8. NOTICE
  9. README.txt