[llvm-bugs] Issue 11654 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: !I.hasOperandBundlesOtherThan( {LLVMContext::OB_deopt, LLVMContext::OB_funclet})

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Status: New
Owner: 
CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com,  
igm...@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 Proj-llvm Reported-2018-12-02

Type: Bug

New issue 11654 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-O2:  
ASSERT: !I.hasOperandBundlesOtherThan( {LLVMContext::OB_deopt,  
LLVMContext::OB_funclet})

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11654

Detailed report: https://oss-fuzz.com/testcase?key=5656797889691648

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:
  !I.hasOperandBundlesOtherThan( {LLVMContext::OB_deopt,  
LLVMContext::OB_funclet})

  llvm::SelectionDAGBuilder::visitInvoke
  llvm::SelectionDAGBuilder::visit

Sanitizer: address (ASAN)

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201710160455:201710190451


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


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 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.


--
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] 4 issues changed in oss-fuzz

2018-12-01 Thread infe… via monorail via llvm-bugs

Updates:
Status: New
Labels: -Unreproducible Reproducible

Comment by infe...@chromium.org:
Please ignore the last comment about testcase being unreproducible. The  
testcase is still reproducible. This happened due to a code refactoring on  
ClusterFuzz side, and the underlying root cause is now fixed. Resetting the  
label back to Reproducible. Sorry about the inconvenience caused from these  
incorrect notifications.


Affected issues:
  issue 4125: llvm/llvm-special-case-list-fuzzer: Heap-buffer-overflow in  
p_ere

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4125

  issue 4176: llvm/llvm-special-case-list-fuzzer: Heap-buffer-overflow in  
llvm_regcomp

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4176

  issue 4192: llvm/llvm-special-case-list-fuzzer: Heap-buffer-overflow in  
p_ere

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4192

  issue 7560: llvm/llvm-opt-fuzzer--x86_64-loop_vectorize:  
Heap-use-after-free in  
llvm::LoopVectorizationCostModel::setCostBasedWideningDecision

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=7560



--
You received this message because you are listed in the owner
or CC fields of these issues, or because you starred them.
You may adjust your issue notification preferences at:
http://bugs.chromium.org/hosting/settings

___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] Issue 11652 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: &*BB.begin() == PadInst && "WinEHPrepare failed to demote PHIs"

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Status: New
Owner: 
CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com,  
igm...@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 Proj-llvm Reported-2018-12-02

Type: Bug

New issue 11652 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-O2:  
ASSERT: &*BB.begin() == PadInst && "WinEHPrepare failed to demote PHIs"

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11652

Detailed report: https://oss-fuzz.com/testcase?key=5729500990537728

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:
  &*BB.begin() == PadInst && "WinEHPrepare failed to demote PHIs"
  llvm::FunctionLoweringInfo::set
  llvm::SelectionDAGISel::runOnMachineFunction

Sanitizer: address (ASAN)

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201710160455:201710190451


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


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 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.


--
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 11649 in oss-fuzz: llvm/clang-fuzzer: ASSERT: Access != AS_none && "Access specifier is AS_none inside a record decl"

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Status: New
Owner: 
CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com,  
igm...@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 Proj-llvm Reported-2018-12-02

Type: Bug

New issue 11649 by ClusterFuzz-External: llvm/clang-fuzzer: ASSERT:  
Access != AS_none && "Access specifier is AS_none inside a record decl"

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11649

Detailed report: https://oss-fuzz.com/testcase?key=5630992291725312

Project: llvm
Fuzzer: libFuzzer_llvm_clang-fuzzer
Fuzz target binary: clang-fuzzer
Job Type: libfuzzer_asan_llvm
Platform Id: linux

Crash Type: ASSERT
Crash Address:
Crash State:
  Access != AS_none && "Access specifier is AS_none inside a record decl"
  clang::Decl::AccessDeclContextSanity
  LookupDirect

Sanitizer: address (ASAN)

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


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 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.


--
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 39858] New: Compound assignment in constexpr function treated as ill-formed if LHS is an int and RHS is a floating point type

2018-12-01 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=39858

Bug ID: 39858
   Summary: Compound assignment in constexpr function treated as
ill-formed if LHS is an int and RHS is a floating
point type
   Product: clang
   Version: trunk
  Hardware: PC
OS: All
Status: NEW
  Severity: normal
  Priority: P
 Component: -New Bugs
  Assignee: unassignedclangb...@nondot.org
  Reporter: yaghmour.sha...@gmail.com
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org,
neeil...@live.com, richard-l...@metafoo.co.uk

Given the following example from this Stack Overflow question
https://stackoverflow.com/q/53570652/1708801

template constexpr int f(A a, B b) {
a /= b;
return a;
}

constexpr int x = f(2, 2);   // a, b: int
constexpr int y = f(2., 2.); // a, b: double
constexpr int z = f(2, 2.);  // a: int, b: double //<-- BOOM!
constexpr int w = f(2., 2);  // a: double, b: int

int main() {}

The line initialization of z is treated as ill-formed but there is nothing in 
[dcl.constexpr]p3 or [expr.const] that would seem to make this case different
than the rest, so this looks like a bug.

-- 
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 11647 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-sccp: ASSERT: getMinSignedBits() <= 64 && "Too many bits for int64_t"

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Status: New
Owner: 
CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com,  
igm...@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 Proj-llvm Reported-2018-12-01

Type: Bug

New issue 11647 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-sccp:  
ASSERT: getMinSignedBits() <= 64 && "Too many bits for int64_t"

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11647

Detailed report: https://oss-fuzz.com/testcase?key=5128791026827264

Project: llvm
Fuzzer: libFuzzer_llvm_llvm-opt-fuzzer--x86_64-sccp
Fuzz target binary: llvm-opt-fuzzer--x86_64-sccp
Job Type: libfuzzer_asan_llvm
Platform Id: linux

Crash Type: ASSERT
Crash Address:
Crash State:
  getMinSignedBits() <= 64 && "Too many bits for int64_t"
  llvm::ConstantFoldGetElementPtr
  llvm::ConstantExpr::getGetElementPtr

Sanitizer: address (ASAN)

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201802070726:201802080701


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


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 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.


--
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 6398 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: Timeout in llvm_llvm-isel-fuzzer--aarch64-O2

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: ClusterFuzz-Verified
Status: Verified

Comment #6 on issue 6398 by ClusterFuzz-External:  
llvm/llvm-isel-fuzzer--aarch64-O2: Timeout in  
llvm_llvm-isel-fuzzer--aarch64-O2

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6398#c6

ClusterFuzz testcase 5696882073403392 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 39857] New: linker script assignment loses relative nature of section

2018-12-01 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=39857

Bug ID: 39857
   Summary: linker script assignment loses relative nature of
section
   Product: lld
   Version: unspecified
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: ELF
  Assignee: unassignedb...@nondot.org
  Reporter: ndesaulni...@google.com
CC: llvm-bugs@lists.llvm.org, peter.sm...@linaro.org,
r...@google.com

Not sure the best way to reproduce this, but it was reported in another bug and
in a mail thread.

https://bugs.llvm.org/show_bug.cgi?id=39810#c11:
"It seems like __efistub__text = _text; loses the section relative property of
_text."

https://bugs.llvm.org/show_bug.cgi?id=39810#c13:
2.) A symbol assignment to symbol defined in a section description in a linker
script can lose the section information.

http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20170116/420898.html:
"The real problem is that we are not tracking
absoluteness correctly."

http://lists.infradead.org/pipermail/linux-arm-kernel/2018-December/616765.html:
(since using an intermediate assignment loses the section relative property
when using ld.lld)

-- 
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 6398 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: Timeout in llvm_llvm-isel-fuzzer--aarch64-O2

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs


Comment #5 on issue 6398 by ClusterFuzz-External:  
llvm/llvm-isel-fuzzer--aarch64-O2: Timeout in  
llvm_llvm-isel-fuzzer--aarch64-O2

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6398#c5

ClusterFuzz has detected this issue as fixed in range  
201804261605:201804270530.


Detailed report: https://oss-fuzz.com/testcase?key=5696882073403392

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: Timeout (exceeds 25 secs)
Crash Address:
Crash State:
  llvm_llvm-isel-fuzzer--aarch64-O2

Sanitizer: address (ASAN)

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201802140618:201802150620
Fixed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201804261605:201804270530


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


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] [Bug 39810] error: -shared and -pie may not be used together

2018-12-01 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=39810

Nick Desaulniers  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|NEW |RESOLVED

--- Comment #19 from Nick Desaulniers  ---
Ard has authored 3 patches to resolve this issue.

