[llvm-bugs] Issue 24260 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::DeclSpec::Finish
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, d...@google.com, mit...@google.com, bigchees...@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 OS-Linux Proj-llvm Reported-2020-07-19 Type: Bug New issue 24260 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::DeclSpec::Finish https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=24260 Detailed Report: https://oss-fuzz.com/testcase?key=6574460396896256 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffdc977bfc0 Crash State: clang::DeclSpec::Finish clang::Parser::ParseDeclarationSpecifiers clang::Parser::ParseSpecifierQualifierList Sanitizer: address (ASAN) Crash Revision: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&revision=202007180156 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6574460396896256 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally. When you fix this bug, please * mention the fix revision(s). * state whether the bug was a short-lived regression or an old bug in any stable releases. * add any other useful information. This information can help downstream consumers. If you need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 46775] New: lldb needs to handle auto
https://bugs.llvm.org/show_bug.cgi?id=46775
Bug ID: 46775
Summary: lldb needs to handle auto
Product: lldb
Version: 11.0
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: All Bugs
Assignee: lldb-...@lists.llvm.org
Reporter: tras...@gmail.com
CC: jdevliegh...@apple.com, llvm-bugs@lists.llvm.org
When compiling clangd with clang it generates the following debug info:
Abbrev Number: 166 (DW_TAG_unspecified_type)
DW_AT_name: (indexed string: 0xb0c6): auto
This is not handled in DWARFASTParserClang::ParseTypeModifier:
case DW_TAG_unspecified_type:
if (attrs.name == "nullptr_t" || attrs.name == "decltype(nullptr)") {
resolve_state = Type::ResolveState::Full;
clang_type = m_ast.GetBasicType(eBasicTypeNullPtr);
break;
}
// Fall through to base type below in case we can handle the type
// there...
LLVM_FALLTHROUGH;
case DW_TAG_base_type:
And due to the fallthrough this results in the following (somewhat misleading)
error message:
error: need to add support for DW_TAG_base_type 'auto' encoded with DW_ATE =
0x0, bit_size = 0
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 46680] ICE in backend: Instruction Combining seems stuck in an infinite loop after 100 iterations
https://bugs.llvm.org/show_bug.cgi?id=46680 Nikita Popov changed: What|Removed |Added Resolution|--- |FIXED Fixed By Commit(s)||d12ec0f752e7f2c7f7252539da2 ||d124264ec33f7 Status|NEW |RESOLVED --- Comment #10 from Nikita Popov --- Fixed by https://reviews.llvm.org/D84109. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 46725] [meta] 11.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=46725 Bug 46725 depends on bug 46680, which changed state. Bug 46680 Summary: ICE in backend: Instruction Combining seems stuck in an infinite loop after 100 iterations https://bugs.llvm.org/show_bug.cgi?id=46680 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 46725] [meta] 11.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=46725 Bug 46725 depends on bug 46680, which changed state. Bug 46680 Summary: ICE in backend: Instruction Combining seems stuck in an infinite loop after 100 iterations https://bugs.llvm.org/show_bug.cgi?id=46680 What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 46680] ICE in backend: Instruction Combining seems stuck in an infinite loop after 100 iterations
https://bugs.llvm.org/show_bug.cgi?id=46680 Roman Lebedev changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #11 from Roman Lebedev --- (Still needs to be cherry-picked, no?) -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 46776] New: bogus -Wmissing-braces for CTAD deduced aggregate with inherited base
https://bugs.llvm.org/show_bug.cgi?id=46776
Bug ID: 46776
Summary: bogus -Wmissing-braces for CTAD deduced aggregate with
inherited base
Product: clang
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: C++17
Assignee: unassignedclangb...@nondot.org
Reporter: wjw...@gmail.com
CC: blitzrak...@gmail.com, erik.pilking...@gmail.com,
llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk
Combination of aggregate CTAD and inheritance makes -Wmissing-braces wrong.
For example, take a tuple class with the usual CTAD:
https://wandbox.org/permlink/USZGcupYvTtP8D6D
template struct tuple;
template tuple(T...) -> tuple;
Implement it as an aggregate, by explicit specializations:
template <> struct tuple<> {};
template struct tuple {A a;};
template struct tuple {A a; B b;};
... & etc.
Now, 'tie' is usually implemented as a helper 'make' function tie(...)
Instead, implement tie as a class inheriting from tuple, with CTAD
template struct tie : tuple {};
template tie(T&...) -> tie;
along with an extra tuple CTAD converting from tie to tuple
template tuple(tie) -> tuple;
Now, usage of tie looks like this:
bool up = true;
tuple t = tie{up};
warning: suggest braces around initialization of subobject [-Wmissing-braces]
tuple t = tie{up};
^~
{ }
1 warning generated.
However, this warning is incorrect here -
adding the suggested braces breaks the CTAD deduction.
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
