http://llvm.org/bugs/show_bug.cgi?id=9858
Summary: targetdata strings starting with "-" causing assertion
failures
Product: libraries
Version: trunk
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P
Component: Target Description Classes
AssignedTo: [email protected]
ReportedBy: [email protected]
CC: [email protected]
The llvm-gcc-x86_64-linux-selfhost and clang-x86_64-linux-selfhost-rel
buildbots, running on osu7, have been failing since 5/2/11:
http://lists.cs.uiuc.edu/pipermail/llvm-testresults/2011-May/032970.html
http://lists.cs.uiuc.edu/pipermail/llvm-testresults/2011-May/032971.html
The symptom is that tests containing targetdata strings beginning with "-",
e.g., "-p:64:64:64", get assertion failures like this:
opt:
/build/buildbot-llvm/clang-x86_64-linux-selfhost-rel/llvm.src/lib/Target/TargetData.cpp:166:
void llvm::TargetData::init(llvm::StringRef): Assertion `!Specifier.empty() &&
"Can't be empty here"' failed.
0 opt 0x000000000091148f
1 opt 0x0000000000911989
2 libpthread.so.0 0x00002b4fe7e86020
3 libc.so.6 0x00002b4fe8a6d415 gsignal + 53
4 libc.so.6 0x00002b4fe8a70690 abort + 384
5 libc.so.6 0x00002b4fe8a665c1 __assert_fail + 241
6 opt 0x00000000007a08bd llvm::TargetData::init(llvm::StringRef) +
1933
7 opt 0x00000000004bf346 main + 2454
8 libc.so.6 0x00002b4fe8a59eed __libc_start_main + 253
9 opt 0x00000000004acaa9
I don't see anything that changes around that time that would cause this, and
we're not seeing it on any other testers, but it would be good to get those
buildbots fixed soon.
--
Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
_______________________________________________
LLVMbugs mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/llvmbugs
