[LLVMdev] Problem about "llc -march=msil"

Gordon Henriksen gordonhenriksen at mac.com
Tue May 6 08:51:01 PDT 2008


It probably means that the MSIL backend hasn't been updated with (or  
never had) support for an intrinsic function used in your LLVM module.  
The printed Intrinsic ID identifies the intrinsic, but if you set a  
breakpoint on that line in llc, you should also be able to find its  
name by evaluating an expression like F->getNameStart() in your  
debugger.

On 2008-05-06, at 06:41, Shao-Yin Cheng wrote:

> Hi,
>
> I am trying to use llvm to translate ftp.c(a file of  
> wget-1.11.2.tar.bz2 ) to msil. But it shows errors like:
> [dayin at localhost src]$ llvm-gcc -emit-llvm ftp.c -c -o ftp.bc
> [dayin at localhost src]$ llc ftp.bc -march=msil -o ftp.s
> Intrinsic ID = 32
> llc: /home/dayin/llvm/llvm-2.2/lib/Target/MSIL/MSILWriter.cpp:802:  
> void <unnamed>::MSILWriter::printIntrinsicCall(const  
> llvm::IntrinsicInst*): Assertion `0 && "Invalid intrinsic function"'  
> failed.
> llc((anonymous namespace)::PrintStackTrace()+0x15)[0x8759049]
> /lib/tls/libc.so.6(abort+0xe9)[0x493279]
> /lib/tls/libc.so.6(__assert_fail+0x101)[0x48ad91]
> llc((anonymous  
> namespace)::MSILWriter::printIntrinsicCall(llvm::IntrinsicInst  
> const*)+0xbd)[0x8194db9]
> Aborted
> What does these mean?
>
> And the follow commands work well:
> [dayin at localhost src]$ llc ftp.bc -o ftp.s
> [dayin at localhost src]$ llc ftp.bc -march=c -o ftp.c.s
> [dayin at localhost src]$ llvm-dis ftp.bc –o ftp.ll
>
> Enc. ftp.bc and ftp.ll
>
> Thank you!
> ----------------------------------------------
> Shao-Yin Cheng
> sycheng at ustc.edu.cn
> 2008-4-26
>
> <ftp.ll><ftp.bc>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev



— Gordon

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20080506/6163c545/attachment.html>


More information about the llvm-dev mailing list