[llvm-bugs] [Bug 37256] New: clang crashes at -O1 and above in 32-bit mode with debugging enabled: fatal error: error in backend: Found 1 in/out CFI information errors

via llvm-bugs llvm-bugs at lists.llvm.org
Thu Apr 26 09:50:57 PDT 2018


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

            Bug ID: 37256
           Summary: clang crashes at -O1 and above in 32-bit mode with
                    debugging enabled: fatal error: error in backend:
                    Found 1 in/out CFI information errors
           Product: clang
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: -New Bugs
          Assignee: unassignedclangbugs at nondot.org
          Reporter: su at cs.ucdavis.edu
                CC: llvm-bugs at lists.llvm.org

Tested with trunk revision 330807. 

$ clangpolly -v
clang version 7.0.0 (http://llvm.org/git/clang.git
859cc527ff1e5b34c3828766dc830a6e46801945) (llvm/trunk 330807)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /home/su/bin
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/4.9
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/4.9.4
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/5
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/5.3.0
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.4
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.4.7
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.6
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.6.4
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.7
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.7.3
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8.5
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.9
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.9.4
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5.3.0
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/6
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/6.2.0
Selected GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.9
Candidate multilib: .;@m64
Candidate multilib: 32;@m32
Candidate multilib: x32;@mx32
Selected multilib: .;@m64
$
$ clangpolly -m32 -O1 -c -w small.c
$ clangpolly -m32 -O0 -g -c -w small.c
$
$ clangpolly -m32 -O1 -g -c -w small.c
*** Inconsistent CFA register and/or offset between pred and succ ***
Pred: if.then outgoing CFA Reg:4
Pred: if.then outgoing CFA Offset:4
Succ: lor.rhs incoming CFA Reg:4
Succ: lor.rhs incoming CFA Offset:8
fatal error: error in backend: Found 1 in/out CFI information errors.
clang-6.0: error: clang frontend command failed with exit code 70 (use -v to
see invocation)
clang version 7.0.0 (http://llvm.org/git/clang.git
859cc527ff1e5b34c3828766dc830a6e46801945) (llvm/trunk 330807)
Target: i386-unknown-linux-gnu
Thread model: posix
InstalledDir: /home/su/bin
clang-6.0: note: diagnostic msg: PLEASE submit a bug report to
http://llvm.org/bugs/ and include the crash backtrace, preprocessed source, and
associated run script.
clang-6.0: note: diagnostic msg:
********************

PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
clang-6.0: note: diagnostic msg: /tmp/small-f728ca.c
clang-6.0: note: diagnostic msg: /tmp/small-f728ca.sh
clang-6.0: note: diagnostic msg:

********************
$


--------------------------------


int a, b, c, d, f;
volatile int e;

void g ()
{ 
  int *h;
  if (a)
    { 
      int *i;
      (d || (*i = b)) | e;
    }
  int volatile j = f;
  *h = c;
}

-- 
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/20180426/1091b6c7/attachment.html>


More information about the llvm-bugs mailing list