[llvm-bugs] [Bug 43699] [AMDGPU][GlobalISel] EXPENSIVE_CHECKS failures with inst-select-fabs.mir and inst-select-fneg.mir
https://bugs.llvm.org/show_bug.cgi?id=43699 Matt Arsenault changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #5 from Matt Arsenault --- 21bc8e5a137d76879223ac2d8ff1ba92e2ea3acb -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43764] Unqualified name use causes ambiguity through ADL (forward_as_tuple)
https://bugs.llvm.org/show_bug.cgi?id=43764 David Blaikie changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED Fixed By Commit(s)||llvmorg-10-init-8501-ge658b ||3eb972 -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43794] Assertion `(*RBI.getRegBank(DefReg, MRI, TRI)).getID() == AArch64::GPRRegBankID && "Unexpected ext regbank"' failed.
https://bugs.llvm.org/show_bug.cgi?id=43794 Amara Emerson changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Amara Emerson --- I've pushed a fix in 0f6ed432d58e47e7082bfd44d7b29f3ee54e2642. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 18594 in oss-fuzz: llvm:clang-fuzzer: Null-dereference READ in clang::Sema::RequireCompleteDeclContext
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, d...@google.com, mit...@google.com, bigchees...@gmail.com, eney...@google.com, llvm-b...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Reproducible Stability-Memory-MemorySanitizer Engine-libfuzzer OS-Linux Proj-llvm Reported-2019-10-28 Type: Bug New issue 18594 by ClusterFuzz-External: llvm:clang-fuzzer: Null-dereference READ in clang::Sema::RequireCompleteDeclContext https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=18594 Detailed Report: https://oss-fuzz.com/testcase?key=5749698086567936 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_msan_llvm Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x Crash State: clang::Sema::RequireCompleteDeclContext clang::Sema::BuildCXXNestedNameSpecifier clang::Sema::IsInvalidUnlessNestedName Sanitizer: memory (MSAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_msan_llvm=201906300300:201910150335 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5749698086567936 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally. When you fix this bug, please * mention the fix revision(s). * state whether the bug was a short-lived regression or an old bug in any stable releases. * add any other useful information. This information can help downstream consumers. If you need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored. -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43831] New: llvm-symbolizer should produce inlined call frames with PDBs
https://bugs.llvm.org/show_bug.cgi?id=43831 Bug ID: 43831 Summary: llvm-symbolizer should produce inlined call frames with PDBs Product: tools Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: llvm-symbolizer Assignee: unassignedb...@nondot.org Reporter: r...@google.com CC: llvm-bugs@lists.llvm.org llvm-symbolizer is mainly used by Windows ASan and LLVM itself to print stack traces. If it is built with DIA support, it prefers to use DIA, which implements the "get inlining info API" by delegating to the main symbolization API: https://github.com/llvm/llvm-project/blob/9c8282a9b33084d95c579e9f76daddfcd2f74c32/llvm/lib/DebugInfo/PDB/PDBContext.cpp#L86 We should print good inline call frame info by default, one way or another: 1. We could implement the API calls via DIA to get this info. 2. We could default to the native debug info libraries and interpret the inline line table info ourselves. Either way, llvm-symbolizer should provide this info by default, since LLVM puts work into producing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43291] Debug info affects output from "opt -inline -adce"
https://bugs.llvm.org/show_bug.cgi?id=43291 bjorn.a.petters...@ericsson.com changed: What|Removed |Added Status|NEW |RESOLVED Fixed By Commit(s)||80cb2cecc65753a Resolution|--- |FIXED --- Comment #6 from bjorn.a.petters...@ericsson.com --- Solved by https://github.com/llvm/llvm-project/commit/80cb2cecc65753aa1de09a09f3750408913f6450 -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 37728] [meta] Make llvm passes debug info invariant
https://bugs.llvm.org/show_bug.cgi?id=37728 Bug 37728 depends on bug 43291, which changed state. Bug 43291 Summary: Debug info affects output from "opt -inline -adce" https://bugs.llvm.org/show_bug.cgi?id=43291 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43771] 'omp target' directive segfaults Clang with std::decay from libstdc++
https://bugs.llvm.org/show_bug.cgi?id=43771 Alexey Bataev changed: What|Removed |Added Fixed By Commit(s)||7c860698208aee32df1883601b9 ||4924fa4a3d531 Status|NEW |RESOLVED CC||a.bat...@hotmail.com Resolution|--- |FIXED --- Comment #1 from Alexey Bataev --- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43830] New: lldb crashes when loading Python 3.6 interpreter
https://bugs.llvm.org/show_bug.cgi?id=43830 Bug ID: 43830 Summary: lldb crashes when loading Python 3.6 interpreter Product: lldb Version: 9.0 Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: sguel...@redhat.com CC: jdevliegh...@apple.com, llvm-bugs@lists.llvm.org Reproducer: $ lldb -o script (lldb) script #0 0x7f89c6b890ee llvm::sys::PrintStackTrace(llvm::raw_ostream&) /home/sguelton/sources/llvm-project/llvm/lib/Support/Unix/Signals.inc:533:22 #1 0x7f89c6b89181 PrintStackTraceSignalHandler(void*) /home/sguelton/sources/llvm-project/llvm/lib/Support/Unix/Signals.inc:594:1 #2 0x7f89c6b87323 llvm::sys::RunSignalHandlers() /home/sguelton/sources/llvm-project/llvm/lib/Support/Signals.cpp:68:20 #3 0x7f89c6b88b6a SignalHandler(int) /home/sguelton/sources/llvm-project/llvm/lib/Support/Unix/Signals.inc:385:1 #4 0x7f89c65d3680 __restore_rt (/lib64/libpthread.so.0+0xf680) #5 0x7f89c0fd5cf4 PyModule_GetState (/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0xe3cf4) #6 0x7f89a36e0ed9 _init (/opt/rh/rh-python36/root/usr/lib64/python3.6/lib-dynload/readline.cpython-36m-x86_64-linux-gnu.so+0x3ed9) #7 0x7f89b79acff5 rl_initialize (/lib64/libedit.so.0+0x20ff5) #8 0x7f89a36e168f PyInit_readline (/opt/rh/rh-python36/root/usr/lib64/python3.6/lib-dynload/readline.cpython-36m-x86_64-linux-gnu.so+0x468f) #9 0x7f89c10c842f _PyImport_LoadDynamicModuleWithSpec (/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x1d642f) #10 0x7f89c10c7ca4 (/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x1d5ca4) #11 0x7f89c0fd55f7 PyCFunction_Call (/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0xe35f7) #12 0x7f89c103c9b2 _PyEval_EvalFrameDefault (/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x14a9b2) #13 0x7f89c1040c8c (/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x14ec8c) #14 0x7f89c1041aba (/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x14faba) #15 0x7f89c1041e23 (/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x14fe23) #16 0x7f89c10362a7 _PyEval_EvalFrameDefault (/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x1442a7) #17 0x7f89c1041a0a (/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x14fa0a) #18 0x7f89c1041e23 (/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x14fe23) #19 0x7f89c10362a7 _PyEval_EvalFrameDefault (/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x1442a7) #20 0x7f89c1041a0a (/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x14fa0a) #21 0x7f89c1041e23 (/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x14fe23) #22 0x7f89c10362a7 _PyEval_EvalFrameDefault (/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x1442a7) #23 0x7f89c1041a0a (/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x14fa0a) #24 0x7f89c1041e23 (/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x14fe23) #25 0x7f89c10362a7 _PyEval_EvalFrameDefault (/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x1442a7) #26 0x7f89c1041a0a (/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x14fa0a) #27 0x7f89c1041e23 (/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x14fe23) #28 0x7f89c10362a7 _PyEval_EvalFrameDefault (/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x1442a7) #29 0x7f89c1042f12 _PyFunction_FastCallDict (/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x150f12) #30 0x7f89c0f980ce _PyObject_FastCallDict (/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0xa60ce) #31 0x7f89c0f993f4 _PyObject_CallMethodIdObjArgs (/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0xa73f4) #32 0x7f89c105a28f PyImport_ImportModuleLevelObject (/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x16828f) #33 0x7f89c1039201 _PyEval_EvalFrameDefault (/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x147201) #34 0x7f89c1042122 PyEval_EvalCodeEx (/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x150122) #35 0x7f89c1042dbb PyEval_EvalCode (/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x150dbb) #36 0x7f89c10352cb (/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x1432cb) #37 0x7f89c0fd55f7 PyCFunction_Call (/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0xe35f7) #38 0x7f89c103c9b2 _PyEval_EvalFrameDefault
[llvm-bugs] [Bug 43829] New: getRegisterByName() should be taught the rest of the registers
https://bugs.llvm.org/show_bug.cgi?id=43829 Bug ID: 43829 Summary: getRegisterByName() should be taught the rest of the registers Product: libraries Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: Backend: Hexagon Assignee: unassignedb...@nondot.org Reporter: ndesaulni...@google.com CC: bc...@codeaurora.org, llvm-bugs@lists.llvm.org https://reviews.llvm.org/rL341658 taught LLVM how to recognize r19, but as we see with https://github.com/ClangBuiltLinux/linux/issues/755, using any other register for a register local variable causes the backend to crash. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 16271 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: Res.getLLTTy(*getMRI()).isPointer() && Res.getLLTTy(*getMRI()) == Op0.getLLTTy(*
Updates: Labels: Deadline-Approaching Comment #2 on issue 16271 by sheriff...@chromium.org: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: Res.getLLTTy(*getMRI()).isPointer() && Res.getLLTTy(*getMRI()) == Op0.getLLTTy(* https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=16271#c2 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 16239 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: Unexpected-exit in llvm::report_fatal_error
Updates: Labels: Deadline-Approaching Comment #2 on issue 16239 by sheriff...@chromium.org: llvm/llvm-dwarfdump-fuzzer: Unexpected-exit in llvm::report_fatal_error https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=16239#c2 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 16246 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: Unexpected-exit in llvm::report_fatal_error
Updates: Labels: Deadline-Approaching Comment #2 on issue 16246 by sheriff...@chromium.org: llvm/llvm-dwarfdump-fuzzer: Unexpected-exit in llvm::report_fatal_error https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=16246#c2 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 16218 in oss-fuzz: llvm/clang-fuzzer: Null-dereference READ in clang::Sema::SetCtorInitializers
Updates: Labels: Deadline-Approaching Comment #2 on issue 16218 by sheriff...@chromium.org: llvm/clang-fuzzer: Null-dereference READ in clang::Sema::SetCtorInitializers https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=16218#c2 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43828] New: nowrap flags are not always correct after vectorization
https://bugs.llvm.org/show_bug.cgi?id=43828 Bug ID: 43828 Summary: nowrap flags are not always correct after vectorization Product: libraries Version: trunk Hardware: PC OS: All Status: NEW Severity: normal Priority: P Component: Loop Optimizer Assignee: unassignedb...@nondot.org Reporter: dantrus...@gmail.com CC: llvm-bugs@lists.llvm.org Created attachment 22738 --> https://bugs.llvm.org/attachment.cgi?id=22738=edit Test to demonstrate wrong vectorizer behavior When widening instructions loop vectorize always copies IR flags (including nowrap) from scalar instruction to new vector instruction. But this is not always correct. Consider subtract reduction loop which is vectorized and interleaved. outer_loop: %local_4 = phi i32 [ 2, %entry ], [ %4, %outer_tail] br label %inner_loop inner_loop: %local_2 = phi i32 [ 0, %outer_loop ], [ %1, %inner_loop ] %local_3 = phi i32 [ -104, %outer_loop ], [ %0, %inner_loop ] %0 = sub nuw nsw i32 %local_3, %local_4 %1 = add nuw nsw i32 %local_2, 1 %2 = icmp ugt i32 %local_2, 126 br i1 %2, label %outer_tail, label %inner_loop outer_tail: %3 = phi i32 [ %0, %inner_loop ] %4 = add i32 %local_4, 1 %5 = icmp slt i32 %4, 6 br i1 %5, label %outer_loop, label %exit Note nuw/nsw flags on sub instruction - they're correct for scalar code after vectorization it becomes: vector.ph:; preds = %outer_loop %broadcast.splatinsert3 = insertelement <4 x i32> undef, i32 %local_4, i32 0 %broadcast.splat4 = shufflevector <4 x i32> %broadcast.splatinsert3, <4 x i32> undef, <4 x i32> zeroinitializer br label %vector.body vector.body: ; preds = %vector.body, %vector.ph %index = phi i32 [ 0, %vector.ph ], [ %index.next, %vector.body ] %vec.phi = phi <4 x i32> [ , %vector.ph ], [ %2, %vector.body ] %vec.phi2 = phi <4 x i32> [ zeroinitializer, %vector.ph ], [ %3, %vector.body ] %0 = sub nuw nsw <4 x i32> %vec.phi, %broadcast.splat4 %1 = sub nuw nsw <4 x i32> %vec.phi2, %broadcast.splat4 %index.next = add i32 %index, 8 %2 = icmp eq i32 %index.next, 128 br i1 %2, label %middle.block, label %vector.body, !llvm.loop !0 Note that %1 sub still has nuw flag set, but it is incorrect now. Due to this flag, later optimizations remove second sub instruction [ (0 - x) -> 0 ] which results in incorrect code Simple testcase is attached (unrolling vectorized loop makes it clearly visible) -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43802] [LVI] Miscompile by CorrelatedValuePropagation: LVI doesn't take nsw into account
https://bugs.llvm.org/show_bug.cgi?id=43802 Sanjay Patel changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #4 from Sanjay Patel --- Should be minimally fixed with: https://reviews.llvm.org/rGf2e93d10fe0c As noted in https://reviews.llvm.org/D69442 - the patch appears to be sufficient given current LVI behavior. If that analysis changes, we might need a different/stronger fix. We can also try to restore the wrapping flags with further analysis. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43747] [AMDGPU][MC][GFX10] Missing v_interp_[p1/p2/mov]_f32_e64
https://bugs.llvm.org/show_bug.cgi?id=43747 Dmitry changed: What|Removed |Added Fixed By Commit(s)||b8042db 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 42473] SyncDependenceAnalysis: Crash on loop with split block
https://bugs.llvm.org/show_bug.cgi?id=42473 Simon Moll changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Simon Moll --- Fixed by https://reviews.llvm.org/rL372223 . -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 37185] Divergence Analysis: undetected divergence in unstructured control
https://bugs.llvm.org/show_bug.cgi?id=37185 Simon Moll changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #2 from Simon Moll --- Fixed by https://reviews.llvm.org/rL348048 -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43791] AlignmentTest.AlignConstexprConstant fails on x86 after r374758
https://bugs.llvm.org/show_bug.cgi?id=43791 Guillaume Chatelet changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #3 from Guillaume Chatelet --- This should be fixed by https://reviews.llvm.org/rGda68fd8f8160 -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 18583 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::APValue::swap
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, d...@google.com, mit...@google.com, bigchees...@gmail.com, eney...@google.com, llvm-b...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2019-10-28 Type: Bug New issue 18583 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::APValue::swap https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=18583 Detailed Report: https://oss-fuzz.com/testcase?key=5716078626078720 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7fff1770de08 Crash State: clang::APValue::swap IntExprEvaluator::Success clang::StmtVisitorBasebool>::Visit Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201904121821:201904130302 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5716078626078720 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally. When you fix this bug, please * mention the fix revision(s). * state whether the bug was a short-lived regression or an old bug in any stable releases. * add any other useful information. This information can help downstream consumers. If you need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored. -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
