[llvm-bugs] Issue 6213 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: SizeInBits != 0 && "invalid zero-sized type"
Comment #3 on issue 6213 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: SizeInBits != 0 && "invalid zero-sized type" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6213#c3 ClusterFuzz has detected this issue as fixed in range 201805160754:201805170725. Detailed report: https://oss-fuzz.com/testcase?key=4922109621960704 Project: llvm Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--aarch64-gisel Fuzz target binary: llvm-isel-fuzzer--aarch64-gisel Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: SizeInBits != 0 && "invalid zero-sized type" llvm::getLLTForType llvm::IRTranslator::getOrCreateVReg Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201712190608:201712210617 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201805160754:201805170725 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4922109621960704 See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 5709 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: Index + MRI->getType(Res).getSizeInBits() <
Comment #3 on issue 5709 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: Index + MRI->getType(Res).getSizeInBits() <= MRI->getType(Src).getSizeInBits() & https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5709#c3 ClusterFuzz has detected this issue as fixed in range 201805160754:201805170725. Detailed report: https://oss-fuzz.com/testcase?key=5647351457775616 Project: llvm Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--aarch64-gisel Fuzz target binary: llvm-isel-fuzzer--aarch64-gisel Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: Index + MRI->getType(Res).getSizeInBits() <= MRI->getType(Src).getSizeInBits() & llvm::MachineIRBuilder::buildExtract llvm::LegalizerHelper::narrowScalar Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710121744:201710130152 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201805160754:201805170725 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5647351457775616 See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 6213 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: SizeInBits != 0 && "invalid zero-sized type"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #4 on issue 6213 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: SizeInBits != 0 && "invalid zero-sized type" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6213#c4 ClusterFuzz testcase 4922109621960704 is verified as fixed, so closing issue as verified. If this is incorrect, please file a bug on https://github.com/google/oss-fuzz/issues/new -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 6461 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: DstSize == 32 && SrcTy.getSizeInBits() == 16 && "unexpected G_INSERT types"
Comment #3 on issue 6461 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: DstSize == 32 && SrcTy.getSizeInBits() == 16 && "unexpected G_INSERT types" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6461#c3 ClusterFuzz has detected this issue as fixed in range 201805160754:201805170725. Detailed report: https://oss-fuzz.com/testcase?key=5762354085101568 Project: llvm Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--aarch64-gisel Fuzz target binary: llvm-isel-fuzzer--aarch64-gisel Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: DstSize == 32 && SrcTy.getSizeInBits() == 16 && "unexpected G_INSERT types" AArch64InstructionSelector::select llvm::InstructionSelect::runOnMachineFunction Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201802180618:201802190622 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201805160754:201805170725 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5762354085101568 See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 5709 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: Index + MRI->getType(Res).getSizeInBits() <
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #4 on issue 5709 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: Index + MRI->getType(Res).getSizeInBits() <= MRI->getType(Src).getSizeInBits() & https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5709#c4 ClusterFuzz testcase 5647351457775616 is verified as fixed, so closing issue as verified. If this is incorrect, please file a bug on https://github.com/google/oss-fuzz/issues/new -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 6461 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: DstSize == 32 && SrcTy.getSizeInBits() == 16 && "unexpected G_INSERT types"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #4 on issue 6461 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: DstSize == 32 && SrcTy.getSizeInBits() == 16 && "unexpected G_INSERT types" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6461#c4 ClusterFuzz testcase 5762354085101568 is verified as fixed, so closing issue as verified. If this is incorrect, please file a bug on https://github.com/google/oss-fuzz/issues/new -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 37514] New: symbols generated for coverage at mingw show incorrect link attributes
https://bugs.llvm.org/show_bug.cgi?id=37514 Bug ID: 37514 Summary: symbols generated for coverage at mingw show incorrect link attributes Product: new-bugs Version: trunk Hardware: PC OS: Windows XP Status: NEW Severity: normal Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: rkasanmasch...@hotmail.com CC: llvm-bugs@lists.llvm.org Created attachment 20316 --> https://bugs.llvm.org/attachment.cgi?id=20316&action=edit sources Compiled LLVM/CLANG head on a current MSYS2/MINGW64 Compiling an advanced production project failed with lots of dublicate symbol errors. For one case I was able to provide an simple example. (code attached) Its a simplification of the scenario of a header defined inline function. There are much more scenarios with the same type of errors. Under my linux system I do not get these errors. clang++ -fprofile-instr-generate -fcoverage-mapping -o llvmbug.exe cu1.cpp cu2.cpp will complain about __profd__Z7inlfuncv defined in both compilation units. By the way there are also errors of not defined symbols lprofGetHostName __llvm_profile_filename I just defined them as described in llvm-sources in my original project to silence them :-) -- 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 37515] New: Compiler crashes in loop vectorizer
https://bugs.llvm.org/show_bug.cgi?id=37515 Bug ID: 37515 Summary: Compiler crashes in loop vectorizer Product: libraries Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: Backend: X86 Assignee: unassignedb...@nondot.org Reporter: santosh.zanju...@amd.com CC: llvm-bugs@lists.llvm.org Created attachment 20317 --> https://bugs.llvm.org/attachment.cgi?id=20317&action=edit test log Small test case/log is attached. I shall try to narrow down the svn revision. -- 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 37516] New: Improve scheduler model documentation
https://bugs.llvm.org/show_bug.cgi?id=37516 Bug ID: 37516 Summary: Improve scheduler model documentation Product: new-bugs Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: llvm-...@redking.me.uk CC: andrea.dibia...@gmail.com, atr...@apple.com, clement.cour...@gmail.com, fil...@gmail.com, florian.h...@arm.com, gchate...@google.com, greg.bedw...@sony.com, javed.ab...@arm.com, llvm-bugs@lists.llvm.org There has been a lot of activity on improving scheduler models recently, but the documentation on explaining how to write a model and how it is used (instruction scheduling, llvm-mca, etc.) is very poor. http://llvm.org/docs/WritingAnLLVMBackend.html#instruction-scheduling We could at least begin by writing up Javed/Florian's "Writing Great Machine Schedulers" tutorial from the 2017 US DevMtg (llvm.org/devmtg/2017-10/). -- 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 37517] New: Assertion `NumReferences == 0 && "Node deleted while references remain"' with -inline -newgvn
https://bugs.llvm.org/show_bug.cgi?id=37517 Bug ID: 37517 Summary: Assertion `NumReferences == 0 && "Node deleted while references remain"' with -inline -newgvn Product: new-bugs Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: mikael.hol...@ericsson.com CC: llvm-bugs@lists.llvm.org Created attachment 20318 --> https://bugs.llvm.org/attachment.cgi?id=20318&action=edit reproducer opt -inline -newgvn -S -o - tr16019.ll gives opt: ../include/llvm/Analysis/CallGraph.h:181: llvm::CallGraphNode::~CallGraphNode(): Assertion `NumReferences == 0 && "Node deleted while references remain"' failed. Stack dump: 0. Program arguments: ../llvm-patch/build-all/bin/opt -inline -newgvn -S -o - tr16019.ll 1. Running pass 'CallGraph Pass Manager' on module 'tr16019.ll'. #0 0x01f911b4 PrintStackTraceSignalHandler(void*) (../llvm-patch/build-all/bin/opt+0x1f911b4) #1 0x01f8f490 llvm::sys::RunSignalHandlers() (../llvm-patch/build-all/bin/opt+0x1f8f490) #2 0x01f91518 SignalHandler(int) (../llvm-patch/build-all/bin/opt+0x1f91518) #3 0x7f8254f23330 __restore_rt (/lib/x86_64-linux-gnu/libpthread.so.0+0x10330) #4 0x7f8253b12c37 gsignal /build/eglibc-ripdx6/eglibc-2.19/signal/../nptl/sysdeps/unix/sysv/linux/raise.c:56:0 #5 0x7f8253b16028 abort /build/eglibc-ripdx6/eglibc-2.19/stdlib/abort.c:91:0 #6 0x7f8253b0bbf6 __assert_fail_base /build/eglibc-ripdx6/eglibc-2.19/assert/assert.c:92:0 #7 0x7f8253b0bca2 (/lib/x86_64-linux-gnu/libc.so.6+0x2fca2) #8 0x0144bc45 (../llvm-patch/build-all/bin/opt+0x144bc45) #9 0x0144c086 std::_Rb_tree > >, std::_Select1st > > >, std::less, std::allocator > > > >::erase(llvm::Function const* const&) (../llvm-patch/build-all/bin/opt+0x144c086) #10 0x0144a905 llvm::CallGraph::removeFunctionFromModule(llvm::CallGraphNode*) (../llvm-patch/build-all/bin/opt+0x144a905) #11 0x01b06c4b llvm::LegacyInlinerBase::removeDeadFunctions(llvm::CallGraph&, bool) (../llvm-patch/build-all/bin/opt+0x1b06c4b) #12 0x0144e576 (anonymous namespace)::CGPassManager::runOnModule(llvm::Module&) (../llvm-patch/build-all/bin/opt+0x144e576) #13 0x01a32c45 llvm::legacy::PassManagerImpl::run(llvm::Module&) (../llvm-patch/build-all/bin/opt+0x1a32c45) #14 0x0073e51c main (../llvm-patch/build-all/bin/opt+0x73e51c) #15 0x7f8253afdf45 __libc_start_main /build/eglibc-ripdx6/eglibc-2.19/csu/libc-start.c:321:0 #16 0x00727b4d _start (../llvm-patch/build-all/bin/opt+0x727b4d) Abort This seems to be old, trying out some old binaries starts crashing around June 22 2017. We don't usually run -newgvn, we found this when doing fuzz testing with random passes. -- 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 37497] [llvm-exegesis] Update docs to cover all command line options
https://bugs.llvm.org/show_bug.cgi?id=37497 cour...@google.com changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #1 from cour...@google.com --- Fixed by https://reviews.llvm.org/D47015. -- 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 37518] New: Merge r329268, r330037 to 6.0.1
https://bugs.llvm.org/show_bug.cgi?id=37518 Bug ID: 37518 Summary: Merge r329268, r330037 to 6.0.1 Product: new-bugs Version: 6.0 Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: simon.dar...@mips.com CC: llvm-bugs@lists.llvm.org -- 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] Issue 3815 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: Crash in llvm::object::WasmObjectFile::parseDataSection
Updates: Labels: Fuzz-Blocker Comment #10 on issue 3815 by ClusterFuzz-External: llvm/llvm-dwarfdump-fuzzer: Crash in llvm::object::WasmObjectFile::parseDataSection https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3815#c10 This crash occurs very frequently on linux platform and is likely preventing the fuzzer llvm-dwarfdump-fuzzer from making much progress. Fixing this will allow more bugs to be found. If this is incorrect, please file a bug on https://github.com/google/oss-fuzz/issues/new -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 37519] New: Merge r324885 to 6.0.1
https://bugs.llvm.org/show_bug.cgi?id=37519 Bug ID: 37519 Summary: Merge r324885 to 6.0.1 Product: new-bugs Version: 6.0 Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: simon.dar...@mips.com CC: llvm-bugs@lists.llvm.org Fixes an UNREACHABLE being triggered in debug and release+asserts builds. -- 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 35359] [GlobalISel][AArch64] Calling convention for HFAs incorrect on big-endian targets
https://bugs.llvm.org/show_bug.cgi?id=35359 Bug 35359 depends on bug 26161, which changed state. Bug 26161 Summary: [GlobalISel] Value to vreg during IR to MachineInstr translation for aggregate type https://bugs.llvm.org/show_bug.cgi?id=26161 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 35360] [GlobalISel][AArch64] Calling convention for vectors incorrect on big-endian targets
https://bugs.llvm.org/show_bug.cgi?id=35360 Bug 35360 depends on bug 26161, which changed state. Bug 26161 Summary: [GlobalISel] Value to vreg during IR to MachineInstr translation for aggregate type https://bugs.llvm.org/show_bug.cgi?id=26161 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 35361] [GlobalISel][AArch64] Calling convention for small arguments passed on stack incorrect on big-endian targets
https://bugs.llvm.org/show_bug.cgi?id=35361 Bug 35361 depends on bug 26161, which changed state. Bug 26161 Summary: [GlobalISel] Value to vreg during IR to MachineInstr translation for aggregate type https://bugs.llvm.org/show_bug.cgi?id=26161 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 26161] [GlobalISel] Value to vreg during IR to MachineInstr translation for aggregate type
https://bugs.llvm.org/show_bug.cgi?id=26161 Amara Emerson changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Amara Emerson --- We now split aggregates into multiple Regs as of r332449. -- 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 37520] New: Merge r322266 to 6.0.1
https://bugs.llvm.org/show_bug.cgi?id=37520 Bug ID: 37520 Summary: Merge r322266 to 6.0.1 Product: new-bugs Version: 6.0 Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: simon.dar...@mips.com CC: llvm-bugs@lists.llvm.org Fixes triggering an UNREACHABLE being triggered instead of an error for a unsupported relocation type. -- 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 37521] New: [X86][AVX512] "getConstant with a uint64_t value that doesn't fit in the type!" in "X86 DAG->DAG Instruction Selection"
https://bugs.llvm.org/show_bug.cgi?id=37521
Bug ID: 37521
Summary: [X86][AVX512] "getConstant with a uint64_t value that
doesn't fit in the type!" in "X86 DAG->DAG Instruction
Selection"
Product: new-bugs
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: ilia.tara...@intel.com
CC: llvm-bugs@lists.llvm.org
This test fails at 'X86 DAG->DAG Instruction Selection' with "getConstant with
a uint64_t value that doesn't fit in the type!" assertion on debug build after
r331792:
= fine.ll==
@a = external global <16 x float>, align 64
declare void @goo(<2 x i256>)
define void @foo() #0 {
%k = bitcast <16 x float>* @a to <2 x i256>*
%1 = load <2 x i256>, <2 x i256>* %k, align 64
call void @goo(<2 x i256> %1)
ret void
}
attributes #0 = { nounwind "target-features"="+avx512bw" }
===
>>> clang -v
clang version 7.0.0 (trunk 332713)
Target: x86_64-unknown-linux-gnu
Thread model: posix
...
>>> llc fine.ll
llc: .../llvm/lib/CodeGen/SelectionDAG/SelectionDAG.cpp:1154: llvm::SDValue
llvm::SelectionDAG::getConstant(uint64_t, const llvm::SDLoc&, llvm::EVT, bool,
bool): Assertion `(EltVT.getSizeInBits() >= 64 || (uint64_t)((int64_t)Val >>
EltVT.getSizeInBits()) + 1 < 2) && "getConstant with a uint64_t value that
doesn't fit in the type!"' failed.
Stack dump:
0. Program arguments: .../debug_build/bin/llc nice.ll
1. Running pass 'Function Pass Manager' on module 'nice.ll'.
2. Running pass 'X86 DAG->DAG Instruction Selection' on function '@foo'
#0 0x037503dd llvm::sys::PrintStackTrace(llvm::raw_ostream&)
.../llvm/lib/Support/Unix/Signals.inc:399:0
#1 0x0375046e PrintStackTraceSignalHandler(void*)
.../llvm/lib/Support/Unix/Signals.inc:463:0
#2 0x0374e954 llvm::sys::RunSignalHandlers()
.../llvm/lib/Support/Signals.cpp:49:0
#3 0x0374fd75 SignalHandler(int)
.../llvm/lib/Support/Unix/Signals.inc:253:0
#4 0x7f1978e345e0 __restore_rt (/lib64/libpthread.so.0+0xf5e0)
#5 0x7f1977a261f7 __GI_raise (/lib64/libc.so.6+0x351f7)
#6 0x7f1977a278e8 __GI_abort (/lib64/libc.so.6+0x368e8)
#7 0x7f1977a1f266 __assert_fail_base (/lib64/libc.so.6+0x2e266)
#8 0x7f1977a1f312 (/lib64/libc.so.6+0x2e312)
#9 0x03559d3f llvm::SelectionDAG::getConstant(unsigned long,
llvm::SDLoc const&, llvm::EVT, bool, bool)
.../llvm/lib/CodeGen/SelectionDAG/SelectionDAG.cpp:1155:0
#10 0x035fbe4b llvm::DAGTypeLegalizer::JoinIntegers(llvm::SDValue,
llvm::SDValue) .../llvm/lib/CodeGen/SelectionDAG/LegalizeTypes.cpp:1079:0
#11 0x036166db
llvm::DAGTypeLegalizer::SplitVecOp_BITCAST(llvm::SDNode*)
.../llvm/lib/CodeGen/SelectionDAG/LegalizeVectorTypes.cpp:1731:0
#12 0x03615174
llvm::DAGTypeLegalizer::SplitVectorOperand(llvm::SDNode*, unsigned int)
.../llvm/lib/CodeGen/SelectionDAG/LegalizeVectorTypes.cpp:1536:0
#13 0x035f7b93 llvm::DAGTypeLegalizer::run()
.../llvm/lib/CodeGen/SelectionDAG/LegalizeTypes.cpp:329:0
#14 0x035fcd1f llvm::SelectionDAG::LegalizeTypes()
.../llvm/lib/CodeGen/SelectionDAG/LegalizeTypes.cpp:1195:0
#15 0x035a6429 llvm::SelectionDAGISel::CodeGenAndEmitDAG()
.../llvm/lib/CodeGen/SelectionDAG/SelectionDAGISel.cpp:769:0
#16 0x035a59b4
llvm::SelectionDAGISel::SelectBasicBlock(llvm::ilist_iterator, false, true>,
llvm::ilist_iterator, false, true>, bool&)
.../llvm/lib/CodeGen/SelectionDAG/SelectionDAGISel.cpp:668:0
#17 0x035ab8ac
llvm::SelectionDAGISel::SelectAllBasicBlocks(llvm::Function const&)
.../llvm/lib/CodeGen/SelectionDAG/SelectionDAGISel.cpp:1736:0
#18 0x035a4694
llvm::SelectionDAGISel::runOnMachineFunction(llvm::MachineFunction&)
.../llvm/lib/CodeGen/SelectionDAG/SelectionDAGISel.cpp:470:0
#19 0x023b3bbe (anonymous
namespace)::X86DAGToDAGISel::runOnMachineFunction(llvm::MachineFunction&)
.../llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:177:0
#20 0x02b507ef
llvm::MachineFunctionPass::runOnFunction(llvm::Function&)
.../llvm/lib/CodeGen/MachineFunctionPass.cpp:62:0
#21 0x02fbb8c8 llvm::FPPassManager::runOnFunction(llvm::Function&)
.../llvm/lib/IR/LegacyPassManager.cpp:1520:0
#22 0x02fbba5b llvm::FPPassManager::runOnModule(llvm::Module&)
.../llvm/lib/IR/LegacyPassManager.cpp:1541:0
#23 0x02fbbde7 (anonymous
namespace)::MPPassManager::runOnModule(llvm::Module&)
.../llvm/lib/IR/LegacyPassManager.cpp:1597:0
#24 0x02fbc4d8 llvm::legacy::PassManagerImpl::run(llvm::Module&)
.../llvm/lib/IR/LegacyPassManager.cpp:1700:0
#25 0x02fbc719 llvm::legacy::PassManager::run(llvm::Module&)
.../llvm/lib/IR/LegacyPassManager.cpp:1732:0
#26 0x01461d6f compileModule(char**, llvm::LLVMContext&)
.../llvm/tools/llc/llc.cpp:575:0
[llvm-bugs] [Bug 36484] Assertion failure with GVNHoist: Assertion `MSSA->dominates(NewDef, FirstDef) && "Should have dominated the new access"' failed.
https://bugs.llvm.org/show_bug.cgi?id=36484 Eli Friedman changed: 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 37499] [AVX512] LLVM ERROR: Cannot select: v8i16 = vselect v8i16, v8i16, v8i16
https://bugs.llvm.org/show_bug.cgi?id=37499 Craig Topper changed: What|Removed |Added Status|NEW |RESOLVED Fixed By Commit(s)||r332743 Resolution|--- |FIXED --- Comment #3 from Craig Topper --- Fixed in r332743 -- 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 37523] New: MemorySanitizer false positive in divide-by-undef
https://bugs.llvm.org/show_bug.cgi?id=37523
Bug ID: 37523
Summary: MemorySanitizer false positive in divide-by-undef
Product: libraries
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Miscellaneous Instrumentation passes
Assignee: unassignedb...@nondot.org
Reporter: eugeni.stepa...@gmail.com
CC: llvm-bugs@lists.llvm.org
#include
#include
int main() {
volatile int scale = 5;
auto zz = _mm_div_ps(_mm_set1_ps(255), _mm_set1_ps(scale));
__msan_print_shadow(&zz, sizeof(zz));
}
Until recently, it was represented like this in the IR:
%vecinit.i = insertelement <4 x float> undef, float %conv, i32 0
%vecinit3.i = shufflevector <4 x float> %vecinit.i, <4 x float> undef, <4 x
i32> zeroinitializer
%div.i = fdiv <4 x float> , %vecinit3.i
The something changed, and now we fill the first lane only, divide, and then
broadcast:
%vecinit.i = insertelement <4 x float> undef, float %conv, i32 0
%0 = fdiv <4 x float> , %vecinit.i
%1 = shufflevector <4 x float> %0, <4 x float> undef, <4 x i32>
zeroinitializer
This in effect divides undef by undef and throws away the result.
MSan instruments division with a strict check for the divisor's shadow,
assuming that division by an uninitialized value may trap. This is not aligned
with IR semantics: LangRef describes fdiv as side effect free.
MSan should delay the check until the value is actually used (or not, like in
this case) by combining and propagating shadow.
--
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 37508] Clang parsing the header file in spite of not finding it
https://bugs.llvm.org/show_bug.cgi?id=37508 David Blaikie changed: What|Removed |Added Resolution|--- |INVALID Status|NEW |RESOLVED CC||dblai...@gmail.com --- Comment #1 from David Blaikie --- Yep, this is intended behavior. Whenever Clang emits a suggested fix on a warning or error, it will continue as though the fix is what was originally written - this way, if the user fixes it the same way the compiler guessed, they can continue reading the rest of the compiler diagnostic output and addressing those issues as well. -- 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 36911] [X86] Add scheduler classes that account for GPR<->XMM transfers
https://bugs.llvm.org/show_bug.cgi?id=36911 Simon Pilgrim changed: What|Removed |Added Resolution|--- |FIXED Fixed By Commit(s)||332745 Status|NEW |RESOLVED --- Comment #1 from Simon Pilgrim --- Fixed in rL332745 -- 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 36908] [meta][x86] Improve scheduler classes instruction coverage
https://bugs.llvm.org/show_bug.cgi?id=36908 Bug 36908 depends on bug 36911, which changed state. Bug 36911 Summary: [X86] Add scheduler classes that account for GPR<->XMM transfers https://bugs.llvm.org/show_bug.cgi?id=36911 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 37131] [X86] Review current scheduler classes to minimise need for InstRW overrides
https://bugs.llvm.org/show_bug.cgi?id=37131 Bug 37131 depends on bug 36911, which changed state. Bug 36911 Summary: [X86] Add scheduler classes that account for GPR<->XMM transfers https://bugs.llvm.org/show_bug.cgi?id=36911 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 37524] New: the relocation type is changed to R_X86_64_32 for .gcc_except_table with -mcmodel=kernel
https://bugs.llvm.org/show_bug.cgi?id=37524
Bug ID: 37524
Summary: the relocation type is changed to R_X86_64_32 for
.gcc_except_table with -mcmodel=kernel
Product: clang
Version: 6.0
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: Frontend
Assignee: unassignedclangb...@nondot.org
Reporter: pan...@gmail.com
CC: llvm-bugs@lists.llvm.org
Use clang 6.0.0.1 to compile this simple code, the relocation for
.gcc_except_table is R_X86_64_32:
$ cat x.cpp
int main () {
try
{
throw 20;
}
catch (int e)
{
}
return 0;
}
$ clang --target=x86_64 -m64 -mcmodel=kernel -c x.cpp
$ $ objdump -Dr x.o|grep .gcc_except_table
Disassembly of section .gcc_except_table:
31: R_X86_64_32 .gcc_except_table
But if use clang 5.0.0.3 to compile the same code, the relocaction type is
R_X86_64_64 for .gcc_except_table.
Is the difference between 5.0.0.3 and 6.0.0.1 expected? or a problem we should
fix?
--
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 37430] [AVX512] Crash in LiveVariables
https://bugs.llvm.org/show_bug.cgi?id=37430 Keno Fischer changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #1 from Keno Fischer --- Fixed by rL332680. -- 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 37396] [AVX512] Incorrect register argument to test instruction
https://bugs.llvm.org/show_bug.cgi?id=37396 Keno Fischer changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #2 from Keno Fischer --- Fixed by rL332682. -- 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 37525] New: Merge rL332302, rL332680, rL332682, rL332694 into 6.0.1
https://bugs.llvm.org/show_bug.cgi?id=37525 Bug ID: 37525 Summary: Merge rL332302, rL332680, rL332682, rL332694 into 6.0.1 Product: new-bugs Version: 6.0 Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: tstel...@redhat.com Reporter: k...@alumni.harvard.edu CC: craig.top...@gmail.com, llvm-bugs@lists.llvm.org, matthew.arsena...@amd.com Blocks: 36649 Please merge the following revisions into 6.0.1. They fix crashing bugs in the julia test suite after the upgrade to LLVM 6.0: rL332302 [InstCombine] fix crash due to ignored addrspacecast (Reviewer: arsenm) rL332680 [X86DomainReassignment] Don't delete IMPLICIT_DEF nodes (Reviewer: craig.topper) rL332682 [X86DomainReassignment] Don't compare stack-allocated values by address (Reviewer: craig.topper) rL332694 [X86DomainReassignment] Hopefully fix buildbot failure (no reviewer, but just a typo fix in the test case for the previous one - can be squashed into that for the cherry-pick) Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=36649 [Bug 36649] [meta] 6.0.1 Release Blockers -- 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 37523] MemorySanitizer false positive in divide-by-undef
https://bugs.llvm.org/show_bug.cgi?id=37523 Evgenii Stepanov changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Evgenii Stepanov --- http://llvm.org/viewvc/llvm-project?view=revision&revision=332761 -- 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 33425] dynamic_cast from one virtual base to another produces the wrong answer
https://bugs.llvm.org/show_bug.cgi?id=33425 Eric Fiselier changed: What|Removed |Added CC||e...@efcs.ca Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Eric Fiselier --- Fixed in r332763. -- 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 33487] dynamic_cast to ambiguous derived class produces the wrong answer
https://bugs.llvm.org/show_bug.cgi?id=33487 Eric Fiselier changed: What|Removed |Added CC||e...@efcs.ca Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #3 from Eric Fiselier --- Fixed in r332763. -- 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 37520] Merge r322266 to 6.0.1
https://bugs.llvm.org/show_bug.cgi?id=37520 Tom Stellard changed: What|Removed |Added Status|NEW |RESOLVED Fixed By Commit(s)|r322266 |r322266 r332765 Resolution|--- |FIXED --- Comment #1 from Tom Stellard --- Merged: r332765 -- 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 36649] [meta] 6.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=36649 Bug 36649 depends on bug 37520, which changed state. Bug 37520 Summary: Merge r322266 to 6.0.1 https://bugs.llvm.org/show_bug.cgi?id=37520 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 33439] dynamic_cast to ambiguous base produces the wrong answer
https://bugs.llvm.org/show_bug.cgi?id=33439 Eric Fiselier changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #7 from Eric Fiselier --- Fixed in r332767 -- 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 37521] [X86][AVX512] "getConstant with a uint64_t value that doesn't fit in the type!" in "X86 DAG->DAG Instruction Selection"
https://bugs.llvm.org/show_bug.cgi?id=37521 Matt Arsenault changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Matt Arsenault --- r332774 -- 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 37519] Merge r324885 to 6.0.1
https://bugs.llvm.org/show_bug.cgi?id=37519 Tom Stellard changed: What|Removed |Added Status|NEW |RESOLVED Fixed By Commit(s)|r324885 |r324885 r332776 Resolution|--- |FIXED --- Comment #1 from Tom Stellard --- Merged: r332776 -- 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 36649] [meta] 6.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=36649 Bug 36649 depends on bug 37519, which changed state. Bug 37519 Summary: Merge r324885 to 6.0.1 https://bugs.llvm.org/show_bug.cgi?id=37519 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 36649] [meta] 6.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=36649 Bug 36649 depends on bug 37518, which changed state. Bug 37518 Summary: Merge r329268, r330037 to 6.0.1 https://bugs.llvm.org/show_bug.cgi?id=37518 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 37518] Merge r329268, r330037 to 6.0.1
https://bugs.llvm.org/show_bug.cgi?id=37518 Tom Stellard changed: What|Removed |Added Resolution|--- |FIXED Fixed By Commit(s)|r329268 r330037 |r329268 r330037 r332778 ||r332782 Status|NEW |RESOLVED --- Comment #2 from Tom Stellard --- Merged: r332778 r332782 -- 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 37526] New: [InstCombine] MinMax patterns produce an infinite loop within InstCombine.
https://bugs.llvm.org/show_bug.cgi?id=37526 Bug ID: 37526 Summary: [InstCombine] MinMax patterns produce an infinite loop within InstCombine. Product: new-bugs Version: trunk Hardware: PC OS: All Status: NEW Severity: normal Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: matthew.da...@sony.com CC: llvm-bugs@lists.llvm.org Created attachment 20319 --> https://bugs.llvm.org/attachment.cgi?id=20319&action=edit Reduced Reproducer The attached test case is a reduced version of some code that we have found to be producing an infinite loop within InstCombine. I have noted that the code works prior to r320157 (December 2017) but with the added handling of MinMax patterns in the r320157 patch, it seems that InstCombine::run gets stuck (infinite loop). In particular, a minmax pattern is discovered in InstCombiner, and removeBitcastsFromLoadStoreOnMinMax is called (InstCombineLoadStoreAlloca.cpp) to handle an instruction that matches that pattern. This routine introduces a load and store which eventually get removed during the same iteration of InstCombiner::run(). The load becomes trivially dead. The store is removed because it is automatically added to the Worklist in InstCombiner, and is visited in the same run() iteration. When this newly created Store instruction is visited it is recognized as being part of a minmax pattern, and removeBitcastsFromLoadStoreOnMinMax is called. That routine is successful, and that store is removed. This instruction add/removal sets the InstCombine::MadeIRChange, flag which controls the exit of InstCombine::run. However, since that iteration of run() will always add and remove instructions, no fixed point is achieved, and run() is called indefinitely. Reproduced with trunk and 6.0 release: clang++ -O2 ./reducer.cc -c -- 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 37527] New: MergeICmps crashes when compiling with -fno-builtin
https://bugs.llvm.org/show_bug.cgi?id=37527 Bug ID: 37527 Summary: MergeICmps crashes when compiling with -fno-builtin Product: libraries Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: Scalar Optimizations Assignee: unassignedb...@nondot.org Reporter: richard-l...@metafoo.co.uk CC: llvm-bugs@lists.llvm.org Created attachment 20321 --> https://bugs.llvm.org/attachment.cgi?id=20321&action=edit testcase Testcase attached. Build with: $ clang -cc1 -O3 -fno-builtin -x ir merge-icmp.ir -emit-obj -o /dev/null to reproduce the crash: Stack dump: 0. Program arguments: clang -cc1 -O3 -fno-builtin -x ir /tmp/merge-icmp.ir -emit-obj -o /dev/null 1. Code generation 2. Running pass 'Function Pass Manager' on module '/tmp/merge-icmp.ir'. 3. Running pass 'Merge contiguous icmps into a memcmp' on function '@wobble' #0 0x556256dd66a6 llvm::sys::RunSignalHandlers() (clang+0x1d4f6a6) #1 0x5562560552f4 SignalHandler(int) (clang+0xfce2f4) #2 0x7f29694cf9a0 __restore_rt (/usr/grte/v4/lib64/libpthread.so.0+0xf9a0) #3 0x556256f01180 llvm::IRBuilder::CreateICmp(llvm::CmpInst::Predicate, llvm::Value*, llvm::Value*, llvm::Twine const&) (clang+0x1e7a180) #4 0x55625628fd05 (anonymous namespace)::BCECmpChain::mergeComparisons(llvm::ArrayRef<(anonymous namespace)::BCECmpBlock>, llvm::BasicBlock*, llvm::PHINode&, llvm::TargetLibraryInfo const*) (clang+0x1208d05) #5 0x556256269972 (anonymous namespace)::MergeICmps::runOnFunction(llvm::Function&) (clang+0x11e2972) -- 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