http://lists.infradead.org/pipermail/linux-arm-kernel/2018-November/616512.html:
[PATCH] arm64: drop linker script hack to hide efistub symbols
http://lists.infradead.org/pipermail/linux-arm-kernel/2018-December/616754.html:
[RFT PATCH] arm64: relocatable: build the kernel as a proper shared library
http://lists.infradead.org/pipermail/linux-arm-kernel/2018-December/616765.html:
[RFT PATCH] arm64: add support for building the KASLR kernel with LLVM lld

>From my testing, I concur that this issue is resolved.  There may be more child
bugs to file from this exploration, but are no longer a blocker for us.  Thanks
everyone for your help.  Closing as invalid.  Will file new bugs should any of
the above patches not land for whatever reason.

-- 
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 39652] Improve printf format string diagnostics for vector types

2018-12-01 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=39652

Matt Arsenault  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #6 from Matt Arsenault  ---
r348084 fixes the important cases

-- 
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 39856] New: Clang consumes all available memory

2018-12-01 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=39856

Bug ID: 39856
   Summary: Clang consumes all available memory
   Product: clang
   Version: 7.0
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: C++
  Assignee: unassignedclangb...@nondot.org
  Reporter: toe-...@web.de
CC: blitzrak...@gmail.com, dgre...@apple.com,
erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org,
richard-l...@metafoo.co.uk

Created attachment 21188
  --> https://bugs.llvm.org/attachment.cgi?id=21188=edit
Code

Code:
#include 
#include 
#include 
#include 

template 
void run_asynchronous_helper(std::index_sequence,
std::tuple &, Args &... args) {
std::array threads =
{std::thread{std::get(functions), args...}...};
std::get<0>(functions)(args...);
for (auto  : threads) {
thread.join();
}
}

template 
void run_asynchronous(std::tuple &, Args &... args) {
run_asynchronous_helper(std::make_index_sequence{}, std::move(functions), args...);
}

int main() {
//run_asynchronous(std::forward_as_tuple());
}

