[llvm-bugs] [Bug 36225] New: clang crashes on valid code at -O3 on x86_64-linux-gnu: "fatal error: error in backend: Broken function found, compilation aborted!"
via llvm-bugs
llvm-bugs at lists.llvm.org
Sat Feb 3 20:37:49 PST 2018
https://bugs.llvm.org/show_bug.cgi?id=36225
Bug ID: 36225
Summary: clang crashes on valid code at -O3 on
x86_64-linux-gnu: "fatal error: error in backend:
Broken function found, compilation aborted!"
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 324181.
$ clangpolly -v
clang version 7.0.0 (http://llvm.org/git/clang.git
6804b86ee9cc16b8a0dbc7024a497d179e88b4d4) (http://llvm.org/git/llvm.git
616c32878e5655ebddeb0ccbcd508745ec27dede)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /home/su/bin
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/5
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/5.4.0
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/6
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/6.0.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.4
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.3
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5.4.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.0.0
Selected GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5.4.0
Candidate multilib: .;@m64
Candidate multilib: 32;@m32
Candidate multilib: x32;@mx32
Selected multilib: .;@m64
$
$ clangpolly -O2 -c small.c
$
$ clangpolly -O3 -c small.c
PHI node has multiple entries for the same basic block with different incoming
values!
%h.3 = phi i32 [ %spec.select, %for.body3.us ], [ %5, %for.body3.us ], [ 0,
%for.body3 ], [ 0, %for.body3 ]
label %for.body3.us
%5 = select i1 %tobool4.us, i32 0, i32 4
%spec.select = select i1 %tobool4.us, i32 0, i32 4
fatal error: error in backend: Broken function found, compilation aborted!
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
6804b86ee9cc16b8a0dbc7024a497d179e88b4d4) (http://llvm.org/git/llvm.git
616c32878e5655ebddeb0ccbcd508745ec27dede)
Target: x86_64-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-6b6e45.c
clang-6.0: note: diagnostic msg: /tmp/small-6b6e45.sh
clang-6.0: note: diagnostic msg:
********************
$
---------------------------------------
int a, b, c, e;
volatile int d;
void j ()
{
while (a)
{
int f, g;
char h = g = 0;
for (; g < 1; g++)
{
for (f = 0; f < 1; f++)
{
int i;
if (d)
{
if (c)
break;
h = 4;
return;
}
}
if (h < a)
c = b;
}
}
}
--
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/20180204/f002a6dd/attachment.html>
More information about the llvm-bugs
mailing list