[llvm-bugs] [Bug 40017] lld and clang do not have proper permissions
https://bugs.llvm.org/show_bug.cgi?id=40017 Sylvestre Ledru changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #1 from Sylvestre Ledru --- Should be fixed soon, I triggered all builds. *** This bug has been marked as a duplicate of bug 39951 *** -- 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 40019] New: [X86][VBMI2] Refactor vpshldv instructions as funnel shifts
https://bugs.llvm.org/show_bug.cgi?id=40019 Bug ID: 40019 Summary: [X86][VBMI2] Refactor vpshldv instructions as funnel shifts Product: libraries Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: Backend: X86 Assignee: unassignedb...@nondot.org Reporter: llvm-...@redking.me.uk CC: craig.top...@gmail.com, llvm-bugs@lists.llvm.org, llvm-...@redking.me.uk, spatel+l...@rotateright.com These can be treated as generic funnel shift intrinsics, and we just need special case custom lowering to handle the immediate 'mm512_shldi' form (like we do for vector rotations). -- 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 40020] New: Illegitimate warning for -Wfloat-conversion
https://bugs.llvm.org/show_bug.cgi?id=40020
Bug ID: 40020
Summary: Illegitimate warning for -Wfloat-conversion
Product: clang
Version: 7.0
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: ltcm...@gmail.com
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org,
neeil...@live.com, richard-l...@metafoo.co.uk
When compiling the C snippet below with -Wconversion, clangs throws the
warning -Wfloat-conversion for (i) expression `x = y', and (ii) for expression
`0 || y'.
int f()
{
int x;
double y;
x = y;
0 || y;
return 0;
}
My interpretation is that the warning for (ii) is not legitimate and should be
removed. As opposed to 6.3.1.4[floating point conversion], where truncation is
defined upon a conversion (e.g., as in an assignment), section 6.5.14 only
relates to the notion of comparison. In particular, it is relevant whether an
operand compare to 0 (the same of a integral of floating point), given the
logical OR only requires that its operands are of scalar type.
GCC 7.3 only produces the warning for case (i), which is according to my
expectation, as described above.
--
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 10250 in oss-fuzz: llvm: Build failure
Comment #22 on issue 10250 by ClusterFuzz-External: llvm: Build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10250#c22 Friendly reminder that the the build is still failing. Please try to fix this failure to ensure that fuzzing remains productive. Latest build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-045eb761-6066-41fe-9173-79220550b6ba.txt -- 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 40021] New: [PPC64/PPC64LE] Call of __attribute__((noreturn)) generates suboptimal code
https://bugs.llvm.org/show_bug.cgi?id=40021
Bug ID: 40021
Summary: [PPC64/PPC64LE] Call of __attribute__((noreturn))
generates suboptimal code
Product: libraries
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Backend: PowerPC
Assignee: unassignedb...@nondot.org
Reporter: simonas+llvm@kazlauskas.me
CC: llvm-bugs@lists.llvm.org, nemanja.i@gmail.com
Created attachment 21223
--> https://bugs.llvm.org/attachment.cgi?id=21223&action=edit
LLVM-IR test case
The following C code
typedef long long unsigned int uint64_t;
void __attribute__((noreturn)) test(uint64_t a, uint64_t b, uint64_t
__attribute__((noreturn)) (*cb)(uint64_t, uint64_t)) {
cb(a, b);
}
which generates the following LLVM-IR (clang 6)
define void @test(i64, i64, i64 (i64, i64)* nocapture) local_unnamed_addr #0 {
%4 = tail call i64 %2(i64 %0, i64 %1) #1
unreachable
}
results in unnecessary instructions after the call when ppc64le is targeted:
mtctr 5
mr 12, 5
std 2, 24(1) /* what for? */
bctrl
ld 2, 24(1) /* what for? */
The full LLVM-IR is attached.
--
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 40022] New: Assertion failure in RegionStoreManager::bindArray()
https://bugs.llvm.org/show_bug.cgi?id=40022
Bug ID: 40022
Summary: Assertion failure in RegionStoreManager::bindArray()
Product: clang
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Static Analyzer
Assignee: dcough...@apple.com
Reporter: hok...@google.com
CC: dcough...@apple.com, llvm-bugs@lists.llvm.org
$ cat test-RegionStoreManager__bindArray.cc
struct f {
typedef int b[];
};
struct g {
f::b c;
};
using d = long;
using e = g;
struct i {
d cookie;
};
struct j : i {
e h;
};
void k() { j a{}; }
$ ./clang-tidy -checks="-*,clang-analyzer*"
test-RegionStoreManager__bindArray.cc -- -std=c++17
F1214 14:18:39.208130 39861 logging.cc:82] assert.h assertion failed at
third_party/llvm/llvm/tools/clang/include/clang/StaticAnalyzer/Core/PathSensitive/SVals.h:105
in T clang::ento::SVal::castAs() const [T = clang::ento::nonloc::CompoundVal]:
T::isKind(*this)
*** Check failure stack trace: ***
@ 0x56443e738c76 __assert_fail
@ 0x56443c254b15 (anonymous
namespace)::RegionStoreManager::bindArray()
@ 0x56443c255073 (anonymous
namespace)::RegionStoreManager::bindStruct()
@ 0x56443c25516b (anonymous
namespace)::RegionStoreManager::bindStruct()
@ 0x56443c24a798 (anonymous namespace)::RegionStoreManager::Bind()
@ 0x56443c264e5f clang::ento::ProgramState::bindLoc()
@ 0x56443c02e069
clang::ento::retaincountchecker::RetainCountChecker::checkBind()
@ 0x56443c035466 clang::ento::check::Bind::_checkBind<>()
@ 0x56443c2a1629 clang::ento::CheckerManager::runCheckersForBind()
@ 0x56443c2b4eb3 clang::ento::ExprEngine::evalBind()
@ 0x56443c2d424e clang::ento::ExprEngine::VisitDeclStmt()
@ 0x56443c2b43fd clang::ento::ExprEngine::Visit()
@ 0x56443c2b06af clang::ento::ExprEngine::ProcessStmt()
@ 0x56443c2b0398 clang::ento::ExprEngine::processCFGElement()
@ 0x56443c2ce4c5 clang::ento::CoreEngine::HandlePostStmt()
@ 0x56443c2cd8be clang::ento::CoreEngine::ExecuteWorkList()
@ 0x56443bfd2715 (anonymous namespace)::AnalysisConsumer::HandleCode()
@ 0x56443bfbdd50 (anonymous
namespace)::AnalysisConsumer::HandleTranslationUnit()
@ 0x56443c53120c clang::MultiplexConsumer::HandleTranslationUnit()
@ 0x56443c6ec414 clang::ParseAST()
@ 0x56443c52ad63 clang::FrontendAction::Execute()
@ 0x56443c3df7e1 clang::CompilerInstance::ExecuteAction()
@ 0x56443c3387d1
clang::tooling::FrontendActionFactory::runInvocation()
@ 0x56443bc3ac27
clang::tidy::runClangTidy()::ActionFactory::runInvocation()
@ 0x56443c33853a clang::tooling::ToolInvocation::runInvocation()
@ 0x56443c337f26 clang::tooling::ToolInvocation::run()
@ 0x56443c33a625 clang::tooling::ClangTool::run()
@ 0x56443bc3696f clang::tidy::runClangTidy()
@ 0x5644396051f4 main
--
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 39991] Memory leaks detected when running check-clangd with ASan
https://bugs.llvm.org/show_bug.cgi?id=39991 hokein changed: What|Removed |Added CC||hok...@google.com Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from hokein --- Fixed in rL349145. -- 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 11795 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in clang::DiagnosticIDs::isUnrecoverable
Comment #1 on issue 11795 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in clang::DiagnosticIDs::isUnrecoverable https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11795#c1 ClusterFuzz has detected this issue as fixed in range 201812130233:201812140233. Detailed report: https://oss-fuzz.com/testcase?key=5751748677861376 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: 0x7fff5ac75b08 Crash State: clang::DiagnosticIDs::isUnrecoverable clang::DiagnosticIDs::ProcessDiag clang::DiagnosticsEngine::EmitCurrentDiagnostic Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201803270519:201803280525 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201812130233:201812140233 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5751748677861376 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 11423 in oss-fuzz: llvm/llvm-special-case-list-fuzzer: Timeout in llvm_llvm-special-case-list-fuzzer
Comment #4 on issue 11423 by ClusterFuzz-External: llvm/llvm-special-case-list-fuzzer: Timeout in llvm_llvm-special-case-list-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11423#c4 ClusterFuzz has detected this issue as fixed in range 201812130233:201812140233. Detailed report: https://oss-fuzz.com/testcase?key=5712296123301888 Project: llvm Fuzzer: libFuzzer_llvm_llvm-special-case-list-fuzzer Fuzz target binary: llvm-special-case-list-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: llvm_llvm-special-case-list-fuzzer Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201711070608:201711090621 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201812130233:201812140233 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5712296123301888 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 40023] New: format security warnings not generated for printf calls in template
https://bugs.llvm.org/show_bug.cgi?id=40023
Bug ID: 40023
Summary: format security warnings not generated for printf
calls in template
Product: clang
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: Frontend
Assignee: unassignedclangb...@nondot.org
Reporter: yshu...@gmail.com
CC: llvm-bugs@lists.llvm.org, neeil...@live.com,
richard-l...@metafoo.co.uk
Code example:
#include
#include
template
void p(const char *fmt, const Args & ... args) {
std::printf(fmt, args...);
}
int main() {
//p("asdfasdf"); // warning generated for this one
p("%d", 1); // but not this one
}
compiler explorer link: https://godbolt.org/z/O8mCQj
--
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 11423 in oss-fuzz: llvm/llvm-special-case-list-fuzzer: Timeout in llvm_llvm-special-case-list-fuzzer
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #5 on issue 11423 by ClusterFuzz-External: llvm/llvm-special-case-list-fuzzer: Timeout in llvm_llvm-special-case-list-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11423#c5 ClusterFuzz testcase 5712296123301888 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 11795 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in clang::DiagnosticIDs::isUnrecoverable
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 11795 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in clang::DiagnosticIDs::isUnrecoverable https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11795#c2 ClusterFuzz testcase 5751748677861376 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 11773 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-indvars: Timeout in llvm_llvm-opt-fuzzer--x86_64-indvars
Comment #2 on issue 11773 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=11773#c2 ClusterFuzz has detected this issue as fixed in range 201812130233:201812140233. Detailed report: https://oss-fuzz.com/testcase?key=5720985035079680 Project: llvm Fuzzer: libFuzzer_llvm_llvm-opt-fuzzer--x86_64-indvars Fuzz target binary: llvm-opt-fuzzer--x86_64-indvars Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: llvm_llvm-opt-fuzzer--x86_64-indvars Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201802210603:201802211531 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201812130233:201812140233 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5720985035079680 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 11773 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-indvars: Timeout in llvm_llvm-opt-fuzzer--x86_64-indvars
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #3 on issue 11773 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=11773#c3 ClusterFuzz testcase 5720985035079680 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 40024] New: Assertion on instantiating function definition from template type function
https://bugs.llvm.org/show_bug.cgi?id=40024
Bug ID: 40024
Summary: Assertion on instantiating function definition from
template type function
Product: clang
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P
Component: C++'17
Assignee: unassignedclangb...@nondot.org
Reporter: christian.br...@st.com
CC: blitzrak...@gmail.com, erik.pilking...@gmail.com,
llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk
Created attachment 21224
--> https://bugs.llvm.org/attachment.cgi?id=21224&action=edit
reproduce -stdc++17
The attached code compiled with
clang++ -std=c++17 bug.C
asserts with
lib/Sema/SemaTemplate.cpp:6814: clang::ExprResult
clang::Sema::BuildExpressionFromDeclTemplateArgument(const
clang::TemplateArgument&, clang::QualType, clang::SourceLocation): Assertion
`!RefExpr.isInvalid() && Context.hasSameType(((Expr*)
RefExpr.get())->getType(), ParamType.getUnqualifiedType())' failed.
I'm not sure it is valid c++17. it compiles fine with c++11 and returns the
following error with g++:
error: 'int (S::*)(){((int (S::*)())S::f<110>), 0}' is not a valid template
argument for type 'int (S::*)()'
--
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 39845] [DebugInfo@O2] CodeGenPrepare drops reference to local in dbg.value intrinsic
https://bugs.llvm.org/show_bug.cgi?id=39845 Wolfgang Pieb changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Wolfgang Pieb --- Fixed with r348896. -- 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 38768] [meta][DebugInfo] Umbrella bug for poor debug experiences
https://bugs.llvm.org/show_bug.cgi?id=38768 Bug 38768 depends on bug 39845, which changed state. Bug 39845 Summary: [DebugInfo@O2] CodeGenPrepare drops reference to local in dbg.value intrinsic https://bugs.llvm.org/show_bug.cgi?id=39845 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40025] New: AArch32 and AArch64 fail to generate vsubl from intrinsics
https://bugs.llvm.org/show_bug.cgi?id=40025 Bug ID: 40025 Summary: AArch32 and AArch64 fail to generate vsubl from intrinsics Product: new-bugs Version: unspecified Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: resis...@mac.com CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org For certain quantized neural network kernels in the QNNPACK library (https://github.com/pytorch/QNNPACK) LLVM fails to generate vsubl instructions from vsubl intrinsics, resulting in up to 2x performance degradation compared to hand-written assembly. The basic symptom is that the vsubl intrinsic is being split into extends + subs. One of the extends is determined to be loop invariant and hoisted out of the loop. This is actually undesirable because it results in the extend of the other operand needing to be explicitly extended inside the loop rather than being implicitly extended as part of a vsubl. I'm attaching two reduced test cases. singleuse.cpp presents a simpler version with only a single vsubl inside the loop. It's relatively easy to write a profitable CodeGenPrepare rule that reverses the LICM using hasOneUse checks. multiuser.cpp is a more realistic example including multiple vsubl's using the same RHS operand, inside nested control flow within the loop. Handling this case properly isn't trivial. -- 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 40026] New: This Invalid Mangling causes crash in llvm-undname: "?ff@@$$J0YAXAU?$AS_@$0A@PEAU?$AS_@$0A@H@__clang@@@__clang@@@Z"
https://bugs.llvm.org/show_bug.cgi?id=40026 Bug ID: 40026 Summary: This Invalid Mangling causes crash in llvm-undname: "?ff@@$$J0YAXAU?$AS_@$0A@PEAU?$AS_@$0A@H@__clang@@@__c lang@@@Z" Product: tools Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P Component: llvm-c++filt Assignee: unassignedb...@nondot.org Reporter: erich.ke...@intel.com CC: llvm-bugs@lists.llvm.org This name: "?ff@@$$J0YAXAU?$ASbash-4.2$ llvm-undname "?ff@@$$J0YAXAU?$AS_@$0A@PEAU?$AS_@$0A@H@__clang@@@__clang@@@Z" ~ ?ff@@22900J0YAXAU?@-/bin/bashA@PEAU?@-/bin/bashA@H@__clang@@@__clang@@@Z ~ Stack dump: ~ 0. Program arguments: llvm-undname ?ff@@22900J0YAXAU?@-/bin/bashA@PEAU?@-/bin/bashA@H@__clang@@@__clang@@@Z ~ LLVMSymbolizer: error reading file: No such file or directory ~ #0 0x7f62bcf8c8fa llvm::sys::PrintStackTrace(llvm::raw_ostream&) /export/iusers/ekeane1/workspaces/llorg/llvm/lib/Support/Unix/Signals.inc:495:22 ~ #1 0x7f62bcf8c98d PrintStackTraceSignalHandler(void*) /export/iusers/ekeane1/workspaces/llorg/llvm/lib/Support/Unix/Signals.inc:559:1 ~ #2 0x7f62bcf8a99f llvm::sys::RunSignalHandlers() /export/iusers/ekeane1/workspaces/llorg/llvm/lib/Support/Signals.cpp:67:20 ~ #3 0x7f62bcf8c3bf SignalHandler(int) /export/iusers/ekeane1/workspaces/llorg/llvm/lib/Support/Unix/Signals.inc:358:1 ~ #4 0x7f62bad7a5e0 __restore_rt (/lib64/libpthread.so.0+0xf5e0) ~ #5 0x7f62bcd94abc llvm::ms_demangle::Node::kind() const /export/iusers/ekeane1/workspaces/llorg/llvm/include/llvm/Demangle/MicrosoftDemangleNodes.h:234:34 ~ #6 0x7f62bcd8f924 llvm::ms_demangle::Demangler::demangleVariableEncoding(StringView&, llvm::ms_demangle::StorageClass) /export/iusers/ekeane1/workspaces/llorg/llvm/lib/Demangle/MicrosoftDemangle.cpp:762:3 ~ #7 0x7f62bcd8f64d llvm::ms_demangle::Demangler::demangleEncodedSymbol(StringView&, llvm::ms_demangle::QualifiedNameNode*) /export/iusers/ekeane1/workspaces/llorg/llvm/lib/Demangle/MicrosoftDemangle.cpp:679:52 ~ #8 0x7f62bcd8f7eb llvm::ms_demangle::Demangler::parse(StringView&) /export/iusers/ekeane1/workspaces/llorg/llvm/lib/Demangle/MicrosoftDemangle.cpp:725:45 ~ #9 0x7f62bcd9451a llvm::microsoftDemangle(char const*, char*, unsigned long*, int*, llvm::MSDemangleFlags) /export/iusers/ekeane1/workspaces/llorg/llvm/lib/Demangle/MicrosoftDemangle.cpp:2190:28 ~ #10 0x00405870 (llvm-undname+0x405870) ~ #11 0x00405db8 (llvm-undname+0x405db8) ~ #12 0x7f62ba12bc05 __libc_start_main (/lib64/libc.so.6+0x21c05) ~ #13 0x00405769 (llvm-undname+
[llvm-bugs] [Bug 40027] New: [X86] cmov conversion hurts binary search performance
https://bugs.llvm.org/show_bug.cgi?id=40027 Bug ID: 40027 Summary: [X86] cmov conversion hurts binary search performance Product: libraries Version: trunk Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: Backend: X86 Assignee: unassignedb...@nondot.org Reporter: nikita@gmail.com CC: craig.top...@gmail.com, llvm-bugs@lists.llvm.org, llvm-...@redking.me.uk, spatel+l...@rotateright.com Originally reported at: https://github.com/rust-lang/rust/issues/53823 The cmov conversion pass converts a cmov in Rust's binary search implementation into a branch. As binary search branches are badly predicted, this significantly hurts performance. For small data sets, which are not dominated by cache performance, the slowdown is around 2-3x. https://gist.github.com/nikic/13e907d7097f74a92d082fcc61bc212c has the LLVM IR for the function, as well as generated assembly with cmov conversion enabled (default) and disabled (-x86-cmov-converter=false). It would be great if the cmov conversion heuristics could be adjusted in some way to avoid converting this case. -- 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 40028] New: Allow -Wno-pass-failed=pass-name-regex
https://bugs.llvm.org/show_bug.cgi?id=40028 Bug ID: 40028 Summary: Allow -Wno-pass-failed=pass-name-regex Product: clang Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: Frontend Assignee: unassignedclangb...@nondot.org Reporter: ruppre...@google.com CC: llvm-bugs@lists.llvm.org, neeil...@live.com, richard-l...@metafoo.co.uk -Wno-pass-failed suppresses warnings from all passes that fail, but does not have an overload that allows suppressing warnings from just a particular pass. I propose also allowing -Wno-pass-failed=pass-name-regex to suppress only warnings from certain passes. -- 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 39994] Converting invoke to call does not transfer "MD_mem_parallel_loop_access" metadata
https://bugs.llvm.org/show_bug.cgi?id=39994 Michael Kruse changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED Fixed By Commit(s)||r349170 -- 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 38996] SmallBitVector::find_last gives incorrect results with small types
https://bugs.llvm.org/show_bug.cgi?id=38996 Zachary Turner changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Zachary Turner --- This is fixed by r349173. -- 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 40029] New: test /test/CodeGenOpenCL/address-spaces-mangling.cl Broken (as is address-space-map-mangling=no)
https://bugs.llvm.org/show_bug.cgi?id=40029
Bug ID: 40029
Summary: test /test/CodeGenOpenCL/address-spaces-mangling.cl
Broken (as is address-space-map-mangling=no)
Product: clang
Version: 7.0
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: OpenCL
Assignee: unassignedclangb...@nondot.org
Reporter: erich.ke...@intel.com
CC: anastasia.stul...@arm.com, llvm-bugs@lists.llvm.org
A bunch of the test-prefixes are incorrect, which causes it to not properly
test in the address-space-map-mangling=no case.
There are a bunch named ASMAN10/ASMAN20/NOASMAN10/NOASMAN20 that are actually
spelled with a "G" (ASMANG10) in the space below.
Fixing these causes the test to fail in the 'NO' cases:
--
/export/iusers/ekeane1/workspaces/llorg/llvm/tools/clang/test/CodeGenOpenCL/address-spaces-mangling.cl:17:16:
error: NOASMANG10: expected string not found in input
// NOASMANG10: @_Z2ffPi
^
:1:1: note: scanning from here
; ModuleID =
'/export/iusers/ekeane1/workspaces/llorg/llvm/tools/clang/test/CodeGenOpenCL/address-spaces-mangling.cl'
^
:7:13: note: possible intended match here
define void @_Z2ffPU9CLprivatei(i32* nocapture %arg) local_unnamed_addr #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
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 11854 in oss-fuzz: llvm/clang-fuzzer: Out-of-memory in llvm_clang-fuzzer
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 Reproducible Engine-libfuzzer Proj-llvm Reported-2018-12-14 Type: Bug New issue 11854 by ClusterFuzz-External: llvm/clang-fuzzer: Out-of-memory in llvm_clang-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11854 Detailed report: https://oss-fuzz.com/testcase?key=5654591048253440 Project: llvm Fuzzer: libFuzzer_llvm_clang-fuzzer Fuzz target binary: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Out-of-memory (exceeds 2048 MB) Crash Address: Crash State: llvm_clang-fuzzer Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201712090607:201712100011 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5654591048253440 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 40030] New: Designated initialisers - diagnose invalid designator order in C++20
https://bugs.llvm.org/show_bug.cgi?id=40030
Bug ID: 40030
Summary: Designated initialisers - diagnose invalid designator
order in C++20
Product: clang
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: C++2a
Assignee: unassignedclangb...@nondot.org
Reporter: david.bolvan...@gmail.com
CC: blitzrak...@gmail.com, erik.pilking...@gmail.com,
llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk
struct S
{
int number;
const char *s;
};
S f()
{
return S{.number = 0, .s = "hi}; // correct order
return S{.s = "hi", .number = 0}; // invalid (out of) order
}
This should not be allowed in C++20 (according to a C++2a standard) and GCC
does not compile it - Clang trunk allows it.
GCC:
error: designator order for field 'S::number' does not match declaration order
in 'S'
12 | return S{.s = "hi", .number = 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
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40026] This Invalid Mangling causes crash in llvm-undname: "?ff@@$$J0YAXAU?$AS_@$0A@PEAU?$AS_@$0A@H@__clang@@@__clang@@@Z"
https://bugs.llvm.org/show_bug.cgi?id=40026 Zachary Turner changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #1 from Zachary Turner --- Fixed in latest 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 40031] New: __builtin_unpredictable is horridly broken--
https://bugs.llvm.org/show_bug.cgi?id=40031 Bug ID: 40031 Summary: __builtin_unpredictable is horridly broken-- Product: clang Version: 7.0 Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: C++ Assignee: unassignedclangb...@nondot.org Reporter: erich.ke...@intel.com CC: blitzrak...@gmail.com, dgre...@apple.com, erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk Mostly a note for the future, though others are welcome to take this. __builtin_unpredictable doesn't work for while/dowhile/for because the place it dealt with isn't called from them. The function to Emit a Bool Branch should be used by the other 3 as well. Additionally, __builtin_unpredictable is implemented IN an emit function, rather than in its CodeGenFunction emit call. Likely, it should be changed to also use the above emit function, then tag the branch after the fact (or bubble it downward to the branch create spot). -- 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 39983] [Hexagon] crash: failed to select v2i16 shift op
https://bugs.llvm.org/show_bug.cgi?id=39983 Krzysztof Parzyszek changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #1 from Krzysztof Parzyszek --- Fixed in r349202. -- 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 40032] New: instcombine forms illegal <2 x i64> multiply with trunc/zext
https://bugs.llvm.org/show_bug.cgi?id=40032
Bug ID: 40032
Summary: instcombine forms illegal <2 x i64> multiply with
trunc/zext
Product: libraries
Version: trunk
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: Scalar Optimizations
Assignee: unassignedb...@nondot.org
Reporter: efrie...@codeaurora.org
CC: husseyde...@gmail.com, llvm-bugs@lists.llvm.org,
spatel+l...@rotateright.com
C testcase:
#include
typedef int64x2_t U64x2;
typedef int32x2_t U32x2;
typedef int32x4_t U32x4;
U64x2 f(U64x2 top, U64x2 bot) {
U32x2 d2 = vmovn_u64(bot);
U32x2 d5 = vmovn_u64(top);
d5 = vmla_u32(d5, d2, d2);
return vshll_n_u32(d5, 0);
}
On ARM, we currently end up scalarizing the multiply, instead of using the
vector operation written in the source. (Even if we improve the expansion of
general <2 x i64 multiplies on ARM, it'll still be more expensive than the
original code. Other targets have similar issues.)
I think instcombine is being too aggressive here; I'm not sure the backend can
reasonably recover the original multiply in general.
IR testcase (for opt -instcombine):
define <2 x i64> @f(<2 x i64> %top, <2 x i64> %bot) {
entry:
%vmovn.i = trunc <2 x i64> %bot to <2 x i32>
%vmovn.i9 = trunc <2 x i64> %top to <2 x i32>
%mul.i = mul <2 x i32> %vmovn.i, %vmovn.i
%add.i = add <2 x i32> %mul.i, %vmovn.i9
%0 = zext <2 x i32> %add.i to <2 x i64>
ret <2 x i64> %0
}
Filing based on discussion in bug 39967.
--
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 40033] New: Unittest Sema/./SemaTests.exe/PreferredTypeTest.BinaryExpr failing when host and target have differing sizes for types
https://bugs.llvm.org/show_bug.cgi?id=40033
Bug ID: 40033
Summary: Unittest
Sema/./SemaTests.exe/PreferredTypeTest.BinaryExpr
failing when host and target have differing sizes for
types
Product: new-bugs
Version: trunk
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: douglas_y...@playstation.sony.com
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org
The unittest PreferredTypeTest.BinaryExpr was added upstream in r349053, and
then subsequently updated in r349086 to fix problems on LLP64 platforms.
We see a failure in the following test in our internal builds:
Code = R"cpp(
void test(int *ptr) {
ptr + ^10;
ptr += ^10;
ptr -= ^10;
})cpp";
// Expect the normalized ptrdiff_t type, which is typically long or long
long.
const char *PtrDiff = sizeof(void *) == sizeof(long) ? "long" : "long long";
EXPECT_THAT(collectPreferredTypes(Code), Each(PtrDiff));
The problem is that we use Visual Studio 2015 to build the clang and the
unittest, while test when run on Windows uses the newly built clang (which has
a target of the PS4). The problem is that the calculation of PtrDiff gives a
different answer depending on what your platform is in this case and causes the
test to fail.
On 64bit Windows, we have the following:
sizeof(void *) = 8
sizeof(long) = 4
While on the PS4 target, we have the following:
sizeof(void *) = 8
sizeof(long) = 8
This causes a problem because when Visual Studio compiles the unittest, since
it is targeting Windows, the comparison evaluates to false, and PtrDiff is set
to "long long". But when the test is actually run and it takes into
consideration the target platform type sizes, it returns only "long" which
causes the test to fail.
--
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 39996] [DebugInfo] Sign-extended variable is described by smaller stack slot, resulting in parts being filled with garbage data
https://bugs.llvm.org/show_bug.cgi?id=39996
Vedant Kumar changed:
What|Removed |Added
Status|NEW |RESOLVED
Fixed By Commit(s)||349214
Resolution|--- |FIXED
--- Comment #4 from Vedant Kumar ---
With r349214, I see:
(lldb) r
Process 36084 launched: './foo.out' (i386)
foo.out was compiled with optimization - stepping may behave oddly; variables
may not be available.
Process 36084 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
frame #0: 0x1f60 foo.out`foo(a=-123, b=3435973836) at foo.c:12 [opt]
9__attribute__((noinline)) void foo(int32_t a, uint32_t b) {
10 int64_t al = a;
11 int64_t rl = 6;
-> 12 bar(al);
13 bar(b);
14 }
15
Target 0: (foo.out) stopped.
(lldb) p al
(int64_t) $0 = -123
--
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 35400] Too much narrowing when converting dbg.declare to dbg.value
https://bugs.llvm.org/show_bug.cgi?id=35400 Vedant Kumar changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from Vedant Kumar --- Fixed in r349214 / PR39996. *** This bug has been marked as a duplicate of bug 39996 *** -- 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 40034] New: Minimize the number of options in VPlanNativePath
https://bugs.llvm.org/show_bug.cgi?id=40034 Bug ID: 40034 Summary: Minimize the number of options in VPlanNativePath Product: libraries Version: trunk Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: Loop Optimizer Assignee: unassignedb...@nondot.org Reporter: satish.guggi...@intel.com CC: llvm-bugs@lists.llvm.org The outer loop vectorization support in LoopVectorize makes use of new command line switches to control features currently under development. This issue is being opened to eliminate such switches once the feature matures. An example is the -enable-vplan-predication switch added in https://reviews.llvm.org/D53349. -- 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 40035] New: --size-sort causes symbols to not print
https://bugs.llvm.org/show_bug.cgi?id=40035
Bug ID: 40035
Summary: --size-sort causes symbols to not print
Product: tools
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: llvm-nm
Assignee: unassignedb...@nondot.org
Reporter: ruppre...@google.com
CC: llvm-bugs@lists.llvm.org
Using "--size-sort" seems to prevent symbols from printing in llvm-nm. Adding
"-S" fixes it but it should not be necessary.
$ echo 'int foo; int bar() { return 5; }' | clang -xc -c - -o /tmp/foo.o
$ nm --size-sort /tmp/foo.o
0004 C foo
000b T bar
$ llvm-nm --size-sort /tmp/foo.o
$ llvm-nm -S --size-sort /tmp/foo.o
0004 0004 C foo
000b T bar
--
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 38804] clang crashes with "-mllvm -enable-newgvn" at -O2: Assertion `F->user_begin() == F->user_end() && "PredicateInfo consumer did not remove all SSA copies."' failed.
https://bugs.llvm.org/show_bug.cgi?id=38804 Florian Hahn changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED Fixed By Commit(s)||349217 --- Comment #2 from Florian Hahn --- Fixed by https://reviews.llvm.org/rL349217 -- 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 40036] New: Clang crashes compiling valgrind Thumb2/arm
https://bugs.llvm.org/show_bug.cgi?id=40036 Bug ID: 40036 Summary: Clang crashes compiling valgrind Thumb2/arm Product: clang Version: 7.0 Hardware: Other OS: All Status: NEW Severity: enhancement Priority: P Component: LLVM Codegen Assignee: unassignedclangb...@nondot.org Reporter: raj.k...@gmail.com CC: llvm-bugs@lists.llvm.org, neeil...@live.com, richard-l...@metafoo.co.uk Created attachment 21228 --> https://bugs.llvm.org/attachment.cgi?id=21228&action=edit shell script Attached testcase and script to run the compiler -- 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 11859 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: Abrt in llvm::llvm_unreachable_internal
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-15 Type: Bug New issue 11859 by ClusterFuzz-External: llvm/llvm-dwarfdump-fuzzer: Abrt in llvm::llvm_unreachable_internal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11859 Detailed report: https://oss-fuzz.com/testcase?key=5646742129737728 Project: llvm Fuzzer: libFuzzer_llvm_llvm-dwarfdump-fuzzer Fuzz target binary: llvm-dwarfdump-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Abrt Crash Address: 0x0001 Crash State: llvm::llvm_unreachable_internal llvm::object::WasmSectionOrderChecker::getSectionOrder llvm::object::WasmObjectFile::WasmObjectFile Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201812140233:201812150234 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5646742129737728 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md 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. -- 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
