Browse Source

Fix for incorrect BYTE instruction results.

It is actually a LLVM bug workaround.
cl-refactor
Paweł Bylica 10 years ago
parent
commit
1d4ea99453
  1. 4
      libevmjit/Compiler.cpp

4
libevmjit/Compiler.cpp

@ -481,7 +481,9 @@ void Compiler::compileBasicBlock(BasicBlock& _basicBlock, RuntimeManager& _runti
auto idxValid = m_builder.CreateICmpULT(idx, Constant::get(32), "idxValid");
auto bytes = m_builder.CreateBitCast(value, llvm::VectorType::get(Type::Byte, 32), "bytes");
auto byte = m_builder.CreateExtractElement(bytes, idx, "byte");
// Workaround for LLVM bug. Using index of type i256 can produce incorrect results
auto safeIdx = m_builder.CreateZExt(m_builder.CreateTrunc(idx, m_builder.getIntNTy(5)), Type::Size);
auto byte = m_builder.CreateExtractElement(bytes, safeIdx, "byte");
value = m_builder.CreateZExt(byte, Type::Word);
value = m_builder.CreateSelect(idxValid, value, Constant::get(0));
stack.push(value);

Loading…
Cancel
Save