Output:
LLVM ERROR: out of memory
Stack dump:
0.  Program arguments: /home/toeger/Projects/llvm/build/bin/clang-7 -cc1
-triple x86_64-unknown-linux-gnu -emit-obj -mrelax-all -disable-free
-main-file-name main.cpp -mrelocation-model static -mthread-model posix
-mdisable-fp-elim -fmath-errno -masm-verbose -mconstructor-aliases
-munwind-tables -fuse-init-array -target-cpu x86-64 -dwarf-column-info
-debugger-tuning=gdb -resource-dir
/home/toeger/Projects/llvm/build/lib/clang/7.0.1 -internal-isystem
/usr/lib/gcc/x86_64-linux-gnu/8/../../../../include/c++/8 -internal-isystem
/usr/lib/gcc/x86_64-linux-gnu/8/../../../../include/x86_64-linux-gnu/c++/8
-internal-isystem
/usr/lib/gcc/x86_64-linux-gnu/8/../../../../include/x86_64-linux-gnu/c++/8
-internal-isystem
/usr/lib/gcc/x86_64-linux-gnu/8/../../../../include/c++/8/backward
-internal-isystem /usr/local/include -internal-isystem
/home/toeger/Projects/llvm/build/lib/clang/7.0.1/include
-internal-externc-isystem /usr/include/x86_64-linux-gnu
-internal-externc-isystem /include -internal-externc-isystem /usr/include
-std=c++17 -fdeprecated-macro -fdebug-compilation-dir
/home/toeger/Projects/llvm/build/bin -ferror-limit 19 -fmessage-length 190
-fobjc-runtime=gcc -fcxx-exceptions -fexceptions -fdiagnostics-show-option
-fcolor-diagnostics -o /tmp/main-dbeaff.o -x c++
/home/toeger/qt-projects/test/main.cpp -faddrsig 
1.   parser at end of file
2.  /home/toeger/qt-projects/test/main.cpp:16:6: instantiating function
definition 'run_asynchronous<>'
#0 0x558099f48324 llvm::sys::PrintStackTrace(llvm::raw_ostream&)
/tmp/llvm/build/../lib/Support/Unix/Signals.inc:490:22
#1 0x558099f483b7 PrintStackTraceSignalHandler(void*)
/tmp/llvm/build/../lib/Support/Unix/Signals.inc:554:1
#2 0x558099f463df llvm::sys::RunSignalHandlers()
/tmp/llvm/build/../lib/Support/Signals.cpp:67:20
#3 0x558099f47dea SignalHandler(int)
/tmp/llvm/build/../lib/Support/Unix/Signals.inc:353:1
#4 0x7fbb784a68e0 __restore_rt
(/lib/x86_64-linux-gnu/libpthread.so.0+0x128e0)
#5 0x7fbb77d7ef3b gsignal (/lib/x86_64-linux-gnu/libc.so.6+0x35f3b)
#6 0x7fbb77d802f1 abort (/lib/x86_64-linux-gnu/libc.so.6+0x372f1)
#7 0x558099ea6237 out_of_memory_new_handler()
/tmp/llvm/build/../lib/Support/ErrorHandling.cpp:186:41
#8 0x558097cd1b13 llvm::safe_realloc(void*, unsigned long)
/tmp/llvm/build/../include/llvm/Support/MemAlloc.h:45:10
#9 0x558099eba567 llvm::SmallVectorBase::grow_pod(void*, unsigned long,
unsigned long) /tmp/llvm/build/../lib/Support/SmallVector.cpp:61:27
#10 0x55809c28cbb6
llvm::SmallVectorTemplateCommon::grow_pod(unsigned long, unsigned long)
/tmp/llvm/build/../include/llvm/ADT/SmallVector.h:100:3
#11 0x55809c27ae02
llvm::SmallVectorTemplateBase::grow(unsigned
long) /tmp/llvm/build/../include/llvm/ADT/SmallVector.h:307:71
#12 0x55809c269a96
llvm::SmallVectorTemplateBase::push_back(clang::TemplateArgumentLoc const&)
/tmp/llvm/build/../include/llvm/ADT/SmallVector.h:313:11
#13 0x55809c263ff5
clang::TemplateArgumentListInfo::addArgument(clang::TemplateArgumentLoc const&)
/tmp/llvm/build/../tools/clang/include/clang/AST/TemplateBase.h:594:3
#14 0x55809cca01e0 checkBuiltinTemplateIdType(clang::Sema&,
clang::BuiltinTemplateDecl*, llvm::SmallVectorImpl
const&, clang::SourceLocation, clang::TemplateArgumentListInfo&)
/tmp/llvm/build/../tools/clang/lib/Sema/SemaTemplate.cpp:2950:25
#15 0x55809cca1a62 clang::Sema::CheckTemplateIdType(clang::TemplateName,
clang::SourceLocation, clang::TemplateArgumentListInfo&)
/tmp/llvm/build/../tools/clang/lib/Sema/SemaTemplate.cpp:3277:56
#16 0x55809ce026d9 clang::TreeTransform<(anonymous
namespace)::TemplateInstantiator>::RebuildTemplateSpecializationType(clang::TemplateName,

[llvm-bugs] [Bug 39855] New: zext inhibits shl+and+shr optimization

2018-12-01 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=39855

Bug ID: 39855
   Summary: zext inhibits shl+and+shr optimization
   Product: libraries
   Version: trunk
  Hardware: PC
OS: Windows NT
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Common Code Generator Code
  Assignee: unassignedb...@nondot.org
  Reporter: nikita@gmail.com
CC: llvm-bugs@lists.llvm.org

For

define i128 @test([4 x i128]* %table, i32 %idx) {
  %a = lshr i32 %idx, 4
  %b = and i32 %a, 3
  %c = zext i32 %b to i64
  %d = getelementptr inbounds [4 x i128], [4 x i128]* %table, i64 0, i64 %c
  %r = load i128, i128* %d, align 8
  ret i128 %r
}

llc generates:

shrl$4, %esi
andl$3, %esi
shlq$4, %rsi
movq(%rdi,%rsi), %rax
movq8(%rdi,%rsi), %rdx
retq

Doing the same without the zext

define i128 @test([4 x i128]* %table, i64 %idx) {
  %a = lshr i64 %idx, 4
  %b = and i64 %a, 3
  %d = getelementptr inbounds [4 x i128], [4 x i128]* %table, i64 0, i64 %b
  %r = load i128, i128* %d, align 8
  ret i128 %r
}

results in

andl$48, %esi
movq(%rdi,%rsi), %rax
movq8(%rdi,%rsi), %rdx
retq

which is the desired output.

This combine is carried out by
https://github.com/llvm-mirror/llvm/blob/d1c472605b0ff640ff202a7faee1fc3dad0174b6/lib/CodeGen/SelectionDAG/DAGCombiner.cpp#L6177,
which is able to handle a (shl (and (sra))) chain, but not (shl (zext (and
(sra.

Rust bug report: https://github.com/rust-lang/rust/issues/56057

-- 
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 6554 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-indvars: ASSERT: Ty->isSized() && "Cannot getTypeInfo() on a type that is unsized!"

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Status: WontFix

Comment #6 on issue 6554 by ClusterFuzz-External:  
llvm/llvm-opt-fuzzer--x86_64-indvars: ASSERT: Ty->isSized() && "Cannot  
getTypeInfo() on a type that is unsized!"

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6554#c6

ClusterFuzz testcase 6010076155346944 is flaky and no longer crashes, so  
closing issue.


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 11638 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-loop_vectorize: ASSERT: !KeyInfoT::isEqual(Val, EmptyKey) && !KeyInfoT::isEqual(Val, TombstoneKey) && "E

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Status: New
Owner: 
CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com,  
igm...@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 Proj-llvm Reported-2018-12-01

Type: Bug

New issue 11638 by ClusterFuzz-External:  
llvm/llvm-opt-fuzzer--x86_64-loop_vectorize:  
ASSERT: !KeyInfoT::isEqual(Val, EmptyKey) && !KeyInfoT::isEqual(Val,  
TombstoneKey) && "E

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11638

Detailed report: https://oss-fuzz.com/testcase?key=5755805853286400

Project: llvm
Fuzzer: libFuzzer_llvm_llvm-opt-fuzzer--x86_64-loop_vectorize
Fuzz target binary: llvm-opt-fuzzer--x86_64-loop_vectorize
Job Type: libfuzzer_asan_llvm
Platform Id: linux

Crash Type: ASSERT
Crash Address:
Crash State:
  !KeyInfoT::isEqual(Val, EmptyKey) && !KeyInfoT::isEqual(Val,  
TombstoneKey) && "E

  llvm::InterleaveGroup::insertMember
  llvm::InterleavedAccessInfo::analyzeInterleaving

Sanitizer: address (ASAN)

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201809120125:201809130127


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


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 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.


--
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 7555 in oss-fuzz: llvm/clang-fuzzer: ASSERT: !isTokenSpecial() && "Should consume special tokens with Consume*Token"

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #5 on issue 7555 by ClusterFuzz-External: llvm/clang-fuzzer:  
ASSERT: !isTokenSpecial() && "Should consume special tokens with  
Consume*Token"

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=7555#c5

ClusterFuzz testcase 6087300736876544 appears to be flaky, updating  
reproducibility label.


--
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 5272 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: idx < size()

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #6 on issue 5272 by ClusterFuzz-External:  
llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: idx < size()

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5272#c6

ClusterFuzz testcase 6638402460975104 appears to be flaky, updating  
reproducibility label.


--
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 4619 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: Abrt in llvm::llvm_unreachable_internal

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #10 on issue 4619 by ClusterFuzz-External:  
llvm/llvm-dwarfdump-fuzzer: Abrt in llvm::llvm_unreachable_internal

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4619#c10

ClusterFuzz testcase 6647657620570112 appears to be flaky, updating  
reproducibility label.


--
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 10380 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in clang::Preprocessor::CachingLex

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #1 on issue 10380 by ClusterFuzz-External: llvm/clang-fuzzer:  
Stack-overflow in clang::Preprocessor::CachingLex

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10380#c1

ClusterFuzz testcase 5696472863997952 appears to be flaky, updating  
reproducibility label.


--
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 4789 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: (!Is64Bit || isInt<32>((long long)FIOffset + Imm)) && "Requesting 64-bit offset

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #7 on issue 4789 by ClusterFuzz-External:  
llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: (!Is64Bit || isInt<32>((long  
long)FIOffset + Imm)) && "Requesting 64-bit offset

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4789#c7

ClusterFuzz testcase 6572563900661760 appears to be flaky, updating  
reproducibility label.


--
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 4749 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: LHS.getValueType() == MVT::f16 || LHS.getValueType() == MVT::f32 || LHS.getValue

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #7 on issue 4749 by ClusterFuzz-External:  
llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: LHS.getValueType() == MVT::f16 | 
| LHS.getValueType() == MVT::f32 || LHS.getValue

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4749#c7

ClusterFuzz testcase 6194536985395200 appears to be flaky, updating  
reproducibility label.


--
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 11097 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: Timeout in llvm_llvm-isel-fuzzer--x86_64-O2

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #2 on issue 11097 by ClusterFuzz-External:  
llvm/llvm-isel-fuzzer--x86_64-O2: Timeout in  
llvm_llvm-isel-fuzzer--x86_64-O2

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11097#c2

ClusterFuzz testcase 5642269969874944 appears to be flaky, updating  
reproducibility label.


--
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 11592 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: Timeout in llvm_llvm-isel-fuzzer--aarch64-gisel

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #2 on issue 11592 by ClusterFuzz-External:  
llvm/llvm-isel-fuzzer--aarch64-gisel: Timeout in  
llvm_llvm-isel-fuzzer--aarch64-gisel

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11592#c2

ClusterFuzz testcase 5640844342722560 appears to be flaky, updating  
reproducibility label.


--
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 7956 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-irce: Out-of-memory in llvm_llvm-opt-fuzzer--x86_64-irce

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #5 on issue 7956 by ClusterFuzz-External:  
llvm/llvm-opt-fuzzer--x86_64-irce: Out-of-memory in  
llvm_llvm-opt-fuzzer--x86_64-irce

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=7956#c5

ClusterFuzz testcase 5706209800749056 appears to be flaky, updating  
reproducibility label.


--
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 5579 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: DAG.getTargetLoweringInfo().isTypeLegal(PartVT) && "Copying to an illegal type!"

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #5 on issue 5579 by ClusterFuzz-External:  
llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT:  
DAG.getTargetLoweringInfo().isTypeLegal(PartVT) && "Copying to an illegal  
type!"

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5579#c5

ClusterFuzz testcase 5826425102794752 appears to be flaky, updating  
reproducibility label.


--
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] 5 issues changed in oss-fuzz

2018-12-01 Thread infe… via monorail via llvm-bugs

Updates:
Labels: -Unreproducible Reproducible

Comment by infe...@chromium.org:
Please ignore the last comment about testcase being unreproducible. The  
testcase is still reproducible. This happened due to a code refactoring on  
ClusterFuzz side, and the underlying root cause is now fixed. Resetting the  
label back to Reproducible. Sorry about the inconvenience caused from these  
incorrect notifications.


Affected issues:
  issue 4748: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: i <  
ValuePtrs.size()

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4748

  issue 6158: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: RC && "This value  
type is not natively supported!"

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6158

  issue 6527: llvm/clang-fuzzer: Stack-overflow in  
ComplexExprEvaluator::VisitBinaryOperator

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6527

  issue 8294: llvm/clang-fuzzer:  
ASSERT: !LHS.get()->getType()->isPlaceholderType()  
&& !RHS.get()->getType()->isPlacehold

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=8294

  issue 9142: llvm/llvm-opt-fuzzer--x86_64-loop_predication: ASSERT: i <  
getNumArgOperands() && "Out of bounds!"

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=9142



--
You received this message because you are listed in the owner
or CC fields of these issues, or because you starred them.
You may adjust your issue notification preferences at:
http://bugs.chromium.org/hosting/settings

___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] Issue 6527 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in ComplexExprEvaluator::VisitBinaryOperator

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #5 on issue 6527 by ClusterFuzz-External: llvm/clang-fuzzer:  
Stack-overflow in ComplexExprEvaluator::VisitBinaryOperator

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6527#c5

ClusterFuzz testcase 5861530882015232 appears to be flaky, updating  
reproducibility label.


--
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 9142 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-loop_predication: ASSERT: i < getNumArgOperands() && "Out of bounds!"

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #4 on issue 9142 by ClusterFuzz-External:  
llvm/llvm-opt-fuzzer--x86_64-loop_predication: ASSERT: i <  
getNumArgOperands() && "Out of bounds!"

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=9142#c4

ClusterFuzz testcase 5475599811346432 appears to be flaky, updating  
reproducibility label.


--
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 6158 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: RC && "This value type is not natively supported!"

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #5 on issue 6158 by ClusterFuzz-External:  
llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: RC && "This value type is not  
natively supported!"

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6158#c5

ClusterFuzz testcase 6518991817277440 appears to be flaky, updating  
reproducibility label.


--
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 4748 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: i < ValuePtrs.size()

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #7 on issue 4748 by ClusterFuzz-External:  
llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: i < ValuePtrs.size()

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4748#c7

ClusterFuzz testcase 5706220812894208 appears to be flaky, updating  
reproducibility label.


--
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 8294 in oss-fuzz: llvm/clang-fuzzer: ASSERT: !LHS.get()->getType()->isPlaceholderType() && !RHS.get()->getType()->isPlacehold

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #5 on issue 8294 by ClusterFuzz-External: llvm/clang-fuzzer:  
ASSERT: !LHS.get()->getType()->isPlaceholderType()  
&& !RHS.get()->getType()->isPlacehold

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=8294#c5

ClusterFuzz testcase 5104005070979072 appears to be flaky, updating  
reproducibility label.


--
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] 15 issues changed in oss-fuzz

2018-12-01 Thread infe… via monorail via llvm-bugs

Updates:
Labels: -Unreproducible Reproducible

Comment by infe...@chromium.org:
Please ignore the last comment about testcase being unreproducible. The  
testcase is still reproducible. This happened due to a code refactoring on  
ClusterFuzz side, and the underlying root cause is now fixed. Resetting the  
label back to Reproducible. Sorry about the inconvenience caused from these  
incorrect notifications.


Affected issues:
  issue 3133: llvm: ASSERT: DelayedTypos.empty() && "Uncorrected typos!"
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3133

  issue 3155: llvm: ASSERT: CachedTokens[CachedLexPos-1].getLastLoc() ==  
Tok.getAnnotationEndLoc() && "The a

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3155

  issue 3239: llvm: ASSERT: getContainingDC(DC) == CurContext && "The next  
DeclContext should be lexically c

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3239

  issue 3264: llvm: ASSERT: Ancestor->getEntity() == CurContext  
&& "ancestor context mismatch"

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3264

  issue 3353: llvm: ASSERT: CodeDC && !CodeDC->isFileContext()  
&& "statement expr not in code context"

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3353

  issue 3676: llvm/clang-format-fuzzer: ASSERT: PPBranchLevel <  
(int)PPLevelBranchIndex.size()

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3676

  issue 3737: llvm/clang-fuzzer: Abrt in llvm::llvm_unreachable_internal
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3737

  issue 4558: llvm/clang-format-fuzzer: ASSERT: NewRemainingTokenColumns <  
RemainingTokenColumns

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4558

  issue 4766: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: EltSize * 8 ==  
EltVT.getSizeInBits() && "Converting bits to bytes lost precision

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4766

  issue 6057: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: !carry
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6057

  issue 6592: llvm/llvm-opt-fuzzer--x86_64-loop_unswitch: Out-of-memory in  
llvm_llvm-opt-fuzzer--x86_64-loop_unswitch

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6592

  issue 7689: llvm/llvm-demangle-fuzzer: Out-of-memory in  
llvm_llvm-demangle-fuzzer

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=7689

  issue 10631: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: (!RS | 
| !RS->isScavengingFrameIndex(FrameIndex)) && "Emergency spill slot is out

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10631

  issue 10883: llvm/llvm-isel-fuzzer--aarch64-gisel: Null-dereference READ  
in llvm::AArch64RegisterBankInfo::getInstrMapping

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10883

  issue 11046: llvm/llvm-opt-fuzzer--x86_64-indvars: Timeout in  
llvm_llvm-opt-fuzzer--x86_64-indvars

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11046



--
You received this message because you are listed in the owner
or CC fields of these issues, or because you starred them.
You may adjust your issue notification preferences at:
http://bugs.chromium.org/hosting/settings

___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] Issue 4766 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: EltSize * 8 == EltVT.getSizeInBits() && "Converting bits to bytes lost precision

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #7 on issue 4766 by ClusterFuzz-External:  
llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: EltSize * 8 ==  
EltVT.getSizeInBits() && "Converting bits to bytes lost precision

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4766#c7

ClusterFuzz testcase 6145546977804288 appears to be flaky, updating  
reproducibility label.


--
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 6057 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: !carry

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #5 on issue 6057 by ClusterFuzz-External:  
llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: !carry

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6057#c5

ClusterFuzz testcase 5660146232459264 appears to be flaky, updating  
reproducibility label.


--
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 7689 in oss-fuzz: llvm/llvm-demangle-fuzzer: Out-of-memory in llvm_llvm-demangle-fuzzer

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #5 on issue 7689 by ClusterFuzz-External:  
llvm/llvm-demangle-fuzzer: Out-of-memory in llvm_llvm-demangle-fuzzer

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=7689#c5

ClusterFuzz testcase 6207753761587200 appears to be flaky, updating  
reproducibility label.


--
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 3676 in oss-fuzz: llvm/clang-format-fuzzer: ASSERT: PPBranchLevel < (int)PPLevelBranchIndex.size()

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #10 on issue 3676 by ClusterFuzz-External:  
llvm/clang-format-fuzzer: ASSERT: PPBranchLevel <  
(int)PPLevelBranchIndex.size()

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3676#c10

ClusterFuzz testcase 5663149194739712 appears to be flaky, updating  
reproducibility label.


--
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 3133 in oss-fuzz: llvm: ASSERT: DelayedTypos.empty() && "Uncorrected typos!"

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #19 on issue 3133 by ClusterFuzz-External: llvm: ASSERT:  
DelayedTypos.empty() && "Uncorrected typos!"

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3133#c19

ClusterFuzz testcase 5337758962810880 appears to be flaky, updating  
reproducibility label.


--
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 10631 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: (!RS || !RS->isScavengingFrameIndex(FrameIndex)) && "Emergency spill slot is out

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #2 on issue 10631 by ClusterFuzz-External:  
llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: (!RS | 
| !RS->isScavengingFrameIndex(FrameIndex)) && "Emergency spill slot is out

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10631#c2

ClusterFuzz testcase 5768734862475264 appears to be flaky, updating  
reproducibility label.


--
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 3264 in oss-fuzz: llvm: ASSERT: Ancestor->getEntity() == CurContext && "ancestor context mismatch"

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #13 on issue 3264 by ClusterFuzz-External: llvm: ASSERT:  
Ancestor->getEntity() == CurContext && "ancestor context mismatch"

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3264#c13

ClusterFuzz testcase 5840450994831360 appears to be flaky, updating  
reproducibility label.


--
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 3155 in oss-fuzz: llvm: ASSERT: CachedTokens[CachedLexPos-1].getLastLoc() == Tok.getAnnotationEndLoc() && "The a

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #15 on issue 3155 by ClusterFuzz-External: llvm: ASSERT:  
CachedTokens[CachedLexPos-1].getLastLoc() == Tok.getAnnotationEndLoc()  
&& "The a

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3155#c15

ClusterFuzz testcase 5706255345647616 appears to be flaky, updating  
reproducibility label.


--
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 11046 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-indvars: Timeout in llvm_llvm-opt-fuzzer--x86_64-indvars

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #2 on issue 11046 by ClusterFuzz-External:  
llvm/llvm-opt-fuzzer--x86_64-indvars: Timeout in  
llvm_llvm-opt-fuzzer--x86_64-indvars

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11046#c2

ClusterFuzz testcase 5692273807851520 appears to be flaky, updating  
reproducibility label.


--
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 3239 in oss-fuzz: llvm: ASSERT: getContainingDC(DC) == CurContext && "The next DeclContext should be lexically c

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #15 on issue 3239 by ClusterFuzz-External: llvm: ASSERT:  
getContainingDC(DC) == CurContext && "The next DeclContext should be  
lexically c

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3239#c15

ClusterFuzz testcase 5287158812246016 appears to be flaky, updating  
reproducibility label.


--
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 5035 in oss-fuzz: llvm/clang-fuzzer: ASSERT: CanDeclareSpecialMemberFunction(RD) && "doing special member lookup into record

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Status: WontFix

Comment #7 on issue 5035 by ClusterFuzz-External: llvm/clang-fuzzer:  
ASSERT: CanDeclareSpecialMemberFunction(RD) && "doing special member lookup  
into record

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5035#c7

ClusterFuzz testcase 6720050863013888 is flaky and no longer crashes, so  
closing issue.


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 4656 in oss-fuzz: llvm/clang-fuzzer: Out-of-memory in llvm_clang-fuzzer

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Status: WontFix

Comment #11 on issue 4656 by ClusterFuzz-External: llvm/clang-fuzzer:  
Out-of-memory in llvm_clang-fuzzer

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4656#c11

ClusterFuzz testcase 6258757458722816 is flaky and no longer crashes, so  
closing issue.


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 3353 in oss-fuzz: llvm: ASSERT: CodeDC && !CodeDC->isFileContext() && "statement expr not in code context"

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #11 on issue 3353 by ClusterFuzz-External: llvm: ASSERT: CodeDC  
&& !CodeDC->isFileContext() && "statement expr not in code context"

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3353#c11

ClusterFuzz testcase 5900679908425728 appears to be flaky, updating  
reproducibility label.


--
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 8803 in oss-fuzz: llvm/clang-fuzzer: ASSERT: N.ugt(ArraySize) && "bounds check failed for in-bounds index"

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Status: WontFix

Comment #5 on issue 8803 by ClusterFuzz-External: llvm/clang-fuzzer:  
ASSERT: N.ugt(ArraySize) && "bounds check failed for in-bounds index"

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=8803#c5

ClusterFuzz testcase 5930304727416832 is flaky and no longer crashes, so  
closing issue.


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 6592 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-loop_unswitch: Out-of-memory in llvm_llvm-opt-fuzzer--x86_64-loop_unswitch

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #5 on issue 6592 by ClusterFuzz-External:  
llvm/llvm-opt-fuzzer--x86_64-loop_unswitch: Out-of-memory in  
llvm_llvm-opt-fuzzer--x86_64-loop_unswitch

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6592#c5

ClusterFuzz testcase 5081849836601344 appears to be flaky, updating  
reproducibility label.


--
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 3737 in oss-fuzz: llvm/clang-fuzzer: Abrt in llvm::llvm_unreachable_internal

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #10 on issue 3737 by ClusterFuzz-External: llvm/clang-fuzzer: Abrt  
in llvm::llvm_unreachable_internal

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3737#c10

ClusterFuzz testcase 5416231357120512 appears to be flaky, updating  
reproducibility label.


--
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 5035 in oss-fuzz: llvm/clang-fuzzer: ASSERT: CanDeclareSpecialMemberFunction(RD) && "doing special member lookup into record

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #6 on issue 5035 by ClusterFuzz-External: llvm/clang-fuzzer:  
ASSERT: CanDeclareSpecialMemberFunction(RD) && "doing special member lookup  
into record

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5035#c6

ClusterFuzz testcase 6720050863013888 appears to be flaky, updating  
reproducibility label.


--
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] 4 issues changed in oss-fuzz

