[LLVMbugs] [Bug 1130] NEW: JIT (x86) produces wrong exception for i8 srem
bugzilla-daemon at cs.uiuc.edu
bugzilla-daemon at cs.uiuc.edu
Wed Jan 24 02:09:49 PST 2007
http://llvm.org/bugs/show_bug.cgi?id=1130
Summary: JIT (x86) produces wrong exception for i8 srem
Product: tools
Version: trunk
Platform: Other
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: lli
AssignedTo: unassignedbugs at nondot.org
ReportedBy: baldrick at free.fr
$ lli f.bc
lli((anonymous namespace)::PrintStackTrace()+0x1a)[0x878977a]
lli((anonymous namespace)::SignalHandler(int)+0x112)[0x8789a40]
[0xb7f04420]
lli(llvm::ExecutionEngine::runFunctionAsMain(llvm::Function*,
std::vector<std::basic_string<char, std::char_traits<char>,
std::allocator<char> >, std::allocator<std::basic_string<char,
std::char_traits<char>, std::allocator<char> > > > const&, char const*
const*)+0x23a)[0x84cc066]
lli(main+0x2ba)[0x83b6056]
/lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xdc)[0xb7c8cebc]
lli[0x83b58e1]
Floating point exception
vs
$ lli -force-interpreter f.bc
-128 rd 1 = 0
The C back-end agrees with lli -force-interpreter (and so do I!).
Running "bugpoint --run-jit f.bc" reduces it a bit.
I send the byte-code in an attachment in a moment.
PS: Probably I should report this for one of the libraries, but
it is not clear where x86 JIT bugs should go.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
More information about the llvm-bugs
mailing list