https://llvm.org/bugs/show_bug.cgi?id=23726

            Bug ID: 23726
           Summary: got error when compile c++ code under VS2013
           Product: new-bugs
           Version: trunk
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P
         Component: new bugs
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]
    Classification: Unclassified

Created attachment 14416
  --> https://llvm.org/bugs/attachment.cgi?id=14416&action=edit
testclang.cpp and testclang.sh

1>------ Build started: Project: testclang, Configuration: Release Win32 ------
1>  Basic Block in function '?clear@ios_base@std@@QAEXH_N@Z' does not have
terminator!
1>  label %entry
1>CL : fatal error : error in backend: Broken function found, compilation
aborted!
1>clang-cl.exe : error : clang frontend command failed with exit code 70 (use
-v to see invocation)
1>  clang version 3.7.0 (trunk)
1>  Target: i686-pc-windows-msvc
1>  Thread model: posix
1>  clang-cl.exe: note: diagnostic msg: PLEASE submit a bug report to
http://llvm.org/bugs/ and include the crash backtrace, preprocessed source, and
associated run script.
1>  clang-cl.exe: note: diagnostic msg: 
1>  ********************
1>  
1>  PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
1>  Preprocessed source(s) and associated run script(s) are located at:
1>  clang-cl.exe: note: diagnostic msg:
C:\Users\zhangv6\AppData\Local\Temp\testclang-412e75.cpp
1>  clang-cl.exe: note: diagnostic msg:
C:\Users\zhangv6\AppData\Local\Temp\testclang-412e75.sh
1>  clang-cl.exe: note: diagnostic msg: 
1>  
1>  ********************
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

The version is : LLVM-3.7.0-r238743-win32.exe

-- 
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

Reply via email to