[llvm-bugs] Issue 23214 in oss-fuzz: llvm:llvm-opt-fuzzer--x86_64-instcombine: ASSERT: A <= llvm::Value::MaximumAlignment && "Alignment too large."

[ClusterFuzz-External via monorail via llvm-bugs]

Status: New
Owner: ----
CC: kcc at google.com, mascasa at google.com, jdevlieg... at apple.com, igm... at gmail.com, davg at google.com, mitchp at google.com, bigchees... at gmail.com, eneyman at google.com, llvm-b... at lists.llvm.org, jfb at chromium.org, v... at apple.com, mitchphi... at outlook.com, xpl... at gmail.com, akils... at apple.com 
Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2020-06-09
Type: Bug

New issue 23214 by ClusterFuzz-External: llvm:llvm-opt-fuzzer--x86_64-instcombine: ASSERT: A <= llvm::Value::MaximumAlignment && "Alignment too large."
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=23214

Detailed Report: https://oss-fuzz.com/testcase?key=6280555200249856

Project: llvm
Fuzzing Engine: libFuzzer
Fuzz Target: llvm-opt-fuzzer--x86_64-instcombine
Job Type: libfuzzer_asan_llvm
Platform Id: linux

Crash Type: ASSERT
Crash Address: 
Crash State:
  A <= llvm::Value::MaximumAlignment && "Alignment too large."
  llvm::Attribute::getWithAlignment
  llvm::InstCombiner::visitCallBase
  
Sanitizer: address (ASAN)

Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202003310247:202004010253

Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6280555200249856

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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20200608/519a8d7f/attachment.html>