2018-12-01 Thread infe… via monorail via llvm-bugs

Updates:
Labels: -Unreproducible Reproducible

Comment by infe...@chromium.org:
Please ignore the last comment about testcase being unreproducible. The  
testcase is still reproducible. This happened due to a code refactoring on  
ClusterFuzz side, and the underlying root cause is now fixed. Resetting the  
label back to Reproducible. Sorry about the inconvenience caused from these  
incorrect notifications.


Affected issues:
  issue 4656: llvm/clang-fuzzer: Out-of-memory in llvm_clang-fuzzer
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4656

  issue 6893: llvm/llvm-opt-fuzzer--x86_64-sccp: Out-of-memory in  
llvm_llvm-opt-fuzzer--x86_64-sccp

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6893

  issue 10075: llvm/clang-fuzzer: ASSERT: !KeyInfoT::isEqual(Val, EmptyKey)  
&& !KeyInfoT::isEqual(Val, TombstoneKey) && "E

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10075

  issue 10907: llvm/clang-format-fuzzer: Timeout in llvm_clang-format-fuzzer
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10907



--
You received this message because you are listed in the owner
or CC fields of these issues, or because you starred them.
You may adjust your issue notification preferences at:
http://bugs.chromium.org/hosting/settings

___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] Issue 8803 in oss-fuzz: llvm/clang-fuzzer: ASSERT: N.ugt(ArraySize) && "bounds check failed for in-bounds index"

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #4 on issue 8803 by ClusterFuzz-External: llvm/clang-fuzzer:  
ASSERT: N.ugt(ArraySize) && "bounds check failed for in-bounds index"

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=8803#c4

