[llvm-bugs] [Bug 37819] New: Poor vectorization with -march=skylake compared to -march=haswell
https://bugs.llvm.org/show_bug.cgi?id=37819 Bug ID: 37819 Summary: Poor vectorization with -march=skylake compared to -march=haswell Product: clang Version: 6.0 Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: -New Bugs Assignee: unassignedclangb...@nondot.org Reporter: j...@59a2.org CC: llvm-bugs@lists.llvm.org Created attachment 20432 --> https://bugs.llvm.org/attachment.cgi?id=20432=edit Source exhibiting optimizer oddity. The attached code optimizes well for Haswell and runs nearly optimally on both Haswell and Skylake. $ clang -Wall -O3 -march=haswell -ffast-math -c mm-clang.c 00e0 vmovapd ymm9,ymm6 00e4 vbroadcastsd ymm10,QWORD PTR [rdi+rbx*8-0x800] 00ee vmovupd ymm6,YMMWORD PTR [rax-0x20] 00f3 vmovupd ymm11,YMMWORD PTR [rax] 00f7 vfmadd231pd ymm1,ymm6,ymm10 00fc vfmadd231pd ymm7,ymm11,ymm10 0101 vbroadcastsd ymm10,QWORD PTR [rdi+rbx*8-0x400] 010b vfmadd231pd ymm8,ymm6,ymm10 0110 vfmadd231pd ymm5,ymm11,ymm10 0115 vbroadcastsd ymm10,QWORD PTR [rdi+rbx*8] 011b vfmadd231pd ymm2,ymm6,ymm10 0120 vfmadd231pd ymm3,ymm11,ymm10 0125 vbroadcastsd ymm10,QWORD PTR [rdi+rbx*8+0x400] 012f vfmadd213pd ymm6,ymm10,ymm9 0134 vfmadd231pd ymm4,ymm11,ymm10 0139 addrax,0x400 013f addrbx,0x1 0143 jne00e0 It is much worse when optimized for Skylake. $ clang -Wall -O3 -march=skylake -ffast-math -c mm-clang.c 0caf vmovapd YMMWORD PTR [rsp],ymm2 0cb4 vmovapd ymm2,YMMWORD PTR [rsp+0x20] 0cba vmovapd ymm3,YMMWORD PTR [rsp+0x400] 0cc3 vfmadd231pd ymm2,ymm3,ymm0 0cc8 vmovapd YMMWORD PTR [rsp+0x20],ymm2 0cce vmovapd ymm2,YMMWORD PTR [rsp+0x40] 0cd4 vfmadd231pd ymm2,ymm7,ymm0 0cd9 vmovapd YMMWORD PTR [rsp+0x40],ymm2 0cdf vmovapd ymm2,YMMWORD PTR [rsp+0x60] 0ce5 vfmadd231pd ymm2,ymm5,ymm0 0cea vmovapd YMMWORD PTR [rsp+0x60],ymm2 0cf0 vmovapd ymm2,YMMWORD PTR [rsp+0x80] 0cf9 vfmadd231pd ymm2,ymm4,ymm0 0cfe vmovapd YMMWORD PTR [rsp+0x80],ymm2 0d07 vmovapd ymm2,YMMWORD PTR [rsp+0xa0] 0d10 vfmadd231pd ymm2,ymm15,ymm0 If we drop -ffast-math, FMA instructions are no longer used (for either -march=haswell or -march=skylake). 0107 vbroadcastsd ymm9,QWORD PTR [rdi+rbx*8-0x400] 0111 vmulpd ymm12,ymm9,ymm10 0116 vaddpd ymm8,ymm8,ymm12 011b vmulpd ymm9,ymm9,ymm11 0120 vaddpd ymm6,ymm6,ymm9 I don't think -ffast-math should be needed to use FMA instructions here. It certainly isn't needed for this code with GCC or Intel compilers. -- 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 20694] msan crashes in SDL_Init on __sanitizer::ForEachMappedRegion
https://bugs.llvm.org/show_bug.cgi?id=20694 Vitaly Buka changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEW |RESOLVED CC||vitalyb...@google.com --- Comment #6 from Vitaly Buka --- Can't reproduce trunk. -- 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 34324] After r305058, AddressSanitizer CHECK failed: lib/asan/asan_errors.h:99 "((second_free_stack->size)) > ((0))" (0x0, 0x0)
https://bugs.llvm.org/show_bug.cgi?id=34324 Vitaly Buka changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #8 from Vitaly Buka --- Nothing in particular. Assumption was that it's impossible to have so many broken test for so long, and maybe someone fixed without knowing about the 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] [Bug 18320] lsan reports tons of leaks in clang due to -disable-free
https://bugs.llvm.org/show_bug.cgi?id=18320 Vitaly Buka changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |WORKSFORME CC||vitalyb...@google.com --- Comment #11 from Vitaly Buka --- We have bot which runs clang with LSAN http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-bootstrap So I assume it works as expected. -- 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 37818] New: condition_variable::wait_for () should always unlock/lock
https://bugs.llvm.org/show_bug.cgi?id=37818
Bug ID: 37818
Summary: condition_variable::wait_for () should always
unlock/lock
Product: libc++
Version: 6.0
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P
Component: All Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: le...@sophists.com
CC: llvm-bugs@lists.llvm.org, mclow.li...@gmail.com
Note - similar to 21395, except reasoning is very different.
http://en.cppreference.com/w/cpp/thread/condition_variable/wait_for says:
... Atomically releases lock, blocks the current executing thread, and adds
it to the list of threads waiting on *this
For the most part this is true with the libc++ implementation, but not when
if (__d <= __d.zero())
return cv_status::timeout;
for comparison, see
libstdc++ does
(https://gcc.gnu.org/onlinedocs/gcc-4.6.2/libstdc++/api/a00818_source.html)
template
00217 cv_status
00218 wait_until(_Lock& __lock,
00219 const chrono::time_point<_Clock, _Duration>& __atime)
00220 {
00221 unique_lock __my_lock(_M_mutex);
00222 __lock.unlock();
00223 cv_status __status = _M_cond.wait_until(__my_lock,
__atime);
00224 __lock.lock();
00225 return __status;
00226 }
unconditionally unlock/lock (even if we are going to get a timeout).
This is IMPORTANT, because if you wait_for (0) a bunch of times (stupid but not
illegal). and in another thread try to get the mutex for the variable, before
setting it, you may infinite loop (because the 'signal'ing thread never gets
the lock).
--
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 37817] New: After r325240, most ASan tests hang in urdlck on FreeBSD 12.0-CURRENT
https://bugs.llvm.org/show_bug.cgi?id=37817
Bug ID: 37817
Summary: After r325240, most ASan tests hang in urdlck on
FreeBSD 12.0-CURRENT
Product: compiler-rt
Version: unspecified
Hardware: PC
OS: FreeBSD
Status: NEW
Severity: normal
Priority: P
Component: asan
Assignee: unassignedb...@nondot.org
Reporter: dimi...@andric.com
CC: llvm-bugs@lists.llvm.org
As noted in https://reviews.llvm.org/rL325240 ("Add Xray instrumentation
support to FreeBSD"), after this commit, most ASan unit tests hang on FreeBSD
12.0-CURRENT, in the 'urdlck' state:
PID USERNAME THR PRI NICE SIZERES STATE C TIMEWCPU
COMMAND
54284 dim 1 30 10 16384G 6700K urldck 21 0:00 0.00%
Asan-x86_64-inline-
Attaching gdb to it shows the following backtrace:
(gdb) bt
#0 _umtx_op_err () at /usr/src/lib/libthr/arch/amd64/amd64/_umtx_op_err.S:37
#1 0x00080067c571 in __thr_rwlock_rdlock (rwlock=0x800696200,
flags=, tsp=) at
/usr/src/lib/libthr/thread/thr_umtx.c:307
#2 0x0008006854c0 in _thr_rwlock_rdlock (flags=0, tsp=0x0,
rwlock=) at /usr/src/lib/libthr/thread/thr_umtx.h:232
#3 _thr_rtld_rlock_acquire (lock=0x800696200) at
/usr/src/lib/libthr/thread/thr_rtld.c:125
#4 0x00080051a70b in rlock_acquire (lock=0x80052b0a0 ,
lockstate=0x7fffddd8) at /usr/src/libexec/rtld-elf/rtld_lock.c:208
#5 0x00080051336d in _rtld_bind (obj=0x800532000, reloff=1512) at
/usr/src/libexec/rtld-elf/rtld.c:812
#6 0x00080051004d in _rtld_bind_start () at
/usr/src/libexec/rtld-elf/amd64/rtld_start.S:121
#7 0x000800685313 in _thr_rtld_init () at
/usr/src/lib/libthr/thread/thr_rtld.c:240
#8 0x000800684fba in _libpthread_init (curthread=0x73e810
) at /usr/src/lib/libthr/thread/thr_init.c:365
#9 0x00080067dff2 in _thr_check_init () at
/usr/src/lib/libthr/thread/thr_private.h:925
#10 _pthread_key_create (key=0x74081c <__asan::tsd_key>, destructor=0x2e8220
<__asan::PlatformTSDDtor(void*)>) at /usr/src/lib/libthr/thread/thr_spec.c:62
#11 0x002e8153 in __asan::AsanTSDInit(void (*)(void*)) () at
/home/dim/src/llvm/llvm-325240/compiler-rt/lib/asan/asan_posix.cc:48
#12 0x002ebd1b in AsanInitInternal () at
/home/dim/src/llvm/llvm-325240/compiler-rt/lib/asan/asan_rtl.cc:426
#13 0x000800511f9d in preinit_main () at
/usr/src/libexec/rtld-elf/rtld.c:2545
#14 _rtld (sp=, exit_proc=0x7fffeb30, objp=0x7fffeb38)
at /usr/src/libexec/rtld-elf/rtld.c:766
#15 0x000800510019 in .rtld_start () at
/usr/src/libexec/rtld-elf/amd64/rtld_start.S:39
#16 0x in ?? ()
There are no other threads at this point.
--
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 37816] New: [DWARF] Add count of template methods to the class definition
https://bugs.llvm.org/show_bug.cgi?id=37816 Bug ID: 37816 Summary: [DWARF] Add count of template methods to the class definition Product: clang Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P Component: LLVM Codegen Assignee: unassignedclangb...@nondot.org Reporter: paul_robin...@playstation.sony.com CC: apra...@apple.com, clayb...@gmail.com, dblai...@gmail.com, echri...@gmail.com, lab...@google.com, llvm-bugs@lists.llvm.org Add a DWARF attribute to the class definition, reporting a count of template methods (not instantiations) defined within the class. In a discussion between myself and Greg Clayton http://lists.llvm.org/pipermail/llvm-dev/2018-June/124085.html this seemed to be a fairly cheap way to provide LLDB with useful information to help it translate DWARF into Clang ASTs without excessive performance cost. Of course this would have to be plumbed through from Clang CodeGen through DIBuilder and down into DwarfDebug, with requisite stops along the way in the bitcode reader/writer. It can't be derived within LLVM because this is a count of template *definitions* not *instantiations*. Probably worth proposing for DWARF v6; in the meantime it would have to be an LLVM extension attribute. -- 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 37815] New: Flexible array type with explicitly defined destructor.
https://bugs.llvm.org/show_bug.cgi?id=37815
Bug ID: 37815
Summary: Flexible array type with explicitly defined
destructor.
Product: clang
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: C++
Assignee: unassignedclangb...@nondot.org
Reporter: zahira.ammarguel...@intel.com
CC: dgre...@apple.com, llvm-bugs@lists.llvm.org
test.cpp:
struct A {
~A() { }
};
struct C {
int c1;
A a[];
};
bash-4.2$ clang -c test.cpp
test.cpp:6:5: error: flexible array member 'a' of type 'A []' with non-trivial
destruction
A a[];
^
1 error generated.
bash-4.2$
GCC allows this.
--
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 7096 in oss-fuzz: llvm/llvm-demangle-fuzzer: Stack-overflow in QualifiedName::printLeft
Updates: Labels: Deadline-Approaching Comment #3 on issue 7096 by sheriff...@chromium.org: llvm/llvm-demangle-fuzzer: Stack-overflow in QualifiedName::printLeft https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=7096#c3 This bug is approaching its deadline for being fixed, and will be automatically derestricted within 7 days. If a fix is planned within 2 weeks after the deadline has passed, a grace extension can be granted. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 37814] New: -Wdocumentation doesn't support Markdown
https://bugs.llvm.org/show_bug.cgi?id=37814
Bug ID: 37814
Summary: -Wdocumentation doesn't support Markdown
Product: clang
Version: 6.0
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: olive...@online.de
CC: llvm-bugs@lists.llvm.org
/// documentation
/// @code
/// std::cout << "test\n";
/// @endcode
///
/// code:
///
/// std::cout << "test\n";
///
/// \return exitcode
int main() {
return 0;
}
produces the following message since the Markdown intendation-based code block
is not being recognized
/mnt/c/clion/example/src/main.cpp:8:27: error: unknown command tag name
[-Werror,-Wdocumentation-unknown-command]
/// std::cout << "test\n";
^~
Both blocks generate code blocks in the documentation.
doxygen 1.8.0 added support for Markdown
https://www.stack.nl/~dimitri/doxygen/manual/markdown.html#md_codeblock
--
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 37813] New: -Wdocumentation-unknown-command does not recognize @private
https://bugs.llvm.org/show_bug.cgi?id=37813
Bug ID: 37813
Summary: -Wdocumentation-unknown-command does not recognize
@private
Product: clang
Version: 6.0
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: olive...@online.de
CC: llvm-bugs@lists.llvm.org
This code
/// @private
int main() {
return 0;
}
produces the following warning
/mnt/c/clion/example/src/main.cpp:1:5: error: unknown command tag name
[-Werror,-Wdocumentation-unknown-command]
/// @private
^~~~
Unfortunately you cannot use -fcomment-block-commands=private to silence the
wrning since that tag can used without any other information leading to this
warning:
/mnt/c/clion/example/src/main.cpp:1:13: error: empty paragraph passed to
'@private' command [-Werror,-Wdocumentation]
/// @private
^
The tag is defined by doxygen
https://www.stack.nl/~dimitri/doxygen/manual/commands.html#cmdprivate
--
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 37603] Missed canonicalization for bit mask calculation
https://bugs.llvm.org/show_bug.cgi?id=37603 Roman Lebedev changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #11 from Roman Lebedev --- Relanded in r334818 -- 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 8906 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: Stack-overflow in llvm::DAGTypeLegalizer::RemapId
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.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-06-15 Type: Bug New issue 8906 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-gisel: Stack-overflow in llvm::DAGTypeLegalizer::RemapId https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=8906 Detailed report: https://oss-fuzz.com/testcase?key=5342672469360640 Project: llvm Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--aarch64-gisel Fuzz target binary: llvm-isel-fuzzer--aarch64-gisel Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffe5a28eff8 Crash State: llvm::DAGTypeLegalizer::RemapId Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201806130804:201806142218 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5342672469360640 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 8573 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in clang::Sema::isTemplateName
Updates: Status: WontFix Comment #3 on issue 8573 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in clang::Sema::isTemplateName https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=8573#c3 ClusterFuzz testcase 4889727105761280 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 8237 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in llvm::StringMapImpl::LookupBucketFor
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #4 on issue 8237 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in llvm::StringMapImpl::LookupBucketFor https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=8237#c4 ClusterFuzz testcase 6323051007311872 is verified as fixed, so closing issue as verified. If this is incorrect, please file a bug on https://github.com/google/oss-fuzz/issues/new -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 8714 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in llvm::SmallVectorBase::grow_pod
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #3 on issue 8714 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in llvm::SmallVectorBase::grow_pod https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=8714#c3 ClusterFuzz testcase 6002306800680960 is verified as fixed, so closing issue as verified. If this is incorrect, please file a bug on https://github.com/google/oss-fuzz/issues/new -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 8573 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in clang::Sema::isTemplateName
Updates: Labels: -Reproducible Unreproducible Comment #2 on issue 8573 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in clang::Sema::isTemplateName https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=8573#c2 ClusterFuzz testcase 4889727105761280 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 8222 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in llvm::detail::IEEEFloat::convertFromStringSpecials
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #3 on issue 8222 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in llvm::detail::IEEEFloat::convertFromStringSpecials https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=8222#c3 ClusterFuzz testcase 5412205699792896 is verified as fixed, so closing issue as verified. If this is incorrect, please file a bug on https://github.com/google/oss-fuzz/issues/new -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 8119 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in clang::StmtVisitorBase::Visit
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #3 on issue 8119 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in clang::StmtVisitorBaseIntExprEvaluator, bool>::Visit https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=8119#c3 ClusterFuzz testcase 5374688455819264 is verified as fixed, so closing issue as verified. If this is incorrect, please file a bug on https://github.com/google/oss-fuzz/issues/new -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 8237 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in llvm::StringMapImpl::LookupBucketFor
Comment #3 on issue 8237 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in llvm::StringMapImpl::LookupBucketFor https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=8237#c3 ClusterFuzz has detected this issue as fixed in range 201806130804:201806142218. Detailed report: https://oss-fuzz.com/testcase?key=6323051007311872 Project: llvm Fuzzer: libFuzzer_llvm_clang-fuzzer Fuzz target binary: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffd24bdcf28 Crash State: llvm::StringMapImpl::LookupBucketFor std::__1::pair, bool> llvm::Stri clang::Preprocessor::LookUpIdentifierInfo Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201805070541:201805080541 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201806130804:201806142218 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6323051007311872 See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 8714 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in llvm::SmallVectorBase::grow_pod
Comment #2 on issue 8714 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in llvm::SmallVectorBase::grow_pod https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=8714#c2 ClusterFuzz has detected this issue as fixed in range 201806130804:201806142218. Detailed report: https://oss-fuzz.com/testcase?key=6002306800680960 Project: llvm Fuzzer: libFuzzer_llvm_clang-fuzzer Fuzz target binary: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffe1e5d9818 Crash State: llvm::SmallVectorBase::grow_pod clang::CharLiteralParser::CharLiteralParser clang::Sema::ActOnCharacterConstant Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201712080609:201712090607 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201806130804:201806142218 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6002306800680960 See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 8222 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in llvm::detail::IEEEFloat::convertFromStringSpecials
Comment #2 on issue 8222 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in llvm::detail::IEEEFloat::convertFromStringSpecials https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=8222#c2 ClusterFuzz has detected this issue as fixed in range 201806130804:201806142218. Detailed report: https://oss-fuzz.com/testcase?key=5412205699792896 Project: llvm Fuzzer: libFuzzer_llvm_clang-fuzzer Fuzz target binary: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffddb5898b8 Crash State: llvm::detail::IEEEFloat::convertFromStringSpecials llvm::detail::IEEEFloat::convertFromString clang::NumericLiteralParser::GetFloatValue Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201805080541:201805100547 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201806130804:201806142218 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5412205699792896 See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 8119 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in clang::StmtVisitorBase::Visit
Comment #2 on issue 8119 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in clang::StmtVisitorBaseIntExprEvaluator, bool>::Visit https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=8119#c2 ClusterFuzz has detected this issue as fixed in range 201806130804:201806142218. Detailed report: https://oss-fuzz.com/testcase?key=5374688455819264 Project: llvm Fuzzer: libFuzzer_llvm_clang-fuzzer Fuzz target binary: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7fff774ac7c0 Crash State: clang::StmtVisitorBasebool>::Visit Evaluate IntExprEvaluator::VisitCastExpr Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201711160610:201712080609 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201806130804:201806142218 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5374688455819264 See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 7734 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-strength_reduce: ASSERT: !BaseRegs.empty() && "1*reg => reg, should not be needed."
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #4 on issue 7734 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-strength_reduce: ASSERT: !BaseRegs.empty() && "1*reg => reg, should not be needed." https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=7734#c4 ClusterFuzz testcase 6305547449008128 is verified as fixed, so closing issue as verified. If this is incorrect, please file a bug on https://github.com/google/oss-fuzz/issues/new -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 8861 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-strength_reduce: ASSERT: !BaseReg->isZero() && "Zero allocated in a base register!"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #3 on issue 8861 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-strength_reduce: ASSERT: !BaseReg->isZero() && "Zero allocated in a base register!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=8861#c3 ClusterFuzz testcase 6195708003614720 is verified as fixed, so closing issue as verified. If this is incorrect, please file a bug on https://github.com/google/oss-fuzz/issues/new -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 8861 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-strength_reduce: ASSERT: !BaseReg->isZero() && "Zero allocated in a base register!"
Comment #2 on issue 8861 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-strength_reduce: ASSERT: !BaseReg->isZero() && "Zero allocated in a base register!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=8861#c2 ClusterFuzz has detected this issue as fixed in range 201806130804:201806142218. Detailed report: https://oss-fuzz.com/testcase?key=6195708003614720 Project: llvm Fuzzer: libFuzzer_llvm_llvm-opt-fuzzer--x86_64-strength_reduce Fuzz target binary: llvm-opt-fuzzer--x86_64-strength_reduce Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: !BaseReg->isZero() && "Zero allocated in a base register!" LSRInstance::InsertFormula LSRInstance::GenerateAllReuseFormulae Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201806110750:201806120754 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201806130804:201806142218 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6195708003614720 See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 7734 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-strength_reduce: ASSERT: !BaseRegs.empty() && "1*reg => reg, should not be needed."
Comment #3 on issue 7734 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-strength_reduce: ASSERT: !BaseRegs.empty() && "1*reg => reg, should not be needed." https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=7734#c3 ClusterFuzz has detected this issue as fixed in range 201806130804:201806142218. Detailed report: https://oss-fuzz.com/testcase?key=6305547449008128 Project: llvm Fuzzer: libFuzzer_llvm_llvm-opt-fuzzer--x86_64-strength_reduce Fuzz target binary: llvm-opt-fuzzer--x86_64-strength_reduce Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: !BaseRegs.empty() && "1*reg => reg, should not be needed." Formula::canonicalize LSRInstance::GenerateReassociationsImpl Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201802210603:201802211531 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201806130804:201806142218 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6305547449008128 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
