[llvm-bugs] [Bug 48323] Attempting to redefine a variable fails silently
https://bugs.llvm.org/show_bug.cgi?id=48323 Raphael Isemann changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED CC||teempe...@gmail.com --- Comment #1 from Raphael Isemann --- Fixed in https://reviews.llvm.org/D89310 FWIW, the reason why I went with (i) is that it's technically not something one can do in C/C++ (i.e., redefining a variable in the same scope). You can always achieve (ii) by just assigning a new value to the existing $x. -- 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 48334] New: wrong code with "-mem2reg -instcombine -simplifycfg -inline"
https://bugs.llvm.org/show_bug.cgi?id=48334
Bug ID: 48334
Summary: wrong code with "-mem2reg -instcombine -simplifycfg
-inline"
Product: new-bugs
Version: trunk
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: suochen...@163.com
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org
Created attachment 24221
--> https://bugs.llvm.org/attachment.cgi?id=24221&action=edit
bc file
***
OS and Platform:
CentOS Linux release 7.8.2003 (Core), x86_64 GNU/Linux
***
Program:
$ cat a.c
int printf(const char *, ...);
int a=0;
int(b)(c) { return 7 >> c; }
void d() { a = b(133); }
int main() {
d();
printf("%d\n", a);
}
***
clang version:
$ clang --version
clang version 12.0.0 (/home/suocy/src/llvm-dev/llvm-project/llvm/tools/clang
f15b7869e5afbd6c24ef440b0b62593e80fbd24f)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /home/suocy/bin/llvm-dev/bin
***
Command Lines:
$ clang -c -emit-llvm -O3 -mllvm -disable-llvm-optzns a.c -o a.bc
$ opt a.bc -o a.opt1.bc
$ clang a.opt1.bc -o a1.o
$ opt -mem2reg -instcombine -simplifycfg -inline a.bc -o a.opt2.bc
$ clang a.opt2.bc -o a2.o
$ ./a1.o
0
$ ./a2.o
4195600
--
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] Issue 28096 in oss-fuzz: llvm:clang-objc-fuzzer: ASSERT: NextLocalOffset + TokLength + 1 > NextLocalOffset && NextLocalOffset + TokLength
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevl...@apple.com, igm...@gmail.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2020-11-30 Type: Bug New issue 28096 by ClusterFuzz-External: llvm:clang-objc-fuzzer: ASSERT: NextLocalOffset + TokLength + 1 > NextLocalOffset && NextLocalOffset + TokLength https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=28096 Detailed Report: https://oss-fuzz.com/testcase?key=5165433854099456 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-objc-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: NextLocalOffset + TokLength + 1 > NextLocalOffset && NextLocalOffset + TokLength clang::SourceManager::createExpansionLocImpl clang::SourceManager::createMacroArgExpansionLoc Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202005130243:202005140645 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5165433854099456 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 44140] XMM constant wrongly hoisted past uses of corresponding YMM register
https://bugs.llvm.org/show_bug.cgi?id=44140 Simon Pilgrim changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #6 from Simon Pilgrim --- (In reply to Craig Topper from comment #5) > Yeah I think this can be resolved Cheers, resolving -- 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 13503] x86 AVX instruction was generated but stack object pointer is not 16/32 byte aligned.
https://bugs.llvm.org/show_bug.cgi?id=13503 Simon Pilgrim changed: What|Removed |Added Resolution|--- |WORKSFORME CC||llvm-...@redking.me.uk Status|NEW |RESOLVED --- Comment #5 from Simon Pilgrim --- Resolving ancient AVX alignment bug - IR works fine in trunk (and at least as far back as 4.0.0 according to godbolt). -- 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 48322] [AVX512F] Compilation failure of _mm512_shuffle_ps
https://bugs.llvm.org/show_bug.cgi?id=48322 Simon Pilgrim changed: What|Removed |Added Resolution|--- |FIXED Fixed By Commit(s)||83d79ca5bf13 Status|CONFIRMED |RESOLVED -- 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 48335] New: [X86
https://bugs.llvm.org/show_bug.cgi?id=48335 Bug ID: 48335 Summary: [X86 Product: libraries Version: trunk Hardware: PC OS: Linux 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, pengfei.w...@intel.com, spatel+l...@rotateright.com -- 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 48335] [X86
https://bugs.llvm.org/show_bug.cgi?id=48335 Simon Pilgrim changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #1 from Simon Pilgrim --- invalid - premature 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 48336] New: [X86] What AVX512 cpus should prefer 512-bit vectors?
https://bugs.llvm.org/show_bug.cgi?id=48336 Bug ID: 48336 Summary: [X86] What AVX512 cpus should prefer 512-bit vectors? Product: libraries Version: trunk Hardware: PC OS: Linux 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, pengfei.w...@intel.com, pe...@cordes.ca, spatel+l...@rotateright.com All avx512 capable Skylake CPUs and later currently prefer 256-bit vs 512-bit vector generation - only the Knights Landing family always prefers 512-bit (very different arch, no VLX support etc.). AFAICT many of the frequency throttling issues with 512-bit ops were already addressed by/after Icelake - so do we need to alter the tuning for later cpus to let them vectorize to the full 512-bit alu width? -- 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 48337] New: [X86] X86TargetTransformInfo - getCmpSelInstrCost doesn't discriminate between comparison codes
https://bugs.llvm.org/show_bug.cgi?id=48337 Bug ID: 48337 Summary: [X86] X86TargetTransformInfo - getCmpSelInstrCost doesn't discriminate between comparison codes Product: libraries Version: trunk Hardware: PC OS: Linux 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, pengfei.w...@intel.com, spatel+l...@rotateright.com Depends on: 40376 [Bug #40376] + D90070 added support for getCmpSelInstrCost to specify a comparison code, the SSE/AVX/XOP/AVX512 targets now need to be updated to better account for the various condcodes. Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=40376 [Bug 40376] TargetTransformInfo::getCmpSelInstrCost should discriminate between comparison codes -- 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 40376] TargetTransformInfo::getCmpSelInstrCost should discriminate between comparison codes
https://bugs.llvm.org/show_bug.cgi?id=40376 Simon Pilgrim changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED Fixed By Commit(s)||b3b993a7ad817c3c5801341fa78 ||f34332900eb83 --- Comment #2 from Simon Pilgrim --- (In reply to Simon Pilgrim from comment #1) > Candidate Patch: https://reviews.llvm.org/D90070 This landed at b3b993a7ad817c3c5801341fa78f34332900eb83 and I've created [Bug #48337] to handle X86 specifics - thanks @fhahn! -- 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 48337] [X86] X86TargetTransformInfo - getCmpSelInstrCost doesn't discriminate between comparison codes
https://bugs.llvm.org/show_bug.cgi?id=48337 Bug 48337 depends on bug 40376, which changed state. Bug 40376 Summary: TargetTransformInfo::getCmpSelInstrCost should discriminate between comparison codes https://bugs.llvm.org/show_bug.cgi?id=40376 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] Issue 19622 in oss-fuzz: llvm:clang-fuzzer: Segv on unknown address in clang::Sema::getCurBlock
Updates: Labels: -Reproducible Unreproducible Comment #2 on issue 19622 by ClusterFuzz-External: llvm:clang-fuzzer: Segv on unknown address in clang::Sema::getCurBlock https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19622#c2 ClusterFuzz testcase 5718959311814656 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 19623 in oss-fuzz: llvm:clang-fuzzer: Segv on unknown address in clang::Sema::ActOnStartOfFunctionDef
Updates: Labels: -Reproducible Unreproducible Comment #2 on issue 19623 by ClusterFuzz-External: llvm:clang-fuzzer: Segv on unknown address in clang::Sema::ActOnStartOfFunctionDef https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19623#c2 ClusterFuzz testcase 5729474851373056 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 23468 in oss-fuzz: llvm:clang-fuzzer: Segv on unknown address in clang::Sema::DeclareImplicitCopyAssignment
Updates: Labels: -Reproducible Unreproducible Comment #2 on issue 23468 by ClusterFuzz-External: llvm:clang-fuzzer: Segv on unknown address in clang::Sema::DeclareImplicitCopyAssignment https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=23468#c2 ClusterFuzz testcase 5957130015473664 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 19683 in oss-fuzz: llvm:clang-fuzzer: Segv on unknown address in clang::LookupResult::sanity
Updates: Labels: -Reproducible Unreproducible Comment #2 on issue 19683 by ClusterFuzz-External: llvm:clang-fuzzer: Segv on unknown address in clang::LookupResult::sanity https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19683#c2 ClusterFuzz testcase 4872329519955968 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 19652 in oss-fuzz: llvm:clang-fuzzer: Segv on unknown address in llvm::llvm_unreachable_internal
Updates: Labels: -Reproducible Unreproducible Comment #2 on issue 19652 by ClusterFuzz-External: llvm:clang-fuzzer: Segv on unknown address in llvm::llvm_unreachable_internal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19652#c2 ClusterFuzz testcase 5165184549388288 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 21077 in oss-fuzz: llvm:clang-objc-fuzzer: Segv on unknown address in clang::Parser::TryAnnotateCXXScopeToken
Updates: Labels: -Reproducible Unreproducible Comment #2 on issue 21077 by ClusterFuzz-External: llvm:clang-objc-fuzzer: Segv on unknown address in clang::Parser::TryAnnotateCXXScopeToken https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=21077#c2 ClusterFuzz testcase 5165252426858496 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 19152 in oss-fuzz: llvm:clang-fuzzer: Segv on unknown address in clang::StmtVisitorBase::Visit
Updates: Labels: -Reproducible Unreproducible Comment #2 on issue 19152 by ClusterFuzz-External: llvm:clang-fuzzer: Segv on unknown address in clang::StmtVisitorBase::Visit https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19152#c2 ClusterFuzz testcase 5629817202671616 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 19071 in oss-fuzz: llvm:clang-fuzzer: Segv on unknown address in clang::Decl::AccessDeclContextSanity
Updates: Labels: -Reproducible Unreproducible Comment #2 on issue 19071 by ClusterFuzz-External: llvm:clang-fuzzer: Segv on unknown address in clang::Decl::AccessDeclContextSanity https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19071#c2 ClusterFuzz testcase 5641990750601216 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 19117 in oss-fuzz: llvm:clang-fuzzer: Segv on unknown address in clang::Decl::AccessDeclContextSanity
Updates: Labels: -Reproducible Unreproducible Comment #2 on issue 19117 by ClusterFuzz-External: llvm:clang-fuzzer: Segv on unknown address in clang::Decl::AccessDeclContextSanity https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19117#c2 ClusterFuzz testcase 5644750535524352 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 27537 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::DeclContext::getLookupParent
Updates: Labels: -Reproducible Unreproducible Comment #1 on issue 27537 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::DeclContext::getLookupParent https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=27537#c1 ClusterFuzz testcase 5644940994150400 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 21119 in oss-fuzz: llvm:clang-fuzzer: Segv on unknown address in clang::FunctionProtoType::FunctionProtoType
Updates: Labels: -Reproducible Unreproducible Comment #2 on issue 21119 by ClusterFuzz-External: llvm:clang-fuzzer: Segv on unknown address in clang::FunctionProtoType::FunctionProtoType https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=21119#c2 ClusterFuzz testcase 5650857535471616 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 21207 in oss-fuzz: llvm:clang-fuzzer: Segv on unknown address in llvm::APInt::trunc
Updates: Labels: -Reproducible Unreproducible Comment #2 on issue 21207 by ClusterFuzz-External: llvm:clang-fuzzer: Segv on unknown address in llvm::APInt::trunc https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=21207#c2 ClusterFuzz testcase 5653608042594304 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 19132 in oss-fuzz: llvm:clang-fuzzer: Segv on unknown address in clang::CXXRecordDecl::data
Updates: Labels: -Reproducible Unreproducible Comment #2 on issue 19132 by ClusterFuzz-External: llvm:clang-fuzzer: Segv on unknown address in clang::CXXRecordDecl::data https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19132#c2 ClusterFuzz testcase 5662230230335488 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 19880 in oss-fuzz: llvm:clang-fuzzer: Segv on unknown address in EvaluateObjectArgument
Updates: Labels: -Reproducible Unreproducible Comment #2 on issue 19880 by ClusterFuzz-External: llvm:clang-fuzzer: Segv on unknown address in EvaluateObjectArgument https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19880#c2 ClusterFuzz testcase 5664409284509696 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 19228 in oss-fuzz: llvm:clang-fuzzer: Segv on unknown address in clang::CXXRecordDecl::data
Updates: Labels: -Reproducible Unreproducible Comment #2 on issue 19228 by ClusterFuzz-External: llvm:clang-fuzzer: Segv on unknown address in clang::CXXRecordDecl::data https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19228#c2 ClusterFuzz testcase 5673340807413760 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 19205 in oss-fuzz: llvm:clang-fuzzer: Segv on unknown address in clang::SourceManager::getFileIDLoaded
Updates: Labels: -Reproducible Unreproducible Comment #2 on issue 19205 by ClusterFuzz-External: llvm:clang-fuzzer: Segv on unknown address in clang::SourceManager::getFileIDLoaded https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19205#c2 ClusterFuzz testcase 5697366384705536 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 19181 in oss-fuzz: llvm:clang-fuzzer: Segv on unknown address in clang::Sema::LookupQualifiedName
Updates: Labels: -Reproducible Unreproducible Comment #2 on issue 19181 by ClusterFuzz-External: llvm:clang-fuzzer: Segv on unknown address in clang::Sema::LookupQualifiedName https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19181#c2 ClusterFuzz testcase 5702033537761280 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 19136 in oss-fuzz: llvm:clang-fuzzer: Segv on unknown address in clang::Sema::SetCtorInitializers
Updates: Labels: -Reproducible Unreproducible Comment #2 on issue 19136 by ClusterFuzz-External: llvm:clang-fuzzer: Segv on unknown address in clang::Sema::SetCtorInitializers https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19136#c2 ClusterFuzz testcase 5704527068266496 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 19171 in oss-fuzz: llvm:clang-fuzzer: Segv on unknown address in llvm::detail::IEEEFloat::roundSignificandWithExponent
Updates: Labels: -Reproducible Unreproducible Comment #2 on issue 19171 by ClusterFuzz-External: llvm:clang-fuzzer: Segv on unknown address in llvm::detail::IEEEFloat::roundSignificandWithExponent https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19171#c2 ClusterFuzz testcase 5706795951849472 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 23785 in oss-fuzz: llvm:clang-objc-fuzzer: Segv on unknown address in clang::Parser::parseObjCTypeArgsAndProtocolQualifiers
Updates: Labels: -Reproducible Unreproducible Comment #2 on issue 23785 by ClusterFuzz-External: llvm:clang-objc-fuzzer: Segv on unknown address in clang::Parser::parseObjCTypeArgsAndProtocolQualifiers https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=23785#c2 ClusterFuzz testcase 5708079416213504 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 20893 in oss-fuzz: llvm:clang-fuzzer: Segv on unknown address in FindDeclaringClass
Updates: Labels: -Reproducible Unreproducible Comment #2 on issue 20893 by ClusterFuzz-External: llvm:clang-fuzzer: Segv on unknown address in FindDeclaringClass https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=20893#c2 ClusterFuzz testcase 5744309964111872 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 19620 in oss-fuzz: llvm:clang-objc-fuzzer: Segv on unknown address in clang::Sema::ActOnMethodDeclaration
Updates: Labels: -Reproducible Unreproducible Comment #2 on issue 19620 by ClusterFuzz-External: llvm:clang-objc-fuzzer: Segv on unknown address in clang::Sema::ActOnMethodDeclaration https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19620#c2 ClusterFuzz testcase 5759960881561600 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 25059 in oss-fuzz: llvm:clang-fuzzer: Segv on unknown address in clang::Sema::PushDeclContext
Updates: Labels: -Reproducible Unreproducible Comment #2 on issue 25059 by ClusterFuzz-External: llvm:clang-fuzzer: Segv on unknown address in clang::Sema::PushDeclContext https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=25059#c2 ClusterFuzz testcase 5760004104388608 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 20232 in oss-fuzz: llvm:clang-fuzzer: Segv on unknown address in clang::Sema::EnterDeclaratorContext
Updates: Labels: -Reproducible Unreproducible Comment #2 on issue 20232 by ClusterFuzz-External: llvm:clang-fuzzer: Segv on unknown address in clang::Sema::EnterDeclaratorContext https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=20232#c2 ClusterFuzz testcase 6244001741275136 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 28000 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::NumericLiteralParser::isValidUDSuffix
Updates: Labels: -Reproducible Unreproducible Comment #1 on issue 28000 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::NumericLiteralParser::isValidUDSuffix https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=28000#c1 ClusterFuzz testcase 6289242531299328 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 27823 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in GetFullTypeForDeclarator
Updates: Labels: -Reproducible Unreproducible Comment #1 on issue 27823 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in GetFullTypeForDeclarator https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=27823#c1 ClusterFuzz testcase 4807434813833216 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 23669 in oss-fuzz: llvm:clang-fuzzer: Segv on unknown address in clang::Expr::skipRValueSubobjectAdjustments
Updates: Labels: -Reproducible Unreproducible Comment #2 on issue 23669 by ClusterFuzz-External: llvm:clang-fuzzer: Segv on unknown address in clang::Expr::skipRValueSubobjectAdjustments https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=23669#c2 ClusterFuzz testcase 4893097812295680 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 27558 in oss-fuzz: llvm:clang-objc-fuzzer: Stack-overflow in llvm::FoldingSetNodeID::AddInteger
Updates: Labels: -Reproducible Unreproducible Comment #1 on issue 27558 by ClusterFuzz-External: llvm:clang-objc-fuzzer: Stack-overflow in llvm::FoldingSetNodeID::AddInteger https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=27558#c1 ClusterFuzz testcase 6285471747145728 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 27287 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::StmtVisitorBase::Visit
Updates: Labels: -Reproducible Unreproducible Comment #1 on issue 27287 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::StmtVisitorBase::Visit https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=27287#c1 ClusterFuzz testcase 5089701398315008 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 27504 in oss-fuzz: llvm:clang-objc-fuzzer: Stack-overflow in clang::Sema::DiagnoseAvailabilityOfDecl
Updates: Labels: -Reproducible Unreproducible Comment #1 on issue 27504 by ClusterFuzz-External: llvm:clang-objc-fuzzer: Stack-overflow in clang::Sema::DiagnoseAvailabilityOfDecl https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=27504#c1 ClusterFuzz testcase 5679402872209408 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 48296] opt crash with "-mem2reg -simplifycfg -instcombine -jump-threading -correlated-propagation -lcssa -loop-rotate -loop-vectorize": Assertion `!verifyFunction(*L->getHeader()->get
https://bugs.llvm.org/show_bug.cgi?id=48296 Sanjay Patel changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED Fixed By Commit(s)||9eb2c011 CC||spatel+l...@rotateright.com --- Comment #1 from Sanjay Patel --- Removed the assert: https://reviews.llvm.org/rG9eb2c0113dfe I tried for a possibly better fix with: https://reviews.llvm.org/D92247 ...but that caused other failures as noted in the reverting commit. -- 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 48339] New: Bogus error/note about dependent base classes on template instantiation failure
https://bugs.llvm.org/show_bug.cgi?id=48339
Bug ID: 48339
Summary: Bogus error/note about dependent base classes on
template instantiation failure
Product: clang
Version: 11.0
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: Frontend
Assignee: unassignedclangb...@nondot.org
Reporter: w...@cornell.edu
CC: llvm-bugs@lists.llvm.org, neeil...@live.com,
richard-l...@metafoo.co.uk
The below code is invalid (the template parameter of g cannot be deduced), but
before giving the correct error clang reports
bug.cpp:11:5: error: use of undeclared identifier 'g'
g(typename T::type{});
^
this->
bug.cpp:16:7: note: in instantiation of function template specialization
'S::f' requested here
S{}.f();
^
bug.cpp:7:15: note: must qualify identifier to find this declaration in
dependent base class
static void g(typename T::type) {}
which make no sense as there are no base classes here, dependent or otherwise.
These messages are not present if g is not marked static.
struct X {
struct type {};
};
struct S {
template
static void g(typename T::type) {}
template
void f() {
g(typename T::type{});
}
};
void f() {
S{}.f();
}
--
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 48340] New: loop-vectorize assertion failure "argument of incompatible type"
https://bugs.llvm.org/show_bug.cgi?id=48340
Bug ID: 48340
Summary: loop-vectorize assertion failure "argument of
incompatible type"
Product: new-bugs
Version: trunk
Hardware: PC
URL: https://github.com/rust-lang/rust/issues/79564
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: tomasz.mia...@gmail.com
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org
$ cat a.ll
; ModuleID = 'a.ll'
source_filename = "a.6dqf8b0y-cgu.0"
target datalayout =
"e-m:e-p270:32:32-p271:32:32-p272:64:64-i64:64-f80:128-n8:16:32:64-S128"
target triple = "x86_64-unknown-linux-gnu"
%0 = type { i32 }
%1 = type { i64 }
define void @a() unnamed_addr #0 {
br label %1
1:; preds = %1, %0
%2 = phi i64* [ undef, %0 ], [ %3, %1 ]
%3 = getelementptr inbounds i64, i64* %2, i64 2
%4 = bitcast i64* %2 to %0**
%5 = load %0*, %0** %4, align 8
%6 = icmp eq i64* %3, undef
br i1 %6, label %7, label %1
7:; preds = %1
ret void
}
define void @b() unnamed_addr #0 {
br label %1
1:; preds = %1, %0
%2 = phi i64* [ undef, %0 ], [ %3, %1 ]
%3 = getelementptr inbounds i64, i64* %2, i64 2
%4 = bitcast i64* %2 to %1**
%5 = load %1*, %1** %4, align 8
%6 = icmp eq i64* %3, undef
br i1 %6, label %7, label %1
7:; preds = %1
ret void
}
attributes #0 = { "target-cpu"="skylake" }
!llvm.module.flags = !{!0}
!0 = !{i32 2, !"RtLibUseGOT", i32 1}
$ opt a.ll -loop-vectorize
opt: llvm-project/llvm/include/llvm/Support/Casting.h:269: typename
llvm::cast_retty::ret_type llvm::cast(Y*) [with X = llvm::Function; Y =
llvm::Value; typename llvm::cast_retty::ret_type = llvm::Function*]:
Assertion `isa(Val) && "cast() argument of incompatible type!"' failed.
PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash
backtrace.
Stack dump:
0. Program arguments: llvm-project/build/bin/opt a.ll -loop-vectorize
1. Running pass 'Function Pass Manager' on module 'a.ll'.
2. Running pass 'Loop Vectorization' on function '@b'
#8 0x02219130 matchIntrinsicType(llvm::Type*,
llvm::ArrayRef&,
llvm::SmallVectorImpl&,
llvm::SmallVectorImpl > >&, bool)
(llvm-project/build/bin/opt+0x2219130)
#9 0x02221bd4 llvm::IRBuilderBase::CreateMaskedIntrinsic(unsigned int,
llvm::ArrayRef, llvm::ArrayRef, llvm::Twine const&)
(llvm-project/build/bin/opt+0x2221bd4)
#10 0x02221f42 llvm::IRBuilderBase::CreateMaskedGather(llvm::Value*,
llvm::Align, llvm::Value*, llvm::Value*, llvm::Twine const&)
(llvm-project/build/bin/opt+0x2221f42)
#11 0x02cbefeb
llvm::InnerLoopVectorizer::vectorizeMemoryInstruction(llvm::Instruction*,
llvm::VPTransformState&, llvm::VPValue*, llvm::VPValue*, llvm::VPValue*,
llvm::VPValue*) (llvm-project/build/bin/opt+0x2cbefeb)
#12 0x02cbf391
llvm::VPWidenMemoryInstructionRecipe::execute(llvm::VPTransformState&)
(llvm-project/build/bin/opt+0x2cbf391)
#13 0x02d35fc7 llvm::VPBasicBlock::execute(llvm::VPTransformState*)
(llvm-project/build/bin/opt+0x2d35fc7)
#14 0x02d39ac4 llvm::VPlan::execute(llvm::VPTransformState*)
(llvm-project/build/bin/opt+0x2d39ac4)
#15 0x02cd3258
llvm::LoopVectorizationPlanner::executePlan(llvm::InnerLoopVectorizer&,
llvm::DominatorTree*) (llvm-project/build/bin/opt+0x2cd3258)
#16 0x02ce2d9a llvm::LoopVectorizePass::processLoop(llvm::Loop*)
(llvm-project/build/bin/opt+0x2ce2d9a)
#17 0x02ce5031 llvm::LoopVectorizePass::runImpl(llvm::Function&,
llvm::ScalarEvolution&, llvm::LoopInfo&, llvm::TargetTransformInfo&,
llvm::DominatorTree&, llvm::BlockFrequencyInfo&, llvm::TargetLibraryInfo*,
llvm::DemandedBits&, llvm::AAResults&, llvm::AssumptionCache&,
std::function&,
llvm::OptimizationRemarkEmitter&, llvm::ProfileSummaryInfo*)
(llvm-project/build/bin/opt+0x2ce5031)
#18 0x02ce5567 (anonymous
namespace)::LoopVectorize::runOnFunction(llvm::Function&)
(llvm-project/build/bin/opt+0x2ce5567)
#19 0x0226f628 llvm::FPPassManager::runOnFunction(llvm::Function&)
(llvm-project/build/bin/opt+0x226f628)
#20 0x0226fca1 llvm::FPPassManager::runOnModule(llvm::Module&)
(llvm-project/build/bin/opt+0x226fca1)
#21 0x0226e573 llvm::legacy::PassManagerImpl::run(llvm::Module&)
(llvm-project/build/bin/opt+0x226e573)
#22 0x0066e85d main (llvm-project/build/bin/opt+0x66e85d)
#23 0x7fc35fe08ba2 __libc_start_main (/lib64/libc.so.6+0x27ba2)
#24 0x0072eafe _start (llvm-project/build/bin/opt+0x72eafe)
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.or
[llvm-bugs] [Bug 48341] New: C99 code completion for field names in designated initializers used with compound literals
https://bugs.llvm.org/show_bug.cgi?id=48341
Bug ID: 48341
Summary: C99 code completion for field names in designated
initializers used with compound literals
Product: clang-tools-extra
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: clangd
Assignee: unassignedclangb...@nondot.org
Reporter: michaelagan...@gmail.com
CC: llvm-bugs@lists.llvm.org
Code completion for field names in designated initializers is a recent addition
to clang. The code completion only works for regular assignments and doesn't
for compound literals.
typedef struct Foo {
int x;
} Foo;
int main (void)
{
Foo bar = { .x = 1 }; // completion works for regular assignments
bar = (Foo){ . // no code completion with compound literals
}
--
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 48342] New: LLDB crashes when inspecting an object created using ni::type_hierarchy
https://bugs.llvm.org/show_bug.cgi?id=48342
Bug ID: 48342
Summary: LLDB crashes when inspecting an object created using
ni::type_hierarchy
Product: lldb
Version: unspecified
Hardware: Macintosh
OS: MacOS X
Status: NEW
Severity: normal
Priority: P
Component: All Bugs
Assignee: lldb-...@lists.llvm.org
Reporter: hbu...@fender.com
CC: jdevliegh...@apple.com, llvm-bugs@lists.llvm.org
When using the Native Instruments open source library matchine, the
ni::type_hierarchy objects crash the LLDB RPC Server when inspected using Xcode
12.
Here is the issue filed against the matchine library:
https://github.com/NativeInstruments/matchine/issues/1
Here is an example that crashes LLDB. It requires the matchine library which
has a dependency on boost.
```
#include
#include
struct EventBase {
EventBase() = default;
virtual ~EventBase() = default;
};
using Event = ni::type_hierarchy::from_base;
NI_SUB_TYPE(struct TestEvent, Event)
{
int value = 0;
TestEvent(int value_)
: value( value_ )
{
}
};
int main(int argc, const char * argv[]) {
TestEvent testEvent(100);
// insert breakpoint here to inspect testEvent
// inpecting testEvent will crash LLDB
TestEvent testEvent2(200);
return 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 48343] New: [InstCombine] Miscompile of sext(ashr(shl(trunc())))
https://bugs.llvm.org/show_bug.cgi?id=48343
Bug ID: 48343
Summary: [InstCombine] Miscompile of sext(ashr(shl(trunc(
Product: libraries
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: Scalar Optimizations
Assignee: unassignedb...@nondot.org
Reporter: meh...@google.com
CC: llvm-bugs@lists.llvm.org
Example failing input:
define i10 @test(i10 %i) {
%a = trunc i10 %i to i3
%b = shl i3 %a, 2
%c = ashr i3 %b, 2
%d = sext i3 %c to i10
ret i10 %d
}
Bad code after optimizations:
$ opt -S --instcombine /tmp/fail.ll
; ModuleID = '/tmp/fail.ll'
source_filename = "/tmp/fail.ll"
define i10 @test(i10 %i) {
%d1 = shl i10 %i, 1
%d = ashr exact i10 %d1, 1
ret i10 %d
}
This should be shifting left by 9 then shifting right by 9, but (I think) the
optimization tries to create a 9 of type i3 which is the source of the bug:
https://github.com/llvm/llvm-project/blob/8cdf4920c47ddd3d60bdc3298f525512d483ce65/llvm/lib/Transforms/InstCombine/InstCombineCasts.cpp#L1526
--
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] Issue 28138 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::Decl::castFromDeclContext
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevl...@apple.com, igm...@gmail.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2020-12-01 Type: Bug New issue 28138 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::Decl::castFromDeclContext https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=28138 Detailed Report: https://oss-fuzz.com/testcase?key=5719153721475072 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffd06297ff8 Crash State: clang::Decl::castFromDeclContext clang::DeclContext::isDependentContext clang::Sema::LookupQualifiedName Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202011290606:202011300612 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5719153721475072 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 48344] New: Coroutine promise types don't support destroying operator delete
https://bugs.llvm.org/show_bug.cgi?id=48344
Bug ID: 48344
Summary: Coroutine promise types don't support destroying
operator delete
Product: clang
Version: trunk
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P
Component: C++2a
Assignee: unassignedclangb...@nondot.org
Reporter: cyg...@michiru.ru
CC: blitzrak...@gmail.com, erik.pilking...@gmail.com,
llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk
$ cat pdd.cpp
#if __has_include()
#include
namespace stdcoro = std;
#else
#include
namespace stdcoro = std::experimental;
#endif
#include
#include
struct coroutine
{
struct promise_type
{
coroutine get_return_object() noexcept
{
return {*this};
}
stdcoro::suspend_always initial_suspend() const noexcept
{
return {};
}
stdcoro::suspend_always final_suspend() const noexcept
{
return {};
}
void return_void() const noexcept {}
void unhandled_exception() noexcept {}
void* operator new(std::size_t n)
{
return std::malloc(n);
}
void operator delete(
promise_type* p,std::destroying_delete_t,std::size_t)
{
std::free(p);
}
};
stdcoro::coroutine_handle h_;
coroutine(promise_type& p)
: h_{decltype(h_)::from_promise(p)}
{}
~coroutine()
{
h_.destroy();
}
};
coroutine f()
{
co_return;
}
$ clang++ -std=c++20 -fsyntax-only pdd.cpp
pdd.cpp:59:11: error: too few arguments to function call, expected 3, have 2
coroutine f()
^
pdd.cpp:40:14: note: 'operator delete' declared here
void operator delete(
^
1 error generated.
Looking at the end of CoroutineStmtBuilder::makeNewAndDeleteExpr(), it seems
like support for destroying operator delete on promise types is not
implemented.
Neither gcc 10.2 nor MSVC 16.8.2 accept this code with similar error messages,
but it looks like it's impossible to implement a coroutine with statefull
Allocator support for promise that also has access to its allocator in its
implementation without support for this combination. I also can't find anything
that prohibits this in the C++ standard.
--
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 48345] New: linker segfaults when using -shared on AMDGPU kernel
https://bugs.llvm.org/show_bug.cgi?id=48345
Bug ID: 48345
Summary: linker segfaults when using -shared on AMDGPU kernel
Product: lld
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: release blocker
Priority: P
Component: ELF
Assignee: unassignedb...@nondot.org
Reporter: fwin...@jlab.org
CC: llvm-bugs@lists.llvm.org, smithp...@googlemail.com
When linking a module containing a really trivial function with ld.lld I get:
$ ld.lld -shared module.o -o module.so
ld.lld: /home/users/coe0193/llvm-project/lld/ELF/Arch/AMDGPU.cpp:48: virtual
uint32_t {anonymous}::AMDGPU::calcEFlags() const: Assertion
`!objectFiles.empty()' failed.
PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash
backtrace.
Stack dump:
0. Program arguments:
/home/users/coe0193/install/llvm-trunk-x86-amdgpu-debug/bin/ld.lld -shared
module_empty.o -o module_empty.so
#0 0x12e30eed llvm::sys::PrintStackTrace(llvm::raw_ostream&, int)
/home/users/coe0193/llvm-project/llvm/lib/Support/Unix/Signals.inc:563:22
#1 0x12e30fa4 PrintStackTraceSignalHandler(void*)
/home/users/coe0193/llvm-project/llvm/lib/Support/Unix/Signals.inc:630:1
#2 0x12e2efa6 llvm::sys::RunSignalHandlers()
/home/users/coe0193/llvm-project/llvm/lib/Support/Signals.cpp:71:20
#3 0x12e30934 SignalHandler(int)
/home/users/coe0193/llvm-project/llvm/lib/Support/Unix/Signals.inc:405:1
#4 0x1511ddd0 __restore_rt (/lib64/libpthread.so.0+0x12dd0)
#5 0x11d6170f raise (/lib64/libc.so.6+0x3770f)
#6 0x11d4bb25 abort (/lib64/libc.so.6+0x21b25)
#7 0x11d4b9f9 _nl_load_domain.cold.0 (/lib64/libc.so.6+0x219f9)
#8 0x11d59cc6 (/lib64/libc.so.6+0x2fcc6)
#9 0x1476b887 (anonymous namespace)::AMDGPU::calcEFlags() const
/home/users/coe0193/llvm-project/lld/ELF/Arch/AMDGPU.cpp:49:41
#10 0x147cc335 void
lld::elf::LinkerDriver::link >(llvm::opt::InputArgList&)
/home/users/coe0193/llvm-project/lld/ELF/Driver.cpp:2209:3
#11 0x147b1ed2 lld::elf::LinkerDriver::main(llvm::ArrayRef) /home/users/coe0193/llvm-project/lld/ELF/Driver.cpp:558:7
#12 0x147ae1ad lld::elf::link(llvm::ArrayRef, bool,
llvm::raw_ostream&, llvm::raw_ostream&)
/home/users/coe0193/llvm-project/lld/ELF/Driver.cpp:125:3
#13 0x0040810a lldMain(int, char const**, llvm::raw_ostream&,
llvm::raw_ostream&, bool)
/home/users/coe0193/llvm-project/lld/tools/lld/lld.cpp:153:12
#14 0x00408581 main
/home/users/coe0193/llvm-project/lld/tools/lld/lld.cpp:211:19
#15 0x11d4d6a3 __libc_start_main (/lib64/libc.so.6+0x236a3)
#16 0x004073ee _start
(/home/users/coe0193/install/llvm-trunk-x86-amdgpu-debug/bin/ld.lld+0x4073ee)
Aborted (core dumped)
This bug is present in LLVM 11 release as well as in LLVM 12 current trunk (as
of Nov. 30th 2020).
On Linux I built llvm-project with
cmake ../llvm-project/llvm \
-DCMAKE_INSTALL_PREFIX="$HOME/install/llvm-trunk-x86-amdgpu-debug" \
-DLLVM_ENABLE_PROJECTS="clang;lld" \
-DCMAKE_BUILD_TYPE="Debug" \
-DBUILD_SHARED_LIBS=ON \
-DCMAKE_CXX_COMPILER=g++ \
-DCMAKE_C_COMPILER=gcc \
-DLLVM_TARGETS_TO_BUILD="X86;AMDGPU"
To provoke the bug I created a small module written in LLVM IR containing a
simple AMDGPU kernel function, like
module.ll:
define amdgpu_kernel void @test() {
entry:
ret void
}
Then I compile this module with
$ clang -target amdgcn-amd-amdhsa -mcpu=gfx908 module.ll -o module.o
And try to link a shared library for it:
$ ld.lld -shared module.o -o module.so
This crashes the linker with the above back trace.
Please help!
Frank
--
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 48346] New: linker segfaults when using -shared on AMDGPU kernel
https://bugs.llvm.org/show_bug.cgi?id=48346
Bug ID: 48346
Summary: linker segfaults when using -shared on AMDGPU kernel
Product: libraries
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: release blocker
Priority: P
Component: Backend: AMDGPU
Assignee: unassignedb...@nondot.org
Reporter: fwin...@jlab.org
CC: llvm-bugs@lists.llvm.org
When linking a module containing a really trivial function with ld.lld I get:
$ ld.lld -shared module.o -o module.so
ld.lld: /home/users/coe0193/llvm-project/lld/ELF/Arch/AMDGPU.cpp:48: virtual
uint32_t {anonymous}::AMDGPU::calcEFlags() const: Assertion
`!objectFiles.empty()' failed.
PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash
backtrace.
Stack dump:
0. Program arguments:
/home/users/coe0193/install/llvm-trunk-x86-amdgpu-debug/bin/ld.lld -shared
module_empty.o -o module_empty.so
#0 0x12e30eed llvm::sys::PrintStackTrace(llvm::raw_ostream&, int)
/home/users/coe0193/llvm-project/llvm/lib/Support/Unix/Signals.inc:563:22
#1 0x12e30fa4 PrintStackTraceSignalHandler(void*)
/home/users/coe0193/llvm-project/llvm/lib/Support/Unix/Signals.inc:630:1
#2 0x12e2efa6 llvm::sys::RunSignalHandlers()
/home/users/coe0193/llvm-project/llvm/lib/Support/Signals.cpp:71:20
#3 0x12e30934 SignalHandler(int)
/home/users/coe0193/llvm-project/llvm/lib/Support/Unix/Signals.inc:405:1
#4 0x1511ddd0 __restore_rt (/lib64/libpthread.so.0+0x12dd0)
#5 0x11d6170f raise (/lib64/libc.so.6+0x3770f)
#6 0x11d4bb25 abort (/lib64/libc.so.6+0x21b25)
#7 0x11d4b9f9 _nl_load_domain.cold.0 (/lib64/libc.so.6+0x219f9)
#8 0x11d59cc6 (/lib64/libc.so.6+0x2fcc6)
#9 0x1476b887 (anonymous namespace)::AMDGPU::calcEFlags() const
/home/users/coe0193/llvm-project/lld/ELF/Arch/AMDGPU.cpp:49:41
#10 0x147cc335 void
lld::elf::LinkerDriver::link >(llvm::opt::InputArgList&)
/home/users/coe0193/llvm-project/lld/ELF/Driver.cpp:2209:3
#11 0x147b1ed2 lld::elf::LinkerDriver::main(llvm::ArrayRef) /home/users/coe0193/llvm-project/lld/ELF/Driver.cpp:558:7
#12 0x147ae1ad lld::elf::link(llvm::ArrayRef, bool,
llvm::raw_ostream&, llvm::raw_ostream&)
/home/users/coe0193/llvm-project/lld/ELF/Driver.cpp:125:3
#13 0x0040810a lldMain(int, char const**, llvm::raw_ostream&,
llvm::raw_ostream&, bool)
/home/users/coe0193/llvm-project/lld/tools/lld/lld.cpp:153:12
#14 0x00408581 main
/home/users/coe0193/llvm-project/lld/tools/lld/lld.cpp:211:19
#15 0x11d4d6a3 __libc_start_main (/lib64/libc.so.6+0x236a3)
#16 0x004073ee _start
(/home/users/coe0193/install/llvm-trunk-x86-amdgpu-debug/bin/ld.lld+0x4073ee)
Aborted (core dumped)
This bug is present in LLVM 11 release as well as in LLVM 12 current trunk (as
of Nov. 30th 2020).
On Linux I built llvm-project with
cmake ../llvm-project/llvm \
-DCMAKE_INSTALL_PREFIX="$HOME/install/llvm-trunk-x86-amdgpu-debug" \
-DLLVM_ENABLE_PROJECTS="clang;lld" \
-DCMAKE_BUILD_TYPE="Debug" \
-DBUILD_SHARED_LIBS=ON \
-DCMAKE_CXX_COMPILER=g++ \
-DCMAKE_C_COMPILER=gcc \
-DLLVM_TARGETS_TO_BUILD="X86;AMDGPU"
To provoke the bug I created a small module written in LLVM IR containing a
simple AMDGPU kernel function, like
module.ll:
define amdgpu_kernel void @test() {
entry:
ret void
}
Then I compile this module with
$ clang -target amdgcn-amd-amdhsa -mcpu=gfx908 module.ll -o module.o
And try to link a shared library for it:
$ ld.lld -shared module.o -o module.so
This crashes the linker with the above back trace.
Please help!
Frank
--
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] Issue 20748 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::Preprocessor::PeekAhead
Updates: Status: WontFix Comment #2 on issue 20748 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::Preprocessor::PeekAhead https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=20748#c2 ClusterFuzz testcase 5070693391925248 is closed as invalid, so closing issue. -- 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] Issue 12894 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in clang::FunctionProtoType::getExtProtoInfo
Updates: Status: WontFix Comment #6 on issue 12894 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in clang::FunctionProtoType::getExtProtoInfo https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12894#c6 ClusterFuzz testcase 5181233204559872 is closed as invalid, so closing issue. -- 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] Issue 19004 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::Parser::ParseOptionalCXXScopeSpecifier
Updates: Status: WontFix Comment #2 on issue 19004 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::Parser::ParseOptionalCXXScopeSpecifier https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19004#c2 ClusterFuzz testcase 5204648021721088 is closed as invalid, so closing issue. -- 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] Issue 10764 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in clang::APValue::swap
Updates: Status: WontFix Comment #5 on issue 10764 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in clang::APValue::swap https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10764#c5 ClusterFuzz testcase 5635264848855040 is closed as invalid, so closing issue. -- 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] Issue 28147 in oss-fuzz: llvm:llvm-opt-fuzzer--x86_64-instcombine: ASSERT: SafeReplacementConstant && "Replacement constant not set"
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevl...@apple.com, igm...@gmail.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2020-12-01 Type: Bug New issue 28147 by ClusterFuzz-External: llvm:llvm-opt-fuzzer--x86_64-instcombine: ASSERT: SafeReplacementConstant && "Replacement constant not set" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=28147 Detailed Report: https://oss-fuzz.com/testcase?key=5553416688107520 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: llvm-opt-fuzzer--x86_64-instcombine Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: SafeReplacementConstant && "Replacement constant not set" llvm::InstCombiner::getFlippedStrictnessPredicateAndConstant llvm::InstCombinerImpl::visitICmpInst Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202011280603:202011290606 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5553416688107520 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] Issue 19203 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::APValue::swap
Updates: Status: WontFix Comment #2 on issue 19203 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::APValue::swap https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19203#c2 ClusterFuzz testcase 5668466220859392 is closed as invalid, so closing issue. -- 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] Issue 17606 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in EvaluateValue
Updates: Status: WontFix Comment #3 on issue 17606 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in EvaluateValue https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=17606#c3 ClusterFuzz testcase 5699838338924544 is closed as invalid, so closing issue. -- 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] Issue 19216 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in processTypeAttrs
Updates: Status: WontFix Comment #2 on issue 19216 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in processTypeAttrs https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19216#c2 ClusterFuzz testcase 5742049781612544 is closed as invalid, so closing issue. -- 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