ClusterFuzz testcase 5930304727416832 appears to be flaky, updating  
reproducibility label.


--
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 10883 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: Null-dereference READ in llvm::AArch64RegisterBankInfo::getInstrMapping

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #2 on issue 10883 by ClusterFuzz-External:  
llvm/llvm-isel-fuzzer--aarch64-gisel: Null-dereference READ in  
llvm::AArch64RegisterBankInfo::getInstrMapping

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10883#c2

ClusterFuzz testcase 5731974405160960 appears to be flaky, updating  
reproducibility label.


--
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 10075 in oss-fuzz: llvm/clang-fuzzer: ASSERT: !KeyInfoT::isEqual(Val, EmptyKey) && !KeyInfoT::isEqual(Val, TombstoneKey) && "E

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #3 on issue 10075 by ClusterFuzz-External: llvm/clang-fuzzer:  
ASSERT: !KeyInfoT::isEqual(Val, EmptyKey) && !KeyInfoT::isEqual(Val,  
TombstoneKey) && "E

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10075#c3

ClusterFuzz testcase 5102081510211584 appears to be flaky, updating  
reproducibility label.


--
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 4656 in oss-fuzz: llvm/clang-fuzzer: Out-of-memory in llvm_clang-fuzzer

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #9 on issue 4656 by ClusterFuzz-External: llvm/clang-fuzzer:  
Out-of-memory in llvm_clang-fuzzer

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4656#c9

ClusterFuzz testcase 6258757458722816 appears to be flaky, updating  
reproducibility label.


--
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 10907 in oss-fuzz: llvm/clang-format-fuzzer: Timeout in llvm_clang-format-fuzzer

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #2 on issue 10907 by ClusterFuzz-External:  
llvm/clang-format-fuzzer: Timeout in llvm_clang-format-fuzzer

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10907#c2

ClusterFuzz testcase 5750465615101952 appears to be flaky, updating  
reproducibility label.


--
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] 4 issues changed in oss-fuzz

2018-12-01 Thread infe… via monorail via llvm-bugs

Updates:
Labels: -Unreproducible Reproducible

Comment by infe...@chromium.org:
Please ignore the last comment about testcase being unreproducible. The  
testcase is still reproducible. This happened due to a code refactoring on  
ClusterFuzz side, and the underlying root cause is now fixed. Resetting the  
label back to Reproducible. Sorry about the inconvenience caused from these  
incorrect notifications.


Affected issues:
  issue 4081: llvm/clang-format-fuzzer: ASSERT: idx < size()
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4081

  issue 4737: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: idx < size()
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4737

  issue 5455: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: New->getType() ==  
getType() && "replaceAllUses of value with new value of differ

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5455

  issue 11234: llvm/llvm-opt-fuzzer--x86_64-strength_reduce: Timeout in  
llvm_llvm-opt-fuzzer--x86_64-strength_reduce

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11234



--
You received this message because you are listed in the owner
or CC fields of these issues, or because you starred them.
You may adjust your issue notification preferences at:
http://bugs.chromium.org/hosting/settings

___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] Issue 6893 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-sccp: Out-of-memory in llvm_llvm-opt-fuzzer--x86_64-sccp

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #5 on issue 6893 by ClusterFuzz-External:  
llvm/llvm-opt-fuzzer--x86_64-sccp: Out-of-memory in  
llvm_llvm-opt-fuzzer--x86_64-sccp

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6893#c5

ClusterFuzz testcase 5265354713464832 appears to be flaky, updating  
reproducibility label.


--
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] 4 issues changed in oss-fuzz

2018-12-01 Thread infe… via monorail via llvm-bugs

Updates:
Labels: -Unreproducible Reproducible

Comment by infe...@chromium.org:
Please ignore the last comment about testcase being unreproducible. The  
testcase is still reproducible. This happened due to a code refactoring on  
ClusterFuzz side, and the underlying root cause is now fixed. Resetting the  
label back to Reproducible. Sorry about the inconvenience caused from these  
incorrect notifications.


Affected issues:
  issue 11423: llvm/llvm-special-case-list-fuzzer: Timeout in  
llvm_llvm-special-case-list-fuzzer

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11423

  issue 11555: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: ShiftAmt <=  
BitWidth && "Invalid shift amount"

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11555

  issue 11567: llvm/clang-fuzzer: Null-dereference READ in  
diagnoseBadTypeAttribute

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11567

  issue 11593: llvm/llvm-dwarfdump-fuzzer: Heap-buffer-overflow in  
llvm::DWARFFormValue::dump

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11593



--
You received this message because you are listed in the owner
or CC fields of these issues, or because you starred them.
You may adjust your issue notification preferences at:
http://bugs.chromium.org/hosting/settings

___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] Issue 5455 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: New->getType() == getType() && "replaceAllUses of value with new value of differ

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #5 on issue 5455 by ClusterFuzz-External:  
llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: New->getType() == getType()  
&& "replaceAllUses of value with new value of differ

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5455#c5

ClusterFuzz testcase 5667930743242752 appears to be flaky, updating  
reproducibility label.


