[llvm-bugs] [Bug 30836] New: clang frontend command failed due to signal
https://llvm.org/bugs/show_bug.cgi?id=30836 Bug ID: 30836 Summary: clang frontend command failed due to signal Product: clang Version: 3.9 Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P Component: Frontend Assignee: unassignedclangb...@nondot.org Reporter: thomas.mer...@gmx.at CC: llvm-bugs@lists.llvm.org Classification: Unclassified Created attachment 17512 --> https://llvm.org/bugs/attachment.cgi?id=17512&action=edit Crash message plus temporary c and sh files. Compiling of a C program generated by the Seed7 compiler fails. Gcc, visual C and other compilers have no problem compiling this file. Below is the error message from clang. The mentioned files are in the attachment. Wrote crash dump file "C:\Users\tm\AppData\Local\Temp\clang.exe-d2f2f5.dmp" 0x0320086A (0x0869C4F0 0x00A4E3F8 0x76EA140E 0x) 0x01C61FF8 (0x00A4E458 0x0869C4F0 0x0CFA9D70 0x039524A8) 0x01C62087 (0x00A4E550 0x0CD78950 0x7EB1FF30 0x0CFA9D70) 0x01CD232D (0x0869C4F0 0x0122B094 0xC45D57EE 0x) 0x01C65DB5 (0x0122B094 0x0001 0x001E 0x01D71F77) 0x01D73F64 (0x06F80758 0x00A4E780 0x05D0A390 0x0012) 0x01D71F77 (0x0122B094 0x07160B38 0x 0x00ED13B8) 0x01D741F8 (0x00ED13B8 0x0612FD01 0x0612FC98 0x) 0x01D7459E (0x00ED13B8 0x00A4EA28 0xC45D5701 0x) 0x02163B2C (0x0005 0x00E9A250 0x205F5F01 0xC45D57EE) 0x02162F47 (0x00E9B190 0x00E99660 0x00E8BC20 0x00E97F98) 0x031DC281 (0x00EC5358 0x00EFD770 0x 0x00EFDD58) 0x02828F29 (0x00EFD770 0x 0x 0x00E8ED58) 0x023E91AB (0x00E8ED58 0x00E9A9A8 0x00E99FE8 0x023C25CD) clang.exe: error: clang frontend command failed due to signal (use -v to see invocation) clang version 3.9.0 (branches/release_39) Target: i686-pc-windows-msvc Thread model: posix InstalledDir: \\?\c:\Program Files (x86)\LLVM\bin clang.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. clang.exe: note: diagnostic msg: PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT: Preprocessed source(s) and associated run script(s) are located at: clang.exe: note: diagnostic msg: C:\Users\tm\AppData\Local\Temp\tmp_chkset-42ebd7.c clang.exe: note: diagnostic msg: C:\Users\tm\AppData\Local\Temp\tmp_chkset-42ebd7.sh clang.exe: note: diagnostic msg: -- You are receiving this mail because: You are on the CC list for the bug. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 28001] [x86, SSE] recognize min/max FP patterns
https://llvm.org/bugs/show_bug.cgi?id=28001 Sanjay Patel changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #8 from Sanjay Patel --- Should be fixed after: https://reviews.llvm.org/rL285495 Given how many problems we have recognizing min/max (see also https://reviews.llvm.org/D26091 , https://reviews.llvm.org/D26096 ), I wonder why we don't have generic IR intrinsics for these ops... -- You are receiving this mail because: You are on the CC list for the bug. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 30624] [META][X86] Avoid lowering C intrinsics calls to target-specific LLVM IR intrinsics
https://llvm.org/bugs/show_bug.cgi?id=30624 Bug 30624 depends on bug 28001, which changed state. Bug 28001 Summary: [x86, SSE] recognize min/max FP patterns https://llvm.org/bugs/show_bug.cgi?id=28001 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 30837] New: logf function call not auto-vectorizing
https://llvm.org/bugs/show_bug.cgi?id=30837 Bug ID: 30837 Summary: logf function call not auto-vectorizing Product: libraries Version: 3.9 Hardware: PC OS: All Status: NEW Severity: normal Priority: P Component: Loop Optimizer Assignee: unassignedb...@nondot.org Reporter: e...@ericmart.in CC: llvm-bugs@lists.llvm.org Classification: Unclassified Created attachment 17513 --> https://llvm.org/bugs/attachment.cgi?id=17513&action=edit C test case, sh command to invoke clang, and example faulty IR I've written 2 test functions in C that take in a float array x of size n and output float array f(x), where f is either fabsf or logf. The LLVM 3.9 auto-vectorization docs claim that both functions will be vectorized: http://llvm.org/releases/3.9.0/docs/Vectorizers.html#vectorization-of-function-calls When running with "clang -O3 -march=x86-64 -mavx2 -ffast-math test.c -S -emit-llvm", the function calling fabsf is vectorized while the function calling logf is not. This is with clang 3.9, but I've also confirmed the bug exists back to at least clang 3.7. I've also observed that logf calls break vectorization of more complex loops, and I provide the comparison with fabsf as a reduced test case. I've attached the C program, a sh script to invoke clang with correct arguments, and an example LLVM IR file I produced by running on my system. -- You are receiving this mail because: You are on the CC list for the bug. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 30838] New: wrong code at -O3 on x86_64-linux-gnu (in both 32-bit and 64-bit modes)
https://llvm.org/bugs/show_bug.cgi?id=30838
Bug ID: 30838
Summary: wrong code at -O3 on x86_64-linux-gnu (in both 32-bit
and 64-bit modes)
Product: clang
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: s...@cs.ucdavis.edu
CC: llvm-bugs@lists.llvm.org
Classification: Unclassified
Interestingly, although fn2 isn't invoked, removing it seems to hide the bug.
$ clang -v
clang version 4.0.0 (trunk 285491)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/local/clang-trunk/bin
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
$
$ clang -O2 small.c; ./a.out
10
$ clang-3.8 -O3 small.c; ./a.out
10
$
$ clang -O3 small.c; ./a.out
0
$
--
int printf (const char *, ...);
short a, b, *c = &a;
static char d, e = 5;
int f, *g = &f, h, i, j = 6, k;
int fn1 (int p1)
{
for (; j < 7; j++)
if (b || d < 2)
for (; e; e++)
{
*g = 10;
h = *c;
}
return p1;
}
void fn2 ()
{
d++;
}
int main ()
{
int l[1];
for (; k < 1; k++)
if (j)
l[0] = 1;
fn1 (l[0]);
l[i] = 0;
printf ("%d\n", f);
return 0;
}
--
You are receiving this mail because:
You are on the CC list for the bug.
___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
