[llvm-bugs] [Bug 47434] New: clang++ fatal error : error in backend: Do not know how to scalarize the result of this operator!
via llvm-bugs
llvm-bugs at lists.llvm.org
Sat Sep 5 18:15:40 PDT 2020
https://bugs.llvm.org/show_bug.cgi?id=47434
Bug ID: 47434
Summary: clang++ fatal error : error in backend: Do not know
how to scalarize the result of this operator!
Product: new-bugs
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: new bugs
Assignee: unassignedbugs at nondot.org
Reporter: scott.waye at hubse.com
CC: htmldeveloper at gmail.com, llvm-bugs at lists.llvm.org
When compiling some bitcode I'm getting this fatal error
ScalarizeVectorResult #0: t59: v1i32 = rotl t56, t40, BitOperations.cs:366 @[
HashCode.cs:279 ]
EXEC : fatal error : error in backend: Do not know how to scalarize the result
of this operator!
[E:\GitHub\corert\tests\src\Simple\HelloWasm\HelloWasm.csproj]
PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash
backtrace, preprocessed source, and associated run script.
Stack dump:
0. Program arguments: E:/GitHub/emsdk/upstream/bin\clang++.exe -target
wasm32-unknown-emscripten -D__EMSCRIPTEN_major__=2 -D__EMSCRIPTEN_minor__=0
-D__EMSCRIPTEN_tiny__=1 -D_LIBCPP_ABI_VERSION=2 -Dunix -D__unix -D__unix__
-Werror=implicit-function-declaration -Xclang -nostdsysteminc -Xclang
-isystemE:\GitHub\emsdk\upstream\emscripten\system\include\libcxx -Xclang
-isystemE:\GitHub\emsdk\upstream\emscripten\system\lib\libcxxabi\include
-Xclang -isystemE:\GitHub\emsdk\upstream\emscripten\system\include\compat
-Xclang -isystemE:\GitHub\emsdk\upstream\emscripten\system\include -Xclang
-isystemE:\GitHub\emsdk\upstream\emscripten\system\include\libc -Xclang
-isystemE:\GitHub\emsdk\upstream\emscripten\system\lib\libc\musl\arch\emscripten
-Xclang -isystemE:\GitHub\emsdk\upstream\emscripten\system\local\include
-Xclang -isystemE:\GitHub\emsdk\upstream\emscripten\system\include\SSE -Xclang
-isystemE:\GitHub\emsdk\upstream\emscripten\system\lib\compiler-rt\include
-Xclang
-isystemE:\GitHub\emsdk\upstream\emscripten\system\lib\libunwind\include
-Xclang -isystemE:\GitHub\emsdk\upstream\emscripten\cache\wasm\include
-DEMSCRIPTEN -c -o
E:\GitHub\corert\tests\src\Simple\HelloWasm\obj\Release\wasm\native\HelloWasm.o
-O2
E:\GitHub\corert\tests\src\Simple\HelloWasm\obj\Release\wasm\native\HelloWasm.bc
-Xclang -isystemE:\GitHub\emsdk\upstream\emscripten\system\include\SDL -c -o
E:\GitHub\corert\tests\src\Simple\HelloWasm\obj\Release\wasm\native\HelloWasm.o
-mllvm -combiner-global-alias-analysis=false -mllvm
-enable-emscripten-cxx-exceptions -mllvm -enable-emscripten-sjlj -mllvm
-disable-lsr
1. Code generation
2. Running pass 'Function Pass Manager' on module
'E:\GitHub\corert\tests\src\Simple\HelloWasm\obj\Release\wasm\native\HelloWasm.bc'.
3. Running pass 'WebAssembly Instruction Selection' on function
'@S_P_CoreLib_System_HashCode__MixState'
#0 0x00007ffec85b3e49 (C:\WINDOWS\System32\KERNELBASE.dll+0x23e49)
#1 0x00007ff7f389527a (E:\GitHub\emsdk\upstream\bin\clang++.exe+0x10c527a)
#2 0x00007ff7f3867f43 (E:\GitHub\emsdk\upstream\bin\clang++.exe+0x1097f43)
#3 0x00007ff7f27d79a9 (E:\GitHub\emsdk\upstream\bin\clang++.exe+0x79a9)
#4 0x00007ff7f38a9e85 (E:\GitHub\emsdk\upstream\bin\clang++.exe+0x10d9e85)
#5 0x00007ff7f38a9d67 (E:\GitHub\emsdk\upstream\bin\clang++.exe+0x10d9d67)
#6 0x00007ff7f4770812 (E:\GitHub\emsdk\upstream\bin\clang++.exe+0x1fa0812)
#7 0x00007ff7f46c392f (E:\GitHub\emsdk\upstream\bin\clang++.exe+0x1ef392f)
#8 0x00007ff7f46c9dea (E:\GitHub\emsdk\upstream\bin\clang++.exe+0x1ef9dea)
#9 0x00007ff7f450800f (E:\GitHub\emsdk\upstream\bin\clang++.exe+0x1d3800f)
#10 0x00007ff7f45077c5 (E:\GitHub\emsdk\upstream\bin\clang++.exe+0x1d377c5)
#11 0x00007ff7f4506ff4 (E:\GitHub\emsdk\upstream\bin\clang++.exe+0x1d36ff4)
#12 0x00007ff7f4502e8c (E:\GitHub\emsdk\upstream\bin\clang++.exe+0x1d32e8c)
#13 0x00007ff7f2bef070 (E:\GitHub\emsdk\upstream\bin\clang++.exe+0x41f070)
#14 0x00007ff7f2ec47ee (E:\GitHub\emsdk\upstream\bin\clang++.exe+0x6f47ee)
#15 0x00007ff7f31fe119 (E:\GitHub\emsdk\upstream\bin\clang++.exe+0xa2e119)
#16 0x00007ff7f3204c03 (E:\GitHub\emsdk\upstream\bin\clang++.exe+0xa34c03)
#17 0x00007ff7f31fe85d (E:\GitHub\emsdk\upstream\bin\clang++.exe+0xa2e85d)
#18 0x00007ff7f3b91b70 (E:\GitHub\emsdk\upstream\bin\clang++.exe+0x13c1b70)
#19 0x00007ff7f64844e2 (E:\GitHub\emsdk\upstream\bin\clang++.exe+0x3cb44e2)
#20 0x00007ff7f417c515 (E:\GitHub\emsdk\upstream\bin\clang++.exe+0x19ac515)
#21 0x00007ff7f4139d4b (E:\GitHub\emsdk\upstream\bin\clang++.exe+0x1969d4b)
#22 0x00007ff7f41f109b (E:\GitHub\emsdk\upstream\bin\clang++.exe+0x1a2109b)
#23 0x00007ff7f27d75fa (E:\GitHub\emsdk\upstream\bin\clang++.exe+0x75fa)
#24 0x00007ff7f27d4914 (E:\GitHub\emsdk\upstream\bin\clang++.exe+0x4914)
#25 0x00007ff7f40cb1b6 (E:\GitHub\emsdk\upstream\bin\clang++.exe+0x18fb1b6)
#26 0x00007ff7f38950c3 (E:\GitHub\emsdk\upstream\bin\clang++.exe+0x10c50c3)
#27 0x00007ff7f40ca9f3 (E:\GitHub\emsdk\upstream\bin\clang++.exe+0x18fa9f3)
#28 0x00007ff7f3fc77c5 (E:\GitHub\emsdk\upstream\bin\clang++.exe+0x17f77c5)
#29 0x00007ff7f3fc7b6b (E:\GitHub\emsdk\upstream\bin\clang++.exe+0x17f7b6b)
#30 0x00007ff7f3fb38a7 (E:\GitHub\emsdk\upstream\bin\clang++.exe+0x17e38a7)
#31 0x00007ff7f27d42c3 (E:\GitHub\emsdk\upstream\bin\clang++.exe+0x42c3)
#32 0x00007ff7f64ae2f0 (E:\GitHub\emsdk\upstream\bin\clang++.exe+0x3cde2f0)
#33 0x00007ffecaa26fd4 (C:\WINDOWS\System32\KERNEL32.DLL+0x16fd4)
#34 0x00007ffecabbcec1 (C:\WINDOWS\SYSTEM32\ntdll.dll+0x4cec1)
clang++ : error : clang frontend command failed with exit code 70 (use -v to
see invocation) [E:\GitHub\corert\tests\src\Simple\HelloWasm\HelloWasm.csproj]
clang version 12.0.0
(Cswircachegitchromium.googlesource.com-external-github.com-llvm-llvm--project
365f861c45bb504c7b61f64943916fc570818cd1)
Target: wasm32-unknown-emscripten
Thread model: posix
InstalledDir: E:/GitHub/emsdk/upstream/bin
clang++: note: diagnostic msg: Error generating preprocessed source(s) - no
preprocessable inputs.
I'll try and get it in the debugger so I have a change to narrow down which
LLVM IR function is causing the problem.
--
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/20200906/7232178f/attachment.html>
More information about the llvm-bugs
mailing list