[llvm-bugs] Issue 4644 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: ASSERT: Params.Version && Params.AddrSize && "Invalid Params for form"
Comment #6 on issue 4644 by ClusterFuzz-External: llvm/llvm-dwarfdump-fuzzer: ASSERT: Params.Version && Params.AddrSize && "Invalid Params for form" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4644#c6 ClusterFuzz has detected this issue as fixed in range 201801050611:201801060605. Detailed report: https://oss-fuzz.com/testcase?key=5921909347713024 Project: llvm Fuzzer: libFuzzer_llvm_llvm-dwarfdump-fuzzer Fuzz target binary: llvm-dwarfdump-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: Params.Version && Params.AddrSize && "Invalid Params for form" llvm::DWARFFormValue::getFixedByteSize llvm::DWARFFormValue::skipValue Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201708280446:201708291805 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201801050611:201801060605 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5921909347713024 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 4708 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: ShiftAmt <= BitWidth && "Invalid shift amount"
Comment #3 on issue 4708 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: ShiftAmt <= BitWidth && "Invalid shift amount" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4708#c3 ClusterFuzz has detected this issue as fixed in range 201801050611:201801060605. Detailed report: https://oss-fuzz.com/testcase?key=6042292046528512 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: ShiftAmt <= BitWidth && "Invalid shift amount" llvm::BasicAAResult::GetLinearExpression llvm::BasicAAResult::DecomposeGEPExpression 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=201801050611:201801060605 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6042292046528512 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 4644 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: ASSERT: Params.Version && Params.AddrSize && "Invalid Params for form"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #7 on issue 4644 by ClusterFuzz-External: llvm/llvm-dwarfdump-fuzzer: ASSERT: Params.Version && Params.AddrSize && "Invalid Params for form" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4644#c7 ClusterFuzz testcase 5921909347713024 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 4708 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: ShiftAmt <= BitWidth && "Invalid shift amount"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #4 on issue 4708 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: ShiftAmt <= BitWidth && "Invalid shift amount" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4708#c4 ClusterFuzz testcase 6042292046528512 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 35843] New: Assertion in APInt::getSExtValue in -aa-eval
https://bugs.llvm.org/show_bug.cgi?id=35843
Bug ID: 35843
Summary: Assertion in APInt::getSExtValue in -aa-eval
Product: libraries
Version: trunk
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: Global Analyses
Assignee: unassignedb...@nondot.org
Reporter: llvm-...@redking.me.uk
CC: dav...@freebsd.org, llvm-bugs@lists.llvm.org,
nunoplo...@sapo.pt, yyc1...@gmail.com
Reduced from https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4711
opt -aa-eval
define void @f() {
BB:
%G22 = getelementptr i1*, i1** undef, i8 -1
%B1 = mul i66 undef, 9223372036854775808
%G45 = getelementptr i1**, i1*** undef, i66 %B1
ret void
}
Assertion failed: getMinSignedBits() <= 64 && "Too many bits for int64_t", file
D:\LLVM\llvm\include\llvm/ADT/APInt.h, line 1557
--
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 35844] New: Missed optimization in math expression: optimize double comparing
https://bugs.llvm.org/show_bug.cgi?id=35844
Bug ID: 35844
Summary: Missed optimization in math expression: optimize
double comparing
Product: clang
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: LLVM Codegen
Assignee: unassignedclangb...@nondot.org
Reporter: zamazan...@tut.by
CC: llvm-bugs@lists.llvm.org
clang trunk with '-O3 -ffast-math -std=c++17' for this code:
double test(double x, double y)
{
if(x != y)
{
return 42.0;
}
return x/y;
}
generates this code:
.LCPI0_0:
.quad 4631107791820423168 # double 42
test(double, double): # @test(double, double)
ucomisd xmm0, xmm1
je .LBB0_2
movsd xmm0, qword ptr [rip + .LCPI0_0] # xmm0 = mem[0],zero
ret
.LBB0_2:
divsd xmm0, xmm1
ret
but we can optimize here divide operation and just return 1.0.
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35845] New: Glitch in documentation of diagnose_if attribute (assigning void return values to int variables)
https://bugs.llvm.org/show_bug.cgi?id=35845 Bug ID: 35845 Summary: Glitch in documentation of diagnose_if attribute (assigning void return values to int variables) Product: Documentation Version: trunk Hardware: All OS: All Status: NEW Severity: normal Priority: P Component: General docs Assignee: unassignedb...@nondot.org Reporter: jonathan.leffler+l...@gmail.com CC: llvm-bugs@lists.llvm.org https://clang.llvm.org/docs/AttributeReference.html#diagnose-if The code there is shown as: void abs(int a) __attribute__((diagnose_if(a >= 0, "Redundant abs call", "warning"))); void must_abs(int a) __attribute__((diagnose_if(a >= 0, "Redundant abs call", "error"))); int val = abs(1); // warning: Redundant abs call int val2 = must_abs(1); // error: Redundant abs call int val3 = abs(val); int val4 = must_abs(val); My understanding is that functions that return void can't be used on the RHS of an assignment, regardless of what happens with the arguments and attributes. The occurrences of void could become int (at least, that seems to me to be the easiest 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 33325] [X86][SSE] Improve equality memcmp support
https://bugs.llvm.org/show_bug.cgi?id=33325 Sanjay Patel changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #21 from Sanjay Patel --- And finally: https://reviews.llvm.org/D41714 https://reviews.llvm.org/rL321934 This goes beyond what was requested in this report to use 2 load-pairs-per-block for all enabled 'memcmp() == 0' expansions (including smaller scalar expansions). That looks better in theory, but we'll see if anyone reports perf problems from that change. -- 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 35834] [InstCombine] recognize 'not' variant of min-of-min
https://bugs.llvm.org/show_bug.cgi?id=35834 Sanjay Patel changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED Summary|[ValueTracking] recognize |[InstCombine] recognize |'not' variant of min-of-min |'not' variant of min-of-min --- Comment #7 from Sanjay Patel --- We can mark this as resolved - it's reduced to the same form as in bug 35717. So we're just waiting to see how we want to deal with min/max factorization (D41603). -- 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 35837] [X86] Assembler for vcvtsd2sil (%rax), %ebx favors EVEX encoding even though there's nothing requiring EVEX
https://bugs.llvm.org/show_bug.cgi?id=35837 Craig Topper changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #1 from Craig Topper --- Should be fixed in r321939. -- 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 10988] x86 MC encoder and disassembler bugs umbrella
https://bugs.llvm.org/show_bug.cgi?id=10988 Bug 10988 depends on bug 35837, which changed state. Bug 35837 Summary: [X86] Assembler for vcvtsd2sil (%rax), %ebx favors EVEX encoding even though there's nothing requiring EVEX https://bugs.llvm.org/show_bug.cgi?id=35837 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] Issue 5008 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: Abrt in llvm::llvm_unreachable_internal
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, llvm-b...@lists.llvm.org, v...@apple.com, mitchphi...@outlook.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Stability-AFL Engine-libfuzzer Proj-llvm Reported-2018-01-07 Type: Bug New issue 5008 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--x86_64-O2: Abrt in llvm::llvm_unreachable_internal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5008 Detailed report: https://oss-fuzz.com/testcase?key=394916122624 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: Abrt Crash Address: 0x0001 Crash State: llvm::llvm_unreachable_internal matchMinMaxOfMinMax matchSelectPattern Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201801020611:201801030610 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=394916122624 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. 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 have questions for the OSS-Fuzz team, please file an issue at https://github.com/google/oss-fuzz/issues. -- 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 5009 in oss-fuzz: llvm: Stack-overflow in clang::DeclContext::lookup
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, llvm-b...@lists.llvm.org, v...@apple.com, mitchphi...@outlook.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer Proj-llvm Reported-2018-01-07 Type: Bug New issue 5009 by ClusterFuzz-External: llvm: Stack-overflow in clang::DeclContext::lookup https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5009 Detailed report: https://oss-fuzz.com/testcase?key=5690793223258112 Project: llvm Fuzzer: libFuzzer_llvm_clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffefc2e6fd8 Crash State: clang::DeclContext::lookup clang::DeclContext::using_directives UnqualUsingDirectiveSet::addUsingDirectives Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201801030610:201801040618 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5690793223258112 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. 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 have questions for the OSS-Fuzz team, please file an issue at https://github.com/google/oss-fuzz/issues. -- 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
