[llvm-bugs] Issue 6270 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: N1.getValueType() == N2.getValueType() && N1.getValueType() == VT && "Binary ope
Comment #2 on issue 6270 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: N1.getValueType() == N2.getValueType() && N1.getValueType() == VT && "Binary ope https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6270#c2 ClusterFuzz has detected this issue as fixed in range 201802130618:201802140618. Detailed report: https://oss-fuzz.com/testcase?key=5697303101833216 Project: llvm Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--x86_64-O2 Fuzz target binary: llvm-isel-fuzzer--x86_64-O2 Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: N1.getValueType() == N2.getValueType() && N1.getValueType() == VT && "Binary ope llvm::SelectionDAG::getNode llvm::SelectionDAGBuilder::visitSDiv Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201802120631:201802130618 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201802130618:201802140618 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5697303101833216 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 6281 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: Result.getValueType() == TLI.getTypeToTransformTo(*DAG.getContext(), Op.getValue
Comment #2 on issue 6281 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: Result.getValueType() == TLI.getTypeToTransformTo(*DAG.getContext(), Op.getValue https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6281#c2 ClusterFuzz has detected this issue as fixed in range 201802130618:201802140618. Detailed report: https://oss-fuzz.com/testcase?key=4724519181746176 Project: llvm Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--aarch64-O2 Fuzz target binary: llvm-isel-fuzzer--aarch64-O2 Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: Result.getValueType() == TLI.getTypeToTransformTo(*DAG.getContext(), Op.getValue llvm::DAGTypeLegalizer::SetPromotedInteger llvm::DAGTypeLegalizer::PromoteIntegerResult Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201802120631:201802130618 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201802130618:201802140618 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4724519181746176 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 6286 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: LL.getValueType() == LR.getValueType() && RL.getValueType() == RR.getValueType()
Comment #2 on issue 6286 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: LL.getValueType() == LR.getValueType() && RL.getValueType() == RR.getValueType() https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6286#c2 ClusterFuzz has detected this issue as fixed in range 201802130618:201802140618. Detailed report: https://oss-fuzz.com/testcase?key=6247202272837632 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: LL.getValueType() == LR.getValueType() && RL.getValueType() == RR.getValueType() DAGCombiner::foldLogicOfSetCCs DAGCombiner::visitORLike Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201802120631:201802130618 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201802130618:201802140618 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6247202272837632 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 6290 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: OpNo == 0 && "Don't know how to promote this operand!"
Comment #2 on issue 6290 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: OpNo == 0 && "Don't know how to promote this operand!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6290#c2 ClusterFuzz has detected this issue as fixed in range 201802130618:201802140618. Detailed report: https://oss-fuzz.com/testcase?key=5720627324387328 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: OpNo == 0 && "Don't know how to promote this operand!" llvm::DAGTypeLegalizer::PromoteIntOp_SETCC llvm::DAGTypeLegalizer::PromoteIntegerOperand Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201802120631:201802130618 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201802130618:201802140618 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5720627324387328 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 6285 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: NumParts == 1 && "No-op copy with multiple parts!"
Comment #2 on issue 6285 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: NumParts == 1 && "No-op copy with multiple parts!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6285#c2 ClusterFuzz has detected this issue as fixed in range 201802130618:201802140618. Detailed report: https://oss-fuzz.com/testcase?key=5842547097206784 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: NumParts == 1 && "No-op copy with multiple parts!" getCopyToParts llvm::SelectionDAGBuilder::visitRet Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201802120631:201802130618 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201802130618:201802140618 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5842547097206784 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 6309 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: BitWidth == RHS.BitWidth && "Comparison requires equal bit widths"
Comment #2 on issue 6309 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: BitWidth == RHS.BitWidth && "Comparison requires equal bit widths" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6309#c2 ClusterFuzz has detected this issue as fixed in range 201802130618:201802140618. Detailed report: https://oss-fuzz.com/testcase?key=5117880619237376 Project: llvm Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--x86_64-O2 Fuzz target binary: llvm-isel-fuzzer--x86_64-O2 Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: BitWidth == RHS.BitWidth && "Comparison requires equal bit widths" llvm::SelectionDAG::FoldSetCC llvm::SelectionDAG::getNode Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201802120631:201802130618 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201802130618:201802140618 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5117880619237376 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 6281 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: Result.getValueType() == TLI.getTypeToTransformTo(*DAG.getContext(), Op.getValue
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #3 on issue 6281 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: Result.getValueType() == TLI.getTypeToTransformTo(*DAG.getContext(), Op.getValue https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6281#c3 ClusterFuzz testcase 4724519181746176 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 6309 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: BitWidth == RHS.BitWidth && "Comparison requires equal bit widths"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #3 on issue 6309 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: BitWidth == RHS.BitWidth && "Comparison requires equal bit widths" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6309#c3 ClusterFuzz testcase 5117880619237376 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 6290 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: OpNo == 0 && "Don't know how to promote this operand!"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #3 on issue 6290 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: OpNo == 0 && "Don't know how to promote this operand!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6290#c3 ClusterFuzz testcase 5720627324387328 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 6270 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: N1.getValueType() == N2.getValueType() && N1.getValueType() == VT && "Binary ope
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #3 on issue 6270 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: N1.getValueType() == N2.getValueType() && N1.getValueType() == VT && "Binary ope https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6270#c3 ClusterFuzz testcase 5697303101833216 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 6285 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: NumParts == 1 && "No-op copy with multiple parts!"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #3 on issue 6285 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: NumParts == 1 && "No-op copy with multiple parts!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6285#c3 ClusterFuzz testcase 5842547097206784 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 6286 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: LL.getValueType() == LR.getValueType() && RL.getValueType() == RR.getValueType()
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #3 on issue 6286 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: LL.getValueType() == LR.getValueType() && RL.getValueType() == RR.getValueType() https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6286#c3 ClusterFuzz testcase 6247202272837632 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 36368] Merge r323998 into the 6.0 branch
https://bugs.llvm.org/show_bug.cgi?id=36368 Hans Wennborg changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #1 from Hans Wennborg --- r325104 -- 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 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 36368, which changed state. Bug 36368 Summary: Merge r323998 into the 6.0 branch https://bugs.llvm.org/show_bug.cgi?id=36368 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 36377] New: clang++ -nostdlib++ -lstdc++ asserts
https://bugs.llvm.org/show_bug.cgi?id=36377 Bug ID: 36377 Summary: clang++ -nostdlib++ -lstdc++ asserts Product: clang Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: Driver Assignee: unassignedclangb...@nondot.org Reporter: h...@chromium.org CC: llvm-bugs@lists.llvm.org, nicolaswe...@gmx.de It should probably be an error instead? $ bin/clang++ -nostdlib++ -lstdc++ /tmp/a.cc clang++: ../tools/clang/lib/Driver/ToolChain.cpp:735: virtual void clang::driver::ToolChain::AddCXXStdlibLibArgs(const llvm::opt::ArgList&, llvm::opt::ArgStringList&) const: Assertion `!Args.hasArg(options::OPT_nostdlibxx) && "should not have called this"' failed. #0 0x560a661501ba llvm::sys::PrintStackTrace(llvm::raw_ostream&) (bin/clang+++0x24251ba) #1 0x560a6614e03e llvm::sys::RunSignalHandlers() (bin/clang+++0x242303e) #2 0x560a6614e18c SignalHandler(int) (bin/clang+++0x242318c) #3 0x7fb2da3d60c0 __restore_rt (/lib/x86_64-linux-gnu/libpthread.so.0+0x110c0) #4 0x7fb2d8f6bfcf gsignal (/lib/x86_64-linux-gnu/libc.so.6+0x32fcf) #5 0x7fb2d8f6d3fa abort (/lib/x86_64-linux-gnu/libc.so.6+0x343fa) #6 0x7fb2d8f64e37 (/lib/x86_64-linux-gnu/libc.so.6+0x2be37) #7 0x7fb2d8f64ee2 (/lib/x86_64-linux-gnu/libc.so.6+0x2bee2) #8 0x560a6660ec4d (bin/clang+++0x28e3c4d) #9 0x560a6663d717 clang::driver::tools::AddLinkerInputs(clang::driver::ToolChain const&, llvm::SmallVector const&, llvm::opt::ArgList const&, llvm::SmallVector&, clang::driver::JobAction const&) (bin/clang+++0x2912717) #10 0x560abac9 clang::driver::tools::gnutools::Linker::ConstructJob(clang::driver::Compilation&, clang::driver::JobAction const&, clang::driver::InputInfo const&, llvm::SmallVector const&, llvm::opt::ArgList const&, char const*) const (bin/clang+++0x2940ac9) #11 0x560a665fac05 clang::driver::Driver::BuildJobsForActionNoCache(clang::driver::Compilation&, clang::driver::Action const*, clang::driver::ToolChain const*, llvm::StringRef, bool, bool, char const*, std::map, std::allocator > >, clang::driver::InputInfo, std::less, std::allocator > > >, std::allocator, std::allocator > > const, clang::driver::InputInfo> > >&, clang::driver::Action::OffloadKind) const (bin/clang+++0x28cfc05) #12 0x560a665fbca8 clang::driver::Driver::BuildJobsForAction(clang::driver::Compilation&, clang::driver::Action const*, clang::driver::ToolChain const*, llvm::StringRef, bool, bool, char const*, std::map, std::allocator > >, clang::driver::InputInfo, std::less, std::allocator > > >, std::allocator, std::allocator > > const, clang::driver::InputInfo> > >&, clang::driver::Action::OffloadKind) const (bin/clang+++0x28d0ca8) #13 0x560a665fc4ab clang::driver::Driver::BuildJobs(clang::driver::Compilation&) const (bin/clang+++0x28d14ab) #14 0x560a665fd38e clang::driver::Driver::BuildCompilation(llvm::ArrayRef) (bin/clang+++0x28d238e) #15 0x560a64975cf0 main (bin/clang+++0xc4acf0) #16 0x7fb2d8f592b1 __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x202b1) #17 0x560a649f104a _start (bin/clang+++0xcc604a) Stack dump: 0. Program arguments: bin/clang++ -nostdlib++ -lstdc++ /tmp/a.cc 1. Compilation construction 2. Building compilation jobs 3. Building compilation jobs Aborted -- 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 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 36182, which changed state. Bug 36182 Summary: [X86] KTEST instruction emitted for signed comparisons despite it always clearing S flag https://bugs.llvm.org/show_bug.cgi?id=36182 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 36182] [X86] KTEST instruction emitted for signed comparisons despite it always clearing S flag
https://bugs.llvm.org/show_bug.cgi?id=36182 Hans Wennborg changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #7 from Hans Wennborg --- Awesome! Merged in r325105 and r325106, respectively. -- 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 36375] Merge r324962 into 6.0
https://bugs.llvm.org/show_bug.cgi?id=36375 Hans Wennborg changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #1 from Hans Wennborg --- Thanks! Merged in r325108. -- 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 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 36375, which changed state. Bug 36375 Summary: Merge r324962 into 6.0 https://bugs.llvm.org/show_bug.cgi?id=36375 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 36094] [AMDGPU][MC][GFX9] r128 modifier of image instructions should be disabled for GFX9
https://bugs.llvm.org/show_bug.cgi?id=36094 Dmitry changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #1 from Dmitry --- closed by commit 324231: http://llvm.org/viewvc/llvm-project?view=revision&revision=324231 -- 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 36095] [AMDGPU][MC][GFX8][GFX9] d16 modifier of image instructions should be enabled for GFX8/9 only
https://bugs.llvm.org/show_bug.cgi?id=36095 Dmitry changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #1 from Dmitry --- closed by commit 324231: http://llvm.org/viewvc/llvm-project?view=revision&revision=324231 -- 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 36154] [AMDGPU][MC][GFX8][GFX9] Incorrect dst/data size for MIMG opcodes with d16 modifier
https://bugs.llvm.org/show_bug.cgi?id=36154 Dmitry changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #1 from Dmitry --- Closed by commit 324237: http://llvm.org/viewvc/llvm-project?rev=324237&view=rev -- 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 36378] New: clang crash building Linux kernel i915 druver
https://bugs.llvm.org/show_bug.cgi?id=36378 Bug ID: 36378 Summary: clang crash building Linux kernel i915 druver Product: libraries Version: 6.0 Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: Backend: X86 Assignee: unassignedb...@nondot.org Reporter: dw...@infradead.org CC: llvm-bugs@lists.llvm.org 1. parser at end of file 2. Code generation 3. Running pass 'Function Pass Manager' on module 'drivers/gpu/drm/i915/i915_perf.c'. 4. Running pass 'X86 DAG->DAG Instruction Selection' on function '@i915_perf_open_ioctl' clang-6.0: error: unable to execute command: Segmentation fault (core dumped) clang-6.0: error: clang frontend command failed due to signal (use -v to see invocation) clang version 6.0.0 (trunk 321709) (llvm/trunk 321711) Target: i386-unknown-linux-gnu Thread model: posix InstalledDir: /home/dwmw2/git/llvm6/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/i915_perf-4799c9.c clang-6.0: note: diagnostic msg: /tmp/i915_perf-4799c9.sh clang-6.0: note: diagnostic msg: http://david.woodhou.se/i915_perf-4799c9.c http://david.woodhou.se/i915_perf-4799c9.sh -- 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 36379] New: opt crashes with -enable-nontrivial-unswitch -passes=unswitch: Assertion `(L.contains(ChildN->getBlock()) || llvm::find(ExitBlocks, ChildN->getBlock()) != ExitBlocks.end()
https://bugs.llvm.org/show_bug.cgi?id=36379
Bug ID: 36379
Summary: opt crashes with -enable-nontrivial-unswitch
-passes=unswitch: Assertion
`(L.contains(ChildN->getBlock()) ||
llvm::find(ExitBlocks, ChildN->getBlock()) !=
ExitBlocks.end()) && "Should never reach beyond the
loop and exits when deleting!"' failed
Product: libraries
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: Loop Optimizer
Assignee: unassignedb...@nondot.org
Reporter: fedor.v.serg...@gmail.com
CC: llvm-bugs@lists.llvm.org
Fails on a rather simple IR:
] cat bad-unswitch.ll
define void @test() {
br label %check1
check1:
br i1 true, label %check2, label %check1
check2:
br i1 true, label %check3, label %zero
check3:
br i1 true, label %check4, label %zero
check4:
br i1 true, label %check3, label %check1
zero:
ret void
}
] opt --enable-nontrivial-unswitch -passes=unswitch --disable-output
bad-unswitch.ll
opt: lib/Transforms/Scalar/SimpleLoopUnswitch.cpp:1238: void
deleteDeadBlocksFromLoop(llvm::Loop&, llvm::BasicBlock*,
llvm::SmallVectorImpl&, llvm::DominatorTree&,
llvm::LoopInfo&): Assertion `(L.contains(ChildN->getBlock()) ||
llvm::find(ExitBlocks, ChildN->getBlock()) != ExitBlocks.end()) && "Should
never reach beyond the loop and exits when deleting!"' failed.
]
Originally it was failing on a considerably more complicated testcase where
trivial unswitch failed to perform any unswitches and I had to enable
nontrivial one. Got this assert immediately, reduced down to the above bits.
--
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 36380] New: No sanity checking of array size with width specifier ?
https://bugs.llvm.org/show_bug.cgi?id=36380
Bug ID: 36380
Summary: No sanity checking of array size with width specifier
?
Product: new-bugs
Version: 5.0
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: dcb...@hotmail.com
CC: llvm-bugs@lists.llvm.org
Given the following code:
# include
extern void g( FILE * fp);
void f( FILE * fp)
{
char buf[ 10];
while (fscanf( fp, "%10s", buf))
;
while (fscanf( fp, "%5s", buf))
;
while (fscanf( fp, "%20s", buf))
;
g( fp);
}
then clang doesn't seem to sanity check the size in the % specifier
against the buffer size. Please note that %10s isn't the correct size.
That's a well known off by one error.
Here is static analyser cppcheck doing something suitable:
[sep9a.cc:13]: (error) Width 10 given in format string (no. 1) is larger than
destination buffer 'buf[10]', use %9s to prevent overflowing it.
[sep9a.cc:17]: (error) Width 20 given in format string (no. 1) is larger than
destination buffer 'buf[10]', use %9s to prevent overflowing it.
--
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 36381] New: Crash in NonNullParamChecker / clang::ento::RangedConstraintManager::assumeSymUnsupported()
https://bugs.llvm.org/show_bug.cgi?id=36381
Bug ID: 36381
Summary: Crash in NonNullParamChecker /
clang::ento::RangedConstraintManager::assumeSymUnsuppo
rted()
Product: clang
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: Static Analyzer
Assignee: dcough...@apple.com
Reporter: ale...@google.com
CC: ekarpen...@apple.com, llvm-bugs@lists.llvm.org
Here's a test case I reduced manually from the output of creduce:
class C {};
void f(C i) {
auto lambda = [&] { f(i); };
typedef decltype(lambda) T;
static char *p;
T **pfn = static_cast(static_cast(&p));
*pfn = new T(lambda);
(**pfn)();
}
Stack trace:
clang::ento::RangedConstraintManager::assumeSymUnsupported
clang::ento::RangedConstraintManager::assumeSym
clang::ento::SimpleConstraintManager::assumeAux
clang::ento::SimpleConstraintManager::assume
clang::ento::SimpleConstraintManager::assume
clang::ento::ConstraintManager::assumeDual
::NonNullParamChecker::checkPreCall
clang::ento::check::PreCall::_checkCall
clang::ento::CheckerFn::operator()
::CheckCallContext::runChecker
expandGraphWithCheckers
clang::ento::CheckerManager::runCheckersForCallEvent
clang::ento::CheckerManager::runCheckersForPreCall
clang::ento::ExprEngine::VisitCXXConstructExpr
clang::ento::ExprEngine::Visit
clang::ento::ExprEngine::ProcessStmt
clang::ento::ExprEngine::processCFGElement
clang::ento::CoreEngine::HandlePostStmt
clang::ento::CoreEngine::ExecuteWorkList
::AnalysisConsumer::ActionExprEngine
::AnalysisConsumer::HandleCode
::AnalysisConsumer::HandleTranslationUnit
--
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 36382] New: math.h included before __config
https://bugs.llvm.org/show_bug.cgi?id=36382 Bug ID: 36382 Summary: math.h included before __config Product: libc++ Version: unspecified Hardware: PC OS: All Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: unassignedclangb...@nondot.org Reporter: christof.do...@arm.com CC: llvm-bugs@lists.llvm.org, mclow.li...@gmail.com A recent change (https://reviews.llvm.org/rL323490) added support for the MS Windows platforms to include the C math.h header as the first thing in the C++ math.h. This creates a problem for C libraries that require some configuration to provide the correct functionality for libc++. Such configuration could be done in __config before, but now there is no such place. Can we move __config to be included before the C math.h? -- 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 36383] New: .inl files ignored by Visual Studio extension
https://bugs.llvm.org/show_bug.cgi?id=36383 Bug ID: 36383 Summary: .inl files ignored by Visual Studio extension Product: clang Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P Component: Formatter Assignee: unassignedclangb...@nondot.org Reporter: mikhail.matro...@gmail.com CC: djas...@google.com, kli...@google.com, llvm-bugs@lists.llvm.org Install Clang-Format extension for Visual Studio 2017. Open Visual Studio, go to Tools->Options->Clang/LLVM, see option "File extensions". This is the default value: .c;.cpp;.cxx;.cc;.tli;.tlh;.h;.hh;.hpp;.hxx;.hh;.inl.java;.js;.ts;.m;.mm;.proto;.protodevel;.td Note how semicolon is missed between .inl and .java. Because of this, when you open .inl file in Visual Studio, it is not formatted on save. The manual fix is easy: just add semicolon after you installed the extension. But it would be nice if you fixed the defaults. -- 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 4390 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: Sanitizer CHECK failure in "((0)) != (0)" (0x0, 0x0)
Updates: Labels: Deadline-Approaching Comment #7 on issue 4390 by sheriff...@chromium.org: llvm/llvm-dwarfdump-fuzzer: Sanitizer CHECK failure in "((0)) != (0)" (0x0, 0x0) https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4390#c7 This bug is approaching its deadline for being fixed, and will be automatically derestricted within 7 days. If a fix is planned within 2 weeks after the deadline has passed, a grace extension can be granted. - Your friendly Sheriffbot -- 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 36384] New: MatchFinder constructor causes segfault
https://bugs.llvm.org/show_bug.cgi?id=36384
Bug ID: 36384
Summary: MatchFinder constructor causes segfault
Product: clang
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: jacq...@nag.co.uk
CC: llvm-bugs@lists.llvm.org
Created attachment 19863
--> https://bugs.llvm.org/attachment.cgi?id=19863&action=edit
Small test code
I'm sure this is not a bug but a user error/config issue, but I thought I'd
report anyway. This is against current trunk of LLVM/clang (see version number
below)
Can someone just check that this code compiles and runs without segfaulting?
Compile with
clang++ -O0 -g -std=c++11 -fno-exceptions -fno-rtti
-I${path/to/clang/build}/lib/clang/7.0.0/include
-I${path/to/clang/build}/include main.cpp -o a.out -lLLVMSupport -lpthread
-ltinfo -lclangFrontend -lclangSerialization -lclangDriver -lclangParse
-lclangSema -lclangAnalysis -lclangEdit -lclangAST -lclangLex -lclangBasic
-lclangTooling -lclangToolingCore -lclangFormat -lclangRewrite
-lclangASTMatchers
Run on any source file.
My setup:
clang version 7.0.0 (trunk 324074)
Target: x86_64-unknown-linux-gnu
Thread model: posix
clang version 7.0.0 (trunk 324074)
Target: x86_64-unknown-linux-gnu
Thread model: posix
gcc (Ubuntu 5.4.0-6ubuntu1~16.04.6) 5.4.0 20160609
Clang built with
cmake -G "Unix Makefiles" -DCMAKE_BUILD_TYPE=Release
-DCMAKE_INSTALL_PREFIX=${path/to/clang/build} -DLLVM_TARGETS_TO_BUILD="X86"
-DBUILD_SHARED_LIBS=true ..
using gcc
--
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 36385] New: Please backport r325139 to 6.0
https://bugs.llvm.org/show_bug.cgi?id=36385 Bug ID: 36385 Summary: Please backport r325139 to 6.0 Product: libraries Version: trunk Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: MC Assignee: unassignedb...@nondot.org Reporter: roy...@freebsd.org CC: llvm-bugs@lists.llvm.org Blocks: 35804 It makes asm macros persistent across inline asm instances. This is required in order to compile Xen. Thanks, Roger. Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=35804 [Bug 35804] [meta] 6.0.0 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 35792] Missed optimization: Failure to emit BLSR for 32 bit inputs (or less)
https://bugs.llvm.org/show_bug.cgi?id=35792 Sanjay Patel changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #21 from Sanjay Patel --- This was at least 3 independent bugs in 1 report. I'm going to mark this as fixed because we are generating 'blsr' in the simplified cases mentioned so far after these commits: https://reviews.llvm.org/rL323437 https://reviews.llvm.org/rL324839 https://reviews.llvm.org/rL325018 If we're still failing to produce blsr in other cases or in your environment, please file another bug. Thanks! -- 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 36386] New: JumpThreading misoptimization, only on glibc 2.26
https://bugs.llvm.org/show_bug.cgi?id=36386 Bug ID: 36386 Summary: JumpThreading misoptimization, only on glibc 2.26 Product: libraries Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: Scalar Optimizations Assignee: unassignedb...@nondot.org Reporter: a...@crichton.co CC: junb...@codeaurora.org, llvm-bugs@lists.llvm.org Hello! Over at rust-lang/rust we've recently upgraded to LLVM 6.0 (yay!) but unfortunately have had a bit of a rocky time since then. We've been having flaky CI runs [1] that are spuriously failing on various platforms. This has been notoriously difficult to reproduce so far, but I think we've started making some great progress! This bug originally surfaced as a presumed miscompilation of rustc itself, although I believe we've reduced it down to a much smaller test case at this point. The odd part about this reproduction is it depends on whether LLVM, as it's running, is using glibc 2.26 or not. When using glibc 2.26 a miscompilation occurs, and when using glibc 2.25 or prior the miscompilation does not occur. I've personally been completely baffled by what's going on here. Valgrind hasn't reported much suspicious unfortunately. The one thing it did report, a conditional jump on uninitialized memory, was diagnosed [2] as a spurious error that likely isn't the root cause. My local machine has glibc 2.23 installed, and I've been using Docker to emulate Ubuntu 18.04 and get glibc 2.26. I've been compiling LLVM locally with assertions enabled and in release mode using Clang 4 as a compiler. Using the same `opt` binary from this build (which was built against glibc 2.23) I then get different results optimizing the input IR [3] depending on whether it runs on Ubuntu 16.04 (glibc 2.23) or Ubuntu 18.04 (glibc 2.26). The output of each run and their diff is here -- [4]. Jun I've cc'd you because when I ran a bisection on this error I was seeing it came up with https://reviews.llvm.org/D30352 as a culprit. Reverting that patch does indeed seem to fix the behavior locally, although that patch also doesn't seem like it's doing anything wrong so I'd suspect that this was an existing bug perhaps. Would you be able to help us though in routing this to the proper folks? If any more information is needed please just let us know! I think we've worked around this issue in our own builds for now at least so it's hopefully not pressing on our end any more, but this seems like it may be good to fix regardless! [1]: https://github.com/rust-lang/rust/issues/48116 [2]: https://github.com/rust-lang/rust/issues/48116#issuecomment-365662392 [3]: https://gist.github.com/alexcrichton/c39d44ea1df7293b5a522293340be6ee [4]: https://gist.github.com/alexcrichton/ac88a4a59576aeff929d568f16c5114d -- 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 27653] BOUND instruction has swapped arguments
https://bugs.llvm.org/show_bug.cgi?id=27653 Craig Topper changed: What|Removed |Added Resolution|--- |FIXED CC||craig.top...@gmail.com Status|ASSIGNED|RESOLVED --- Comment #4 from Craig Topper --- Fixed in r325178 -- 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 35818] Crash when compiling coroutine with custom suspend_always
https://bugs.llvm.org/show_bug.cgi?id=35818
gornisha...@gmail.com changed:
What|Removed |Added
CC||gornisha...@gmail.com
Status|NEW |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #3 from gornisha...@gmail.com ---
Looks like a duplicate of https://bugs.llvm.org/show_bug.cgi?id=34984
In suspend_always, await_resume() is missing.
constexpr void await_result() const noexcept {} // <-- should be await_resume
Though, I like await_result name. Maybe even more than await_resume.
*** This bug has been marked as a duplicate of bug 34984 ***
--
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 36387] New: Load from a local value is not hoisted outside of the loop when the value is populated via sret pointer
https://bugs.llvm.org/show_bug.cgi?id=36387 Bug ID: 36387 Summary: Load from a local value is not hoisted outside of the loop when the value is populated via sret pointer Product: libraries Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: Global Analyses Assignee: unassignedb...@nondot.org Reporter: timshe...@gmail.com CC: llvm-bugs@lists.llvm.org Created attachment 19864 --> https://bugs.llvm.org/attachment.cgi?id=19864&action=edit Test The attach shows a piece of IR that contains two loads in the loop, while GCC compiles the original C++ source code down to one load in the loop, the other one hoisted out of the loop. I'm not entirely sure if this should be fixed in Clang or LLVM. Put it here to start with. -- 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 36388] New: -polyhedral-info -polly-check-parallel analyzes non parallel loop as parallel.
https://bugs.llvm.org/show_bug.cgi?id=36388
Bug ID: 36388
Summary: -polyhedral-info -polly-check-parallel analyzes non
parallel loop as parallel.
Product: Polly
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: Optimizer
Assignee: polly-...@googlegroups.com
Reporter: takiu...@oscartech.jp
CC: llvm-bugs@lists.llvm.org
The outer loop of the following program is analyzed as parallel by
-polyhedral-info -polly-check-parallel. But the outerloop has loop-carried
dependence and is analyzed as not parallel by -polly-parallel analysis.
float a[256],b[256];
float aa[256][256],bb[256][256],cc[256][256];
int main () {
for (int i = 1; i < 256;i++) {
a[i] = a[i-1]+b[i] ;
for (int j=0;j<256;j++ ) {
aa[i][j] = aa[i][j]+cc[i][j];
}
}
return 0;
}
clang -O1 -S -emit-llvm -o loop.s loop.c
opt -S -polly-canonicalize loop.s > loop.preopt.ll
opt -polly-parallel -polly-ast -polyhedral-info -polly-check-parallel -analyze
-q loop.preopt.ll -polly-process-unprofitable
Printing analysis 'Polly - Generate an AST from the SCoP (isl)' for region:
'for.body8 => for.cond.cleanup7' in function 'main':
Printing analysis 'Polly - Generate an AST from the SCoP (isl)' for region:
'for.body => for.cond.cleanup' in function 'main':
:: isl ast :: main :: %for.body---%for.cond.cleanup
if (1)
#pragma minimal dependence distance: 1
for (int c0 = 0; c0 <= 254; c0 += 1) {
Stmt0(c0);
#pragma simd
#pragma known-parallel
for (int c1 = 0; c1 <= 255; c1 += 1)
Stmt1(c0, c1);
}
else
{ /* original code */ }
Printing analysis 'Polly - Generate an AST from the SCoP (isl)' for region:
'entry => ' in function 'main':
Printing analysis 'Polly - Interface to polyhedral analysis engine' for
function 'main':
for.body: Loop is parallel.
for.body8:Loop is parallel.
--
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 36389] New: clang crashes on valid code at -O3 in 64-bit mode on x86_64-linux-gnu: Assertion `SuccChain.UnscheduledPredecessors == 0 && "Found CFG-violating block"' failed
https://bugs.llvm.org/show_bug.cgi?id=36389
Bug ID: 36389
Summary: clang crashes on valid code at -O3 in 64-bit mode on
x86_64-linux-gnu: Assertion
`SuccChain.UnscheduledPredecessors == 0 && "Found
CFG-violating block"' failed
Product: clang
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: s...@cs.ucdavis.edu
CC: llvm-bugs@lists.llvm.org
Tested with trunk revision 325135. The reduced code is still very hairy.
$ clangpolly -v
clang version 7.0.0 (http://llvm.org/git/clang.git
1532324f1979660b1fc429eff544e1a9c1b79332) (http://llvm.org/git/llvm.git
ba2e473a530286f386d18a95c9de4d673d4a21dc)
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 -m64 -O2 small.c
$ clangpolly -m32 -O3 small.c
$
$ clangpolly -m64 -O3 small.c
clang-6.0:
/home/su/software/tmp/polly/llvm/lib/CodeGen/MachineBlockPlacement.cpp:1591:
llvm::MachineBasicBlock*
{anonymous}::MachineBlockPlacement::selectBestCandidateBlock(const
{anonymous}::BlockChain&, llvm::SmallVectorImpl&):
Assertion `SuccChain.UnscheduledPredecessors == 0 && "Found CFG-violating
block"' failed.
#0 0x0219695a llvm::sys::PrintStackTrace(llvm::raw_ostream&)
/home/su/software/tmp/polly/llvm/lib/Support/Unix/Signals.inc:402:0
#1 0x021947ee llvm::sys::RunSignalHandlers()
/home/su/software/tmp/polly/llvm/lib/Support/Signals.cpp:50:0
#2 0x02194962 SignalHandler(int)
/home/su/software/tmp/polly/llvm/lib/Support/Unix/Signals.inc:242:0
#3 0x7f5b14372390 __restore_rt
(/lib/x86_64-linux-gnu/libpthread.so.0+0x11390)
#4 0x7f5b130e4428 gsignal
/build/glibc-bfm8X4/glibc-2.23/signal/../sysdeps/unix/sysv/linux/raise.c:54:0
#5 0x7f5b130e602a abort /build/glibc-bfm8X4/glibc-2.23/stdlib/abort.c:91:0
#6 0x7f5b130dcbd7 __assert_fail_base
/build/glibc-bfm8X4/glibc-2.23/assert/assert.c:92:0
#7 0x7f5b130dcc82 (/lib/x86_64-linux-gnu/libc.so.6+0x2dc82)
#8 0x01b60dbe LookupBucketFor
/home/su/software/tmp/polly/llvm/include/llvm/ADT/DenseMap.h:618:0
#9 0x01b60dbe lookup
/home/su/software/tmp/polly/llvm/include/llvm/ADT/DenseMap.h:183:0
#10 0x01b60dbe operator()
/home/su/software/tmp/polly/llvm/lib/CodeGen/MachineBlockPlacement.cpp:1571:0
#11 0x01b60dbe operator()
/usr/include/c++/5/bits/predefined_ops.h:234:0
#12 0x01b60dbe __find_if&)::
> > /usr/include/c++/5/bits/stl_algo.h:120:0
#13 0x01b60dbe __find_if&)::
> > /usr/include/c++/5/bits/stl_algo.h:162:0
#14 0x01b60dbe __remove_if&)::
> > /usr/include/c++/5/bits/stl_algo.h:860:0
#15 0x01b60dbe remove_if&)::
> /usr/include/c++/5/bits/stl_algo.h:937:0
#16 0x01b60dbe
remove_if&, (anonymous
namespace)::MachineBlockPlacement::selectBestCandidateBlock(const (anonymous
namespace)::BlockChain&,
llvm::SmallVectorImpl&)::
> /home/su/software/tmp/polly/llvm/include/llvm/ADT/STLExtras.h:855:0
#17 0x01b60dbe (anonymous
namespace)::MachineBlockPlacement::selectBestCandidateBlock((anonymous
namespace)::BlockChain const&,
llvm::SmallVectorImpl&) [clone .constprop.382]
/home/su/software/tmp/polly/llvm/lib/CodeGen/MachineBlockPlacement.cpp:1569:0
#18 0x01b65542 (anonymous
namespace)::MachineBlockPlacement::buildChain(llvm::MachineBasicBlock const*,
(anonymous namespace)::BlockChain&,
llvm::SmallSetVector*)