--
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 4737 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: idx < size()

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #7 on issue 4737 by ClusterFuzz-External:  
llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: idx < size()

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4737#c7

ClusterFuzz testcase 6656887798890496 appears to be flaky, updating  
reproducibility label.


--
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 4081 in oss-fuzz: llvm/clang-format-fuzzer: ASSERT: idx < size()

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #9 on issue 4081 by ClusterFuzz-External: llvm/clang-format-fuzzer:  
ASSERT: idx < size()

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4081#c9

ClusterFuzz testcase 474537037824 appears to be flaky, updating  
reproducibility label.


--
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 11234 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-strength_reduce: Timeout in llvm_llvm-opt-fuzzer--x86_64-strength_reduce

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #2 on issue 11234 by ClusterFuzz-External:  
llvm/llvm-opt-fuzzer--x86_64-strength_reduce: Timeout in  
llvm_llvm-opt-fuzzer--x86_64-strength_reduce

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11234#c2

ClusterFuzz testcase 5743328872628224 appears to be flaky, updating  
reproducibility label.


--
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] 6 issues changed in oss-fuzz

2018-12-01 Thread infe… via monorail via llvm-bugs

Updates:
Labels: -Unreproducible Reproducible

Comment by infe...@chromium.org:
Please ignore the last comment about testcase being unreproducible. The  
testcase is still reproducible. This happened due to a code refactoring on  
ClusterFuzz side, and the underlying root cause is now fixed. Resetting the  
label back to Reproducible. Sorry about the inconvenience caused from these  
incorrect notifications.


Affected issues:
  issue 4714: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: Offset <= INT_MAX  
&& "Offset too big to fit in int."

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4714

  issue 9418: llvm/llvm-opt-fuzzer--x86_64-earlycse: ASSERT:  
(VTy->isFirstClassType() || VTy->isVoidTy()) && "Cannot create  
non-first-class v

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=9418

  issue 10980: llvm/llvm-special-case-list-fuzzer: Out-of-memory in  
llvm_llvm-special-case-list-fuzzer

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10980

  issue 11023: llvm/clang-fuzzer: Timeout in llvm_clang-fuzzer
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11023

  issue 11075: llvm/llvm-dwarfdump-fuzzer: Timeout in  
llvm_llvm-dwarfdump-fuzzer

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11075

  issue 11363: llvm/llvm-demangle-fuzzer: Stack-overflow in  
llvm::itanium_demangle::AbstractManglingParser
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11363



--
You received this message because you are listed in the owner
or CC fields of these issues, or because you starred them.
You may adjust your issue notification preferences at:
http://bugs.chromium.org/hosting/settings

___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] 3 issues changed in oss-fuzz

2018-12-01 Thread infe… via monorail via llvm-bugs

Updates:
Labels: -Unreproducible Reproducible

Comment by infe...@chromium.org:
Please ignore the last comment about testcase being unreproducible. The  
testcase is still reproducible. This happened due to a code refactoring on  
ClusterFuzz side, and the underlying root cause is now fixed. Resetting the  
label back to Reproducible. Sorry about the inconvenience caused from these  
incorrect notifications.


Affected issues:
  issue 4702: llvm/llvm-isel-fuzzer--aarch64-gisel: Direct-leak in  
llvm::BitcodeReaderValueList::getValueFwdRef

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4702

  issue 4712: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT:  
