[LLVMbugs] [Bug 18549] New: crash with address_space(256)
bugzilla-daemon at llvm.org
bugzilla-daemon at llvm.org
Sun Jan 19 08:46:13 PST 2014
http://llvm.org/bugs/show_bug.cgi?id=18549
Bug ID: 18549
Summary: crash with address_space(256)
Product: clang
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: -New Bugs
Assignee: unassignedclangbugs at nondot.org
Reporter: arigo at tunes.org
CC: llvmbugs at cs.uiuc.edu
Classification: Unclassified
Created attachment 11895
--> http://llvm.org/bugs/attachment.cgi?id=11895&action=edit
Preprocessed source
Attached an example where clang-trunk crashes with an assertion, when compiling
a program that makes heavy use of address_space(256):
SelectionDAGBuilder.cpp:4599: const char*
llvm::SelectionDAGBuilder::visitIntrinsicCall(const llvm::CallInst&, unsigned
int): Assertion
`cast<PointerType>(I.getArgOperand(0)->getType())->getAddressSpace() < 256 &&
cast<PointerType>(I.getArgOperand(1)->getType())->getAddressSpace() < 256 &&
"Unknown address space"
A preliminary guess is that it's a memcpy() inserted automatically by some
earlier pass. All explicit memcpy() in the C source are with "char *" or "void
*" arguments with no address_space.
It always fails for me on Linux 64 when running "clang frame-22da9c.c",
apparently at any "-O" level.
--
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20140119/7352d859/attachment.html>
More information about the llvm-bugs
mailing list