[LLVMbugs] [Bug 1924] New: Assertion failure at ParseStmt.cpp:983

bugzilla-daemon at cs.uiuc.edu bugzilla-daemon at cs.uiuc.edu
Fri Jan 18 12:14:00 PST 2008


http://llvm.org/bugs/show_bug.cgi?id=1924

           Summary: Assertion failure at ParseStmt.cpp:983
           Product: clang
           Version: unspecified
          Platform: Macintosh
        OS/Version: MacOS X
            Status: NEW
          Severity: normal
          Priority: P2
         Component: parser
        AssignedTo: unassignedbugs at nondot.org
        ReportedBy: brett at python.org
                CC: llvmbugs at cs.uiuc.edu


Created an attachment (id=1342)
 --> (http://llvm.org/bugs/attachment.cgi?id=1342)
Text file with error info as listed in the bug description for easier reading.

[All info mentioned below is in the attached text file for possible easier
reading]

With a checkout of LLVM (r46142) and clang (r46147) I decided to run clang
against a svn checkout of Python (r60021).

With the command-line arguments of::

  find . -name '*.c' -print | xargs /unix/repos/llvm/Debug/bin/clang -I=.
-I=Include -I=$CPPFLAGS -fsyntax-only

>From the top-level directory of a checkout of the trunk, I got the following
error (chopped out the previous warnings so that only the leading reporting
error is show below)::

./Modules/_ctypes/libffi/src/ia64/ffi.c:77:52: error: use of undeclared
identifier 'value'
  asm ("stf.spill %0 = %1%P0" : "=m" (*addr) : "f"(value));
                                                   ^
Assertion failed: (Names.size() == Constraints.size() && Constraints.size() ==
Exprs.size() && "Input operand size mismatch!"), function ParseAsmStatement,
file ParseStmt.cpp, line 983.
0   clang                               0x00228df5
_ZN40_GLOBAL__N_Signals.cpp_00000000_C27D906915PrintStackTraceEv + 45
1   clang                               0x0022919b
_ZN40_GLOBAL__N_Signals.cpp_00000000_C27D906913SignalHandlerEi + 323
2   libSystem.B.dylib                   0x92f2497b _sigtramp + 43
3   ???                                 0xffffffff 0x0 + 4294967295
4   libSystem.B.dylib                   0x92f9d782 raise + 26
5   libSystem.B.dylib                   0x92facd3f abort + 73
6   libSystem.B.dylib                   0x92f9e923 __assert_rtn + 101
7   clang                               0x00106372
_ZN5clang6Parser17ParseAsmStatementEv + 1000
8   clang                               0x00107211
_ZN5clang6Parser27ParseStatementOrDeclarationEb + 1863
9   clang                               0x00106610
_ZN5clang6Parser26ParseCompoundStatementBodyEb + 124
10  clang                               0x00106980
_ZN5clang6Parser26ParseFunctionStatementBodyEPvNS_14SourceLocationES2_ + 26
11  clang                               0x0010a820
_ZN5clang6Parser23ParseFunctionDefinitionERNS_10DeclaratorE + 418
12  clang                               0x0010ac90
_ZN5clang6Parser36ParseDeclarationOrFunctionDefinitionEv + 1122
13  clang                               0x0010ade9
_ZN5clang6Parser24ParseExternalDeclarationEv + 83
14  clang                               0x0010afc5
_ZN5clang6Parser17ParseTopLevelDeclERPv + 61
15  clang                               0x00082ff0
_ZN37_GLOBAL__N__ZN5clang11ASTConsumerD2Ev11ASTStreamer16ReadTopLevelDeclEv +
24
16  clang                               0x00083134
_ZN5clang8ParseASTERNS_12PreprocessorEPNS_11ASTConsumerEb + 258
17  clang                               0x00023134
_ZNSsC1IN9__gnu_cxx17__normal_iteratorIPcSsEEEET_S4_RKSaIcE + 4808
18  clang                               0x000251b9 main + 1315
19  clang                               0x000020c2 start + 54


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



More information about the llvm-bugs mailing list