TRI.getRegSizeInBits(*getRegClass(DstReg)) ==  
TRI.getRegSizeInBits(*getRegClass(

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4712

  issue 4858: llvm/clang-fuzzer: Abrt in llvm::llvm_unreachable_internal
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4858



--
You received this message because you are listed in the owner
or CC fields of these issues, or because you starred them.
You may adjust your issue notification preferences at:
http://bugs.chromium.org/hosting/settings

___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] Issue 4176 in oss-fuzz: llvm/llvm-special-case-list-fuzzer: Heap-buffer-overflow in llvm_regcomp

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Status: WontFix

Comment #11 on issue 4176 by ClusterFuzz-External:  
llvm/llvm-special-case-list-fuzzer: Heap-buffer-overflow in llvm_regcomp

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4176#c11

ClusterFuzz testcase 6698599137148928 is flaky and no longer crashes, so  
closing issue.


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 4714 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: Offset <= INT_MAX && "Offset too big to fit in int."

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #7 on issue 4714 by ClusterFuzz-External:  
llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: Offset <= INT_MAX && "Offset too  
big to fit in int."

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4714#c7

ClusterFuzz testcase 6053793432076288 appears to be flaky, updating  
reproducibility label.


--
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 9418 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-earlycse: ASSERT: (VTy->isFirstClassType() || VTy->isVoidTy()) && "Cannot create non-first-class v

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #3 on issue 9418 by ClusterFuzz-External:  
llvm/llvm-opt-fuzzer--x86_64-earlycse: ASSERT: (VTy->isFirstClassType() ||  
VTy->isVoidTy()) && "Cannot create non-first-class v

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=9418#c3

ClusterFuzz testcase 5735705459294208 appears to be flaky, updating  
reproducibility label.


--
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 4858 in oss-fuzz: llvm/clang-fuzzer: Abrt in llvm::llvm_unreachable_internal

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Status: WontFix

Comment #8 on issue 4858 by ClusterFuzz-External: llvm/clang-fuzzer: Abrt  
in llvm::llvm_unreachable_internal

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4858#c8

ClusterFuzz testcase 6742219068276736 is flaky and no longer crashes, so  
closing issue.


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 4125 in oss-fuzz: llvm/llvm-special-case-list-fuzzer: Heap-buffer-overflow in p_ere

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Status: WontFix

Comment #11 on issue 4125 by ClusterFuzz-External:  
llvm/llvm-special-case-list-fuzzer: Heap-buffer-overflow in p_ere

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4125#c11

ClusterFuzz testcase 6496293208719360 is flaky and no longer crashes, so  
closing issue.


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 4712 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: TRI.getRegSizeInBits(*getRegClass(DstReg)) == TRI.getRegSizeInBits(*getRegClass(

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #7 on issue 4712 by ClusterFuzz-External:  
llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT:  
TRI.getRegSizeInBits(*getRegClass(DstReg)) ==  
TRI.getRegSizeInBits(*getRegClass(

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4712#c7

ClusterFuzz testcase 5077269534998528 appears to be flaky, updating  
reproducibility label.


--
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 7690 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-licm: Out-of-memory in llvm_llvm-opt-fuzzer--x86_64-licm

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Status: WontFix

Comment #6 on issue 7690 by ClusterFuzz-External:  
llvm/llvm-opt-fuzzer--x86_64-licm: Out-of-memory in  
llvm_llvm-opt-fuzzer--x86_64-licm

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=7690#c6

ClusterFuzz testcase 6253849095438336 is flaky and no longer crashes, so  
closing issue.


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 4702 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: Direct-leak in llvm::BitcodeReaderValueList::getValueFwdRef

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #10 on issue 4702 by ClusterFuzz-External:  
llvm/llvm-isel-fuzzer--aarch64-gisel: Direct-leak in  
llvm::BitcodeReaderValueList::getValueFwdRef

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4702#c10

ClusterFuzz testcase 5258363341373440 appears to be flaky, updating  
reproducibility label.


--
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 8819 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: E <= size() && "Attempted to reset out-of-bounds range!"

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Status: WontFix

Comment #6 on issue 8819 by ClusterFuzz-External:  
llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: E <= size() && "Attempted to  
reset out-of-bounds range!"

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=8819#c6

ClusterFuzz testcase 5980804718002176 is flaky and no longer crashes, so  
closing issue.


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 11383 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-loop_vectorize: ASSERT: !KeyInfoT::isEqual(Val, EmptyKey) && !KeyInfoT::isEqual(Val, TombstoneKey) && "E

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Status: WontFix

Comment #3 on issue 11383 by ClusterFuzz-External:  
llvm/llvm-opt-fuzzer--x86_64-loop_vectorize:  
ASSERT: !KeyInfoT::isEqual(Val, EmptyKey) && !KeyInfoT::isEqual(Val,  
TombstoneKey) && "E

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11383#c3

ClusterFuzz testcase 576288457792 is flaky and no longer crashes, so  
closing issue.


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 4858 in oss-fuzz: llvm/clang-fuzzer: Abrt in llvm::llvm_unreachable_internal

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #7 on issue 4858 by ClusterFuzz-External: llvm/clang-fuzzer: Abrt  
in llvm::llvm_unreachable_internal

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4858#c7

ClusterFuzz testcase 6742219068276736 appears to be flaky, updating  
reproducibility label.


--
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] 6 issues changed in oss-fuzz

2018-12-01 Thread infe… via monorail via llvm-bugs

Updates:
Labels: -Unreproducible Reproducible

Comment by infe...@chromium.org:
Please ignore the last comment about testcase being unreproducible. The  
testcase is still reproducible. This happened due to a code refactoring on  
ClusterFuzz side, and the underlying root cause is now fixed. Resetting the  
label back to Reproducible. Sorry about the inconvenience caused from these  
incorrect notifications.


Affected issues:
  issue 7690: llvm/llvm-opt-fuzzer--x86_64-licm: Out-of-memory in  
llvm_llvm-opt-fuzzer--x86_64-licm

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=7690

  issue 8605: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: (Known.Zero &  
Known.One) == 0 && "Bits known to be one AND zero?"

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=8605

  issue 8694: llvm/llvm-dwarfdump-fuzzer: Heap-buffer-overflow in  
llvm::object::ELFObjectFile
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=8694

  issue 8699: llvm/llvm-dwarfdump-fuzzer: Out-of-memory in  
llvm_llvm-dwarfdump-fuzzer

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=8699

  issue 8819: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: E <= size()  
&& "Attempted to reset out-of-bounds range!"

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=8819

  issue 9569: llvm/llvm-dwarfdump-fuzzer: Abrt in  
llvm::report_bad_alloc_error

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=9569



--
You received this message because you are listed in the owner
or CC fields of these issues, or because you starred them.
You may adjust your issue notification preferences at:
http://bugs.chromium.org/hosting/settings

___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] Issue 11593 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: Heap-buffer-overflow in llvm::DWARFFormValue::dump

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #2 on issue 11593 by ClusterFuzz-External:  
llvm/llvm-dwarfdump-fuzzer: Heap-buffer-overflow in  
llvm::DWARFFormValue::dump

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11593#c2

ClusterFuzz testcase 5634286556807168 appears to be flaky, updating  
reproducibility label.


--
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 11373 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-loop_vectorize: ASSERT: !isUniformAfterVectorization(PredInst, VF) && "Instruction marked uniform-after-

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Status: WontFix

Comment #3 on issue 11373 by ClusterFuzz-External:  
llvm/llvm-opt-fuzzer--x86_64-loop_vectorize:  
ASSERT: !isUniformAfterVectorization(PredInst, VF) && "Instruction marked  
uniform-after-

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11373#c3

ClusterFuzz testcase 5736092758704128 is flaky and no longer crashes, so  
closing issue.


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 6157 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-gvn: ASSERT: !isa(TI) && "Cannot split critical edge from IndirectBrInst"

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #5 on issue 6157 by ClusterFuzz-External:  
llvm/llvm-opt-fuzzer--x86_64-gvn: ASSERT: !isa(TI)  
&& "Cannot split critical edge from IndirectBrInst"

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6157#c5

ClusterFuzz testcase 4975040933134336 appears to be flaky, updating  
reproducibility label.


--
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 10849 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: isValidElementType(ElementType) && "Element type of a VectorType must " "be an i

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Status: WontFix

Comment #3 on issue 10849 by ClusterFuzz-External:  
llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: isValidElementType(ElementType)  
&& "Element type of a VectorType must " "be an i

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10849#c3

ClusterFuzz testcase 5678889012035584 is flaky and no longer crashes, so  
closing issue.


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] 10 issues changed in oss-fuzz

2018-12-01 Thread infe… via monorail via llvm-bugs

Updates:
Labels: -Unreproducible Reproducible

Comment by infe...@chromium.org:
Please ignore the last comment about testcase being unreproducible. The  
testcase is still reproducible. This happened due to a code refactoring on  
ClusterFuzz side, and the underlying root cause is now fixed. Resetting the  
label back to Reproducible.


Affected issues:
  issue 4125: llvm/llvm-special-case-list-fuzzer: Heap-buffer-overflow in  
p_ere

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4125

  issue 4176: llvm/llvm-special-case-list-fuzzer: Heap-buffer-overflow in  
llvm_regcomp

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4176

  issue 4574: llvm/clang-fuzzer: ASSERT: !E->isArrow() && "missing call to  
bound member function?"

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4574

  issue 4604: llvm/clang-fuzzer: ASSERT:  
(data().DefaultedCopyConstructorIsDeleted ||  
needsOverloadResolutionForCopyConst

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4604

  issue 6052: llvm/llvm-opt-fuzzer--x86_64-gvn: ASSERT: ID <  
(MDStringRef.size()) + GlobalMetadataBitPosIndex.size()

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6052

  issue 6415: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: (DestReg !=  
AArch64::SP || Offset % 16 == 0) && "SP increment/decrement not 16-b

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6415

  issue 7167: llvm/llvm-dwarfdump-fuzzer: Abrt in  
llvm::llvm_unreachable_internal

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=7167

  issue 7177: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT:  
getMinSignedBits() <= 64 && "Too many bits for int64_t"

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=7177

  issue 7701: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: isa(Val)  
&& "cast() argument of incompatible type!"

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=7701

  issue 8037: llvm/llvm-isel-fuzzer--aarch64-O2: Abrt in  
llvm::llvm_unreachable_internal

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=8037



--
You received this message because you are listed in the owner
or CC fields of these issues, or because you starred them.
You may adjust your issue notification preferences at:
http://bugs.chromium.org/hosting/settings

___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] Issue 7690 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-licm: Out-of-memory in llvm_llvm-opt-fuzzer--x86_64-licm

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #4 on issue 7690 by ClusterFuzz-External:  
llvm/llvm-opt-fuzzer--x86_64-licm: Out-of-memory in  
llvm_llvm-opt-fuzzer--x86_64-licm

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=7690#c4

ClusterFuzz testcase 6253849095438336 appears to be flaky, updating  
reproducibility label.


--
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] 30 issues changed in oss-fuzz

2018-12-01 Thread infe… via monorail via llvm-bugs

Updates:
Labels: -Unreproducible Reproducible

Comment by infe...@chromium.org:
Please ignore the last comment about testcase being unreproducible. The  
testcase is still reproducible. This happened due to a code refactoring on  
ClusterFuzz side, and the underlying root cause is now fixed. Resetting the  
label back to Reproducible.


Affected issues:
  issue 3146: llvm: ASSERT: Access != AS_none && "Access specifier is  
AS_none inside a record decl"

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3146

  issue 3163: llvm: ASSERT: Tok.is(tok::eof) && Tok.getEofData() ==  
AttrEnd.getEofData()

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3163

  issue 3168: llvm: ASSERT: Access == AS_private || Access == AS_protected
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3168

  issue 3169: llvm: ASSERT: RHS.U.VAL != 0 && "Divide by zero?"
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3169

  issue 3171: llvm: ASSERT: RHS.U.VAL != 0 && "Divide by zero?"
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3171

  issue 3178: llvm: ASSERT: !CodeSynthesisContexts.empty()
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3178

  issue 3194: llvm: Abrt in llvm::llvm_unreachable_internal
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3194

  issue 3369: llvm: Out-of-memory in llvm_clang-format-fuzzer
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3369

  issue 3370: llvm: ASSERT: getClient() && "DiagnosticClient not set!"
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3370

  issue 3705: llvm/clang-fuzzer: ASSERT: getResultKind() == Found  
&& "getFoundDecl called on non-unique result"

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3705

  issue 3979: llvm/clang-fuzzer: ASSERT: !isNull() && "Cannot retrieve a  
NULL type pointer"

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3979

  issue 4063: llvm/clang-fuzzer: ASSERT: isa(Val) && "cast()  
argument of incompatible type!"

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4063

  issue 4192: llvm/llvm-special-case-list-fuzzer: Heap-buffer-overflow in  
p_ere

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4192

  issue 4278: llvm/clang-format-fuzzer: ASSERT: (TokenText.startswith("//")  
|| TokenText.startswith("#")) && "unsupported line c

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4278

  issue 4575: llvm/clang-fuzzer: ASSERT: DD && "queried property of class  
with no definition"

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4575

  issue 4608: llvm/clang-fuzzer: Stack-overflow in  
clang::Parser::ParseDeclaratorInternal

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4608

  issue 4701: llvm/llvm-isel-fuzzer--x86_64-O2: Direct-leak in  
llvm::MDTuple::getImpl

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4701

  issue 4704: llvm/llvm-isel-fuzzer--aarch64-gisel: Abrt in  
handleLLVMFatalError

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4704

  issue 4706: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: VSTOffset  
== 0 || !F->hasName()

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4706

  issue 4740: llvm/llvm-isel-fuzzer--aarch64-O2: Abrt in  
llvm::llvm_unreachable_internal

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4740

  issue 4755: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT:  
I.use_empty() && "Cannot erase instruction that is used!"

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4755

  issue 4978: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: NumBytes >= 0  
&& "Negative stack allocation size!?"

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4978

  issue 4988: llvm/llvm-isel-fuzzer--x86_64-O2: Abrt in  
llvm::llvm_unreachable_internal

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4988

  issue 5250: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: ((OffsetImm & 1)  
== 0) && "Unexpected offset to merge"

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5250

  issue 5426: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT:  
N->getOpcode() != ISD::DELETED_NODE && "DELETED_NODE in CSEMap!"

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5426

  issue 5446: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: getMinSignedBits()  
<= 64 && "Too many bits for int64_t"

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5446

  issue 5779: llvm/llvm-opt-fuzzer--x86_64-earlycse: ASSERT: fs == opOK ||  
fs == opInexact

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5779

  issue 6109: llvm/llvm-opt-fuzzer--x86_64-sccp: ASSERT: getActiveBits() <=  
64 && "Too many bits for uint64_t"

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6109

  issue 6477: llvm/llvm-opt-fuzzer--x86_64-loop_vectorize: ASSERT:  
VPlans.size() == 1 && "Best VF has not a single VPlan."

http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6477

  issue 6674: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT:  

[llvm-bugs] Issue 4604 in oss-fuzz: llvm/clang-fuzzer: ASSERT: (data().DefaultedCopyConstructorIsDeleted || needsOverloadResolutionForCopyConst

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #9 on issue 4604 by ClusterFuzz-External: llvm/clang-fuzzer:  
ASSERT: (data().DefaultedCopyConstructorIsDeleted ||  
needsOverloadResolutionForCopyConst

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4604#c9

ClusterFuzz testcase 5456719829270528 appears to be flaky, updating  
reproducibility label.


--
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 4574 in oss-fuzz: llvm/clang-fuzzer: ASSERT: !E->isArrow() && "missing call to bound member function?"

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #10 on issue 4574 by ClusterFuzz-External: llvm/clang-fuzzer:  
ASSERT: !E->isArrow() && "missing call to bound member function?"

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4574#c10

ClusterFuzz testcase 5223936292814848 appears to be flaky, updating  
reproducibility label.


--
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 4125 in oss-fuzz: llvm/llvm-special-case-list-fuzzer: Heap-buffer-overflow in p_ere

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #9 on issue 4125 by ClusterFuzz-External:  
llvm/llvm-special-case-list-fuzzer: Heap-buffer-overflow in p_ere

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4125#c9

ClusterFuzz testcase 6496293208719360 appears to be flaky, updating  
reproducibility label.


--
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 4537 in oss-fuzz: llvm/clang-fuzzer: ASSERT: isa(Val) && "cast() argument of incompatible type!"

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Status: WontFix

Comment #11 on issue 4537 by ClusterFuzz-External: llvm/clang-fuzzer:  
ASSERT: isa(Val) && "cast() argument of incompatible type!"

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4537#c11

ClusterFuzz testcase 5542430263738368 is flaky and no longer crashes, so  
closing issue.


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 4192 in oss-fuzz: llvm/llvm-special-case-list-fuzzer: Heap-buffer-overflow in p_ere

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Status: WontFix

Comment #11 on issue 4192 by ClusterFuzz-External:  
llvm/llvm-special-case-list-fuzzer: Heap-buffer-overflow in p_ere

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4192#c11

ClusterFuzz testcase 5534705328848896 is flaky and no longer crashes, so  
closing issue.


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 6052 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-gvn: ASSERT: ID < (MDStringRef.size()) + GlobalMetadataBitPosIndex.size()

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #5 on issue 6052 by ClusterFuzz-External:  
llvm/llvm-opt-fuzzer--x86_64-gvn: ASSERT: ID < (MDStringRef.size()) +  
GlobalMetadataBitPosIndex.size()

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6052#c5

ClusterFuzz testcase 5423687848165376 appears to be flaky, updating  
reproducibility label.


--
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 7307 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-loop_rotate: ASSERT: Amt->getType()->isIntegerTy() && "Allocation array size is not an integer!"

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Status: WontFix

Comment #6 on issue 7307 by ClusterFuzz-External:  
llvm/llvm-opt-fuzzer--x86_64-loop_rotate: ASSERT:  
Amt->getType()->isIntegerTy() && "Allocation array size is not an integer!"

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=7307#c6

ClusterFuzz testcase 5457660892676096 is flaky and no longer crashes, so  
closing issue.


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 7048 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-earlycse: ASSERT: (!LastStore || ParseMemoryInst(LastStore, TTI).getPointerOperand() == MemInst.ge

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Status: WontFix

Comment #6 on issue 7048 by ClusterFuzz-External:  
llvm/llvm-opt-fuzzer--x86_64-earlycse: ASSERT: (!LastStore ||  
ParseMemoryInst(LastStore, TTI).getPointerOperand() == MemInst.ge

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=7048#c6

ClusterFuzz testcase 5165290087251968 is flaky and no longer crashes, so  
closing issue.


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 4063 in oss-fuzz: llvm/clang-fuzzer: ASSERT: isa(Val) && "cast() argument of incompatible type!"

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Status: WontFix

Comment #10 on issue 4063 by ClusterFuzz-External: llvm/clang-fuzzer:  
ASSERT: isa(Val) && "cast() argument of incompatible type!"

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4063#c10

ClusterFuzz testcase 5116512231751680 is flaky and no longer crashes, so  
closing issue.


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 8819 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: E <= size() && "Attempted to reset out-of-bounds range!"

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #4 on issue 8819 by ClusterFuzz-External:  
llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: E <= size() && "Attempted to  
reset out-of-bounds range!"

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=8819#c4

ClusterFuzz testcase 5980804718002176 appears to be flaky, updating  
reproducibility label.


--
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 10790 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: Abrt in llvm::llvm_unreachable_internal

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Status: WontFix

Comment #2 on issue 10790 by ClusterFuzz-External:  
llvm/llvm-isel-fuzzer--aarch64-gisel: Abrt in  
llvm::llvm_unreachable_internal

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10790#c2

ClusterFuzz testcase 5157814772170752 is flaky and no longer crashes, so  
closing issue.


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 11383 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-loop_vectorize: ASSERT: !KeyInfoT::isEqual(Val, EmptyKey) && !KeyInfoT::isEqual(Val, TombstoneKey) && "E

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #2 on issue 11383 by ClusterFuzz-External:  
llvm/llvm-opt-fuzzer--x86_64-loop_vectorize:  
ASSERT: !KeyInfoT::isEqual(Val, EmptyKey) && !KeyInfoT::isEqual(Val,  
TombstoneKey) && "E

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11383#c2

ClusterFuzz testcase 576288457792 appears to be flaky, updating  
reproducibility label.


--
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 4988 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: Abrt in llvm::llvm_unreachable_internal

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Status: WontFix

Comment #7 on issue 4988 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=4988#c7

ClusterFuzz testcase 5092662118973440 is flaky and no longer crashes, so  
closing issue.


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 5250 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: ((OffsetImm & 1) == 0) && "Unexpected offset to merge"

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Status: WontFix

Comment #7 on issue 5250 by ClusterFuzz-External:  
llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: ((OffsetImm & 1) == 0)  
&& "Unexpected offset to merge"

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5250#c7

ClusterFuzz testcase 4918260140081152 is flaky and no longer crashes, so  
closing issue.


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 4608 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in clang::Parser::ParseDeclaratorInternal

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Status: WontFix

Comment #9 on issue 4608 by ClusterFuzz-External: llvm/clang-fuzzer:  
Stack-overflow in clang::Parser::ParseDeclaratorInternal

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4608#c9

ClusterFuzz testcase 4509429087076352 is flaky and no longer crashes, so  
closing issue.


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 4176 in oss-fuzz: llvm/llvm-special-case-list-fuzzer: Heap-buffer-overflow in llvm_regcomp

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #9 on issue 4176 by ClusterFuzz-External:  
llvm/llvm-special-case-list-fuzzer: Heap-buffer-overflow in llvm_regcomp

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4176#c9

ClusterFuzz testcase 6698599137148928 appears to be flaky, updating  
reproducibility label.


--
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 10790 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: Abrt in llvm::llvm_unreachable_internal

2018-12-01 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: -Reproducible Unreproducible

Comment #1 on issue 10790 by ClusterFuzz-External:  
llvm/llvm-isel-fuzzer--aarch64-gisel: Abrt in  
llvm::llvm_unreachable_internal

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10790#c1

ClusterFuzz testcase 5157814772170752 appears to be flaky, updating  
reproducibility label.


--
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


  1   2   3   >