[llvm-bugs] Issue 3629 in oss-fuzz: ASSERT: Offset <= INT_MAX && "Offset too big to fit in int."

Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #4 on issue 3629 by monor...@clusterfuzz-external.iam.gserviceaccount.com: ASSERT: Offset <= INT_MAX && "Offset too big to fit in int." https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3629#c4 ClusterFuzz

[llvm-bugs] Issue 3629 in oss-fuzz: ASSERT: Offset <= INT_MAX && "Offset too big to fit in int."

Comment #3 on issue 3629 by monor...@clusterfuzz-external.iam.gserviceaccount.com: ASSERT: Offset <= INT_MAX && "Offset too big to fit in int." https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3629#c3 ClusterFuzz has detected this issue as fixed in range 201711140614:201711141648.

[llvm-bugs] Issue 3629 in oss-fuzz: ASSERT: Offset <= INT_MAX && "Offset too big to fit in int."

Comment #2 on issue 3629 by jus...@justinbogner.com: ASSERT: Offset <= INT_MAX && "Offset too big to fit in int." https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3629#c2 Reproducer in IR: source_filename = "M" define void @f() { BB: %A11 = alloca i16 %A7 = alloca i1, i32 -1 %L4

[llvm-bugs] Issue 3629 in oss-fuzz: ASSERT: Offset <= INT_MAX && "Offset too big to fit in int."

Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, llvm-b...@lists.llvm.org, v...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer Proj-llvm Reported-2017-10-13 New issue 3629 by