[llvm-bugs] [Bug 41259] switch is not converted into an argument LUT when a call return value is discarded
https://bugs.llvm.org/show_bug.cgi?id=41259 Hans Wennborg changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #10 from Hans Wennborg --- Looks like this was reverted in r360086 for reasons that aren't entirely clear yet. -- 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 41569] clangd vs LLVM_ENABLE_THREADS=OFF
https://bugs.llvm.org/show_bug.cgi?id=41569 Sam McCall changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED Fixed By Commit(s)||r360115 -- 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 41782] New: Deduce memcpy copy range
https://bugs.llvm.org/show_bug.cgi?id=41782
Bug ID: 41782
Summary: Deduce memcpy copy range
Product: libraries
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Scalar Optimizations
Assignee: unassignedb...@nondot.org
Reporter: david.bolvan...@gmail.com
CC: llvm-bugs@lists.llvm.org
bool foo(int *a, int *b, unsigned n) {
memcpy(a, b, 8); // memcpy expanded
return a == b;
}
foo(int*, int*, unsigned int):# @foo(int*, int*,
unsigned int)
mov rax, qword ptr [rsi]
mov qword ptr [rdi], rax
cmp rdi, rsi
seteal
ret
bool foo1(int *a, int *b, unsigned n) {
n = (n % 9);
memcpy(a, b, n);
return a == b;
}
bool foo2(int *a, int *b, unsigned n) {
while (n > 8) {
--n;
}
memcpy(a, b, n);
return a == b;
}
Clang emits memcpy call in foo1 and foo2, Clang does not expand it as in the
"foo" case, but it should.
foo1(int*, int*, unsigned int):# @foo(int*, int*,
unsigned int)
pushr14
pushrbx
pushrax
mov r14, rsi
mov rbx, rdi
mov eax, edx
imulrax, rax, 954437177
shr rax, 33
lea eax, [rax + 8*rax]
sub edx, eax
callmemcpy
cmp rbx, r14
seteal
add rsp, 8
pop rbx
pop r14
ret
foo2(int*, int*, unsigned int):# @foo(int*, int*,
unsigned int)
pushr14
pushrbx
pushrax
mov r14, rsi
mov rbx, rdi
cmp edx, 8
mov eax, 8
cmovae edx, eax
callmemcpy
cmp rbx, r14
seteal
add rsp, 8
pop rbx
pop r14
ret
--
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 41783] New: [clang-format] BreakConstructorInitializers doesn't preserve NOLINT comments
https://bugs.llvm.org/show_bug.cgi?id=41783
Bug ID: 41783
Summary: [clang-format] BreakConstructorInitializers doesn't
preserve NOLINT comments
Product: new-bugs
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: dennis.fels...@sap.com
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org
$ cat .clang-format
Language: Cpp
BreakConstructorInitializers: AfterColon
CommentPragmas: 'NOLINT'
$ cat x.cpp
class C
{
public:
C(C&& rhs) : // NOLINT(performance-noexcept-move-constructor)
x(rhs.x),
y(rhs.y)
{}
private:
int x;
int y;
};
$ clang-format x.cpp
class C {
public:
C(C &&rhs) :
// NOLINT(performance-noexcept-move-constructor)
x(rhs.x), y(rhs.y) {}
private:
int x;
int y;
};
After clang-format's reformatting the NOLINT marker loses its meaning for
clang-tidy. In this instance a NOLINTNEXTLINE could be used instead as a
workaround from clang-tidy's side.
Unfortunately even CommentPragma can't preserve the comment on the same line.
The only workaround I found is setting BreakConstructorInitializers:
BeforeComma, but in our case this is not wished.
Ideally the comment would stay on the same line and only the x(rhs.x), ... part
be broken over to the next line.
--
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 41716] Add support for `--cref`
https://bugs.llvm.org/show_bug.cgi?id=41716 Rui Ueyama changed: What|Removed |Added Status|NEW |RESOLVED CC||r...@google.com Resolution|--- |FIXED --- Comment #2 from Rui Ueyama --- As George wrote it's already implemented. Can you check that? -- 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 41784] New: volatile copy assignment operator for std::atomic
https://bugs.llvm.org/show_bug.cgi?id=41784
Bug ID: 41784
Summary: volatile copy assignment operator for std::atomic
Product: libc++
Version: 8.0
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P
Component: All Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: ilya.bury...@intel.com
CC: llvm-bugs@lists.llvm.org, mclow.li...@gmail.com
The code snippet below is compiled.
#include
int main()
{
volatile std::atomic a1;
std::atomic a2;
a1 = a2;
}
But shouldn't because copy assignment operator marked as deleted (atomic&
operator=( const atomic& ) volatile = delete) by 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 41785] New: Making class template breaks compilation
https://bugs.llvm.org/show_bug.cgi?id=41785
Bug ID: 41785
Summary: Making class template breaks compilation
Product: clang
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: C++
Assignee: unassignedclangb...@nondot.org
Reporter: we...@wsoptics.de
CC: blitzrak...@gmail.com, dgre...@apple.com,
erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org,
richard-l...@metafoo.co.uk
The following code compiles iff `-DFIX` is provided:
template
struct b : b
{
static constexpr unsigned c = a;
};
template <>
struct b<0>
{
};
#ifndef FIX
template
#endif
class X
{
void e();
static auto e(b<1> f) -> b;
static auto e(b{}))::c + 1> f) -> b;
void e(b{}))::c + 1>);
};
Also see https://godbolt.org/z/VHG_cE
--
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 14524 in oss-fuzz: llvm: Build failure
Updates: Status: Verified Comment #2 on issue 14524 by ClusterFuzz-External: llvm: Build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14524#c2 The latest build has succeeded, closing this 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] [Bug 41786] New: X86WinAllocaExpander::lower - Value stored to 'AmountReg' is never read
https://bugs.llvm.org/show_bug.cgi?id=41786
Bug ID: 41786
Summary: X86WinAllocaExpander::lower - Value stored to
'AmountReg' is never read
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, h...@chromium.org,
h...@hanshq.net, llvm-bugs@lists.llvm.org,
llvm-...@redking.me.uk, spatel+l...@rotateright.com
Ancient commit rL269828/rL269949
scan-build is complaining that the 'AmountReg' is written to but never read:
unsigned AmountReg = MI->getOperand(0).getReg();
MI->eraseFromParent();
// Delete the definition of AmountReg, possibly walking a chain of copies.
for (;;) {
if (!MRI->use_empty(AmountReg))
break;
MachineInstr *AmountDef = MRI->getUniqueVRegDef(AmountReg);
if (!AmountDef)
break;
if (AmountDef->isCopy() && AmountDef->getOperand(1).isReg())
AmountReg = AmountDef->getOperand(1).isReg();
AmountDef->eraseFromParent();
break;
}
I have no experience with this code, but the comment mentions walking the
copies, so should it be doing something like this?
if (AmountDef->isCopy() && AmountDef->getOperand(1).isReg()) {
AmountReg = AmountDef->getOperand(1).isReg();
continue;
}
--
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 34773] [SSE, AVX]: doesn't use packuswb with 2 different registers
https://bugs.llvm.org/show_bug.cgi?id=34773 Simon Pilgrim changed: What|Removed |Added Fixed By Commit(s)||r314788,r360134 Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #3 from Simon Pilgrim --- Resolving - rL360134 concatenates packus ops back together. -- 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 23698] [win] compiler_rt doesn't link when building with clang-cl.exe
https://bugs.llvm.org/show_bug.cgi?id=23698 Nico Weber changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 41355] Relocation records printed in the wrong format
https://bugs.llvm.org/show_bug.cgi?id=41355 George Rimar changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from George Rimar --- r360143 -- 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 14629 in oss-fuzz: llvm/llvm-isel-fuzzer--wasm32-O2: Abrt in llvm::llvm_unreachable_internal
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, mit...@google.com, bigchees...@gmail.com, eney...@google.com, llvm-b...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer Proj-llvm Reported-2019-05-07 Type: Bug New issue 14629 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--wasm32-O2: Abrt in llvm::llvm_unreachable_internal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14629 Detailed report: https://oss-fuzz.com/testcase?key=5657595710275584 Project: llvm Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--wasm32-O2 Fuzz target binary: llvm-isel-fuzzer--wasm32-O2 Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Abrt Crash Address: 0x0001 Crash State: llvm::llvm_unreachable_internal llvm::getLibcallSignature llvm::WebAssemblyMCInstLower::GetExternalSymbolSymbol Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201811180234:201811190234 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5657595710275584 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 37006] lld should typo-correct flags
https://bugs.llvm.org/show_bug.cgi?id=37006 Nico Weber changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #11 from Nico Weber --- r360145. I filed follow-up bug 41787 for finding a way to make typo correction work for /foo style flags as well. -- 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 41787] New: clang-cl and lld-link: Come up with a way to make typo correction work for '/' style flags
https://bugs.llvm.org/show_bug.cgi?id=41787 Bug ID: 41787 Summary: clang-cl and lld-link: Come up with a way to make typo correction work for '/' style flags Product: clang Version: unspecified Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: Driver Assignee: unassignedclangb...@nondot.org Reporter: nicolaswe...@gmx.de CC: llvm-bugs@lists.llvm.org, neeil...@live.com, richard-l...@metafoo.co.uk clang-cl and lld-link accept /foo flags in addition to -foo flags. Since /foo is also a valid path name on non-win, the logic goes like so: 1. If /foo is a known flag, treat it as flag (use -- to treat it as file name) 2. If it isn't, treat it as a file name So if a /foo flag has a typo, we treat it as a filename, hence don't show typo suggestions for it, and then show a "file not found" diagnostic. We should find a way to make typo suggestions work for /foo style flags. Ideas: - Have typo suggestions for filenames as well, and have a unified candidate list for both (idea from ruiu on issue 37006) - Add "3. If file of this name doesn't exist, consider it as a possible typo of a flag" The former is a nicer user experience since it also gives us spelling suggestions for typos in file names, but it requires getting a list of files off disk (only in error cases though) and is more work to implement. -- 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 41788] New: clangd tries to index/syntax check MATLAB files (.m extension conflict)
https://bugs.llvm.org/show_bug.cgi?id=41788
Bug ID: 41788
Summary: clangd tries to index/syntax check MATLAB files (.m
extension conflict)
Product: clang-tools-extra
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: clangd
Assignee: unassignedclangb...@nondot.org
Reporter: lilbil...@gmail.com
CC: llvm-bugs@lists.llvm.org
I've got clangd hooked up in VSCode and really like it. As part of my work I
also need to write MATLAB code for which I'm using the vscode-matlab extension
and have the extension .m bound to the language "matlab" in VSCode:
"files.associations": {"*.m": "matlab"}
However when I open a .m file in VSCode with clangd running, it validates the
file, likely as Objective-C, causing a bunch of errors to show up.
Can clangd indexing be based off of the language rather than the file
extension?
https://github.com/microsoft/vscode-extension-samples/blob/master/lsp-sample/package.json
shows binding with a language as well as their client:
https://github.com/microsoft/vscode-extension-samples/blob/master/lsp-sample/client/src/extension.ts
Using this mechanism allows users to perform the extension to language mapping
on their own.
--
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 14508 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: Reg >= X86::FP0 && Reg <= X86::FP6 && "Expected FP register!"
Comment #2 on issue 14508 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: Reg >= X86::FP0 && Reg <= X86::FP6 && "Expected FP register!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14508#c2 ClusterFuzz has detected this issue as fixed in range 201904290301:201905070306. Detailed report: https://oss-fuzz.com/testcase?key=5640319170772992 Project: llvm Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--x86_64-O2 Fuzz target binary: llvm-isel-fuzzer--x86_64-O2 Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: Reg >= X86::FP0 && Reg <= X86::FP6 && "Expected FP register!" FPS::processBasicBlock FPS::runOnMachineFunction Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710160455:201710190451 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201904290301:201905070306 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5640319170772992 See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for instructions to reproduce this bug locally. 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 11461 in oss-fuzz: llvm/llvm-isel-fuzzer--wasm32-O2: ASSERT: val != Map.end() && "unexpected runtime library name"
Comment #5 on issue 11461 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--wasm32-O2: ASSERT: val != Map.end() && "unexpected runtime library name" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11461#c5 ClusterFuzz has detected this issue as fixed in range 201904290301:201905070306. Detailed report: https://oss-fuzz.com/testcase?key=5690233278955520 Project: llvm Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--wasm32-O2 Fuzz target binary: llvm-isel-fuzzer--wasm32-O2 Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: val != Map.end() && "unexpected runtime library name" llvm::GetLibcallSignature llvm::WebAssemblyMCInstLower::GetExternalSymbolSymbol Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201811180234:201811190234 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201904290301:201905070306 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5690233278955520 See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for instructions to reproduce this bug locally. 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 12857 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: Val && "isa<> used on a null pointer"
Comment #5 on issue 12857 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: Val && "isa<> used on a null pointer" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12857#c5 ClusterFuzz has detected this issue as fixed in range 201904290301:201905070306. Detailed report: https://oss-fuzz.com/testcase?key=5667767804493824 Project: llvm Fuzzer: libFuzzer_llvm_llvm-opt-fuzzer--x86_64-instcombine Fuzz target binary: llvm-opt-fuzzer--x86_64-instcombine Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: Val && "isa<> used on a null pointer" computeKnownBitsFromOperator computeKnownBits Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201901220414:201902020421 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201904290301:201905070306 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5667767804493824 See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for instructions to reproduce this bug locally. 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 12846 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: EltTy && "Can't get a pointer to type!"
Comment #5 on issue 12846 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: EltTy && "Can't get a pointer to type!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12846#c5 ClusterFuzz has detected this issue as fixed in range 201904290301:201905070306. Detailed report: https://oss-fuzz.com/testcase?key=5641756073263104 Project: llvm Fuzzer: libFuzzer_llvm_llvm-opt-fuzzer--x86_64-instcombine Fuzz target binary: llvm-opt-fuzzer--x86_64-instcombine Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: EltTy && "Can't get a pointer to type!" llvm::PointerType::get SimplifyGEPInst Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201901220414:201902020421 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201904290301:201905070306 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5641756073263104 See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for instructions to reproduce this bug locally. 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 41760] get_default_resource is undefined
https://bugs.llvm.org/show_bug.cgi?id=41760 Zoe Carver changed: What|Removed |Added Resolution|--- |INVALID Status|NEW |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] Issue 14492 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: Abrt in llvm::llvm_unreachable_internal
Comment #2 on issue 14492 by ClusterFuzz-External: llvm/llvm-dwarfdump-fuzzer: Abrt in llvm::llvm_unreachable_internal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14492#c2 ClusterFuzz has detected this issue as fixed in range 201904290301:201905070306. Detailed report: https://oss-fuzz.com/testcase?key=5736410918682624 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::XCOFFObjectFile::getBytesInAddress llvm::DWARFContext::create Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201903270300:201904052014 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201904290301:201905070306 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5736410918682624 See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for instructions to reproduce this bug locally. 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 14159 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: IsVector && "cannot get number of elements on scalar/aggregate"
Comment #2 on issue 14159 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: IsVector && "cannot get number of elements on scalar/aggregate" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14159#c2 ClusterFuzz has detected this issue as fixed in range 201904290301:201905070306. Detailed report: https://oss-fuzz.com/testcase?key=5681405037641728 Project: llvm Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--aarch64-gisel Fuzz target binary: llvm-isel-fuzzer--aarch64-gisel Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: IsVector && "cannot get number of elements on scalar/aggregate" llvm::AArch64CallLowering::lowerReturn llvm::IRTranslator::runOnMachineFunction Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201904080300:201904100010 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201904290301:201905070306 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5681405037641728 See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for instructions to reproduce this bug locally. 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 14508 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: Reg >= X86::FP0 && Reg <= X86::FP6 && "Expected FP register!"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #3 on issue 14508 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: Reg >= X86::FP0 && Reg <= X86::FP6 && "Expected FP register!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14508#c3 ClusterFuzz testcase 5640319170772992 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 12846 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: EltTy && "Can't get a pointer to type!"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #6 on issue 12846 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: EltTy && "Can't get a pointer to type!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12846#c6 ClusterFuzz testcase 5641756073263104 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 12857 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: Val && "isa<> used on a null pointer"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #6 on issue 12857 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: Val && "isa<> used on a null pointer" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12857#c6 ClusterFuzz testcase 5667767804493824 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 9605 in oss-fuzz: llvm/clang-fuzzer: ASSERT: ParmVarDeclBits.ScopeDepthOrObjCQuals == scopeDepth && "truncation!"
Comment #7 on issue 9605 by ClusterFuzz-External: llvm/clang-fuzzer: ASSERT: ParmVarDeclBits.ScopeDepthOrObjCQuals == scopeDepth && "truncation!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=9605#c7 ClusterFuzz has detected this issue as fixed in range 201904290301:201905070306. Detailed report: https://oss-fuzz.com/testcase?key=6080258993291264 Project: llvm Fuzzer: libFuzzer_llvm_clang-fuzzer Fuzz target binary: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: ParmVarDeclBits.ScopeDepthOrObjCQuals == scopeDepth && "truncation!" clang::Sema::ActOnParamDeclarator clang::Parser::ParseParameterDeclarationClause Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201807260237:201807261853 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201904290301:201905070306 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6080258993291264 See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for instructions to reproduce this bug locally. 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 14159 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: IsVector && "cannot get number of elements on scalar/aggregate"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #3 on issue 14159 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: IsVector && "cannot get number of elements on scalar/aggregate" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14159#c3 ClusterFuzz testcase 5681405037641728 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 11461 in oss-fuzz: llvm/llvm-isel-fuzzer--wasm32-O2: ASSERT: val != Map.end() && "unexpected runtime library name"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #6 on issue 11461 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--wasm32-O2: ASSERT: val != Map.end() && "unexpected runtime library name" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11461#c6 ClusterFuzz testcase 5690233278955520 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 14492 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: Abrt in llvm::llvm_unreachable_internal
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #3 on issue 14492 by ClusterFuzz-External: llvm/llvm-dwarfdump-fuzzer: Abrt in llvm::llvm_unreachable_internal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14492#c3 ClusterFuzz testcase 5736410918682624 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 9605 in oss-fuzz: llvm/clang-fuzzer: ASSERT: ParmVarDeclBits.ScopeDepthOrObjCQuals == scopeDepth && "truncation!"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #8 on issue 9605 by ClusterFuzz-External: llvm/clang-fuzzer: ASSERT: ParmVarDeclBits.ScopeDepthOrObjCQuals == scopeDepth && "truncation!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=9605#c8 ClusterFuzz testcase 6080258993291264 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 14631 in oss-fuzz: llvm/llvm-isel-fuzzer--wasm32-O2: ASSERT: Val != Map.end() && "unexpected runtime library name"
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, mit...@google.com, bigchees...@gmail.com, eney...@google.com, llvm-b...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer Proj-llvm Reported-2019-05-07 Type: Bug New issue 14631 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--wasm32-O2: ASSERT: Val != Map.end() && "unexpected runtime library name" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14631 Detailed report: https://oss-fuzz.com/testcase?key=5100983250583552 Project: llvm Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--wasm32-O2 Fuzz target binary: llvm-isel-fuzzer--wasm32-O2 Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: Val != Map.end() && "unexpected runtime library name" llvm::getLibcallSignature llvm::WebAssemblyMCInstLower::GetExternalSymbolSymbol Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201811180234:201811190234 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5100983250583552 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 41789] New: lld documentation build fails with TemplateNotFound on Python 3.7/Sphinx 2.0.1
https://bugs.llvm.org/show_bug.cgi?id=41789
Bug ID: 41789
Summary: lld documentation build fails with TemplateNotFound on
Python 3.7/Sphinx 2.0.1
Product: lld
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: All Bugs
Assignee: unassignedb...@nondot.org
Reporter: ste...@uplinklabs.net
CC: llvm-bugs@lists.llvm.org, peter.sm...@linaro.org
Created attachment 21905
--> https://bugs.llvm.org/attachment.cgi?id=21905&action=edit
output of sphinx-build with -v -v arguments
I'm trying to build the current release_80 branch of lld, but the build failed
around generating the Sphinx documentation:
-
lld $ mkdir build; cd build
lld/build $ cmake -G Ninja .. -DLLVM_BUILD_DOCS=ON -DLLVM_ENABLE_SPHINX=ON
lld/build $ ninja docs/all
[1/1] Generating html Sphinx documentation for lld into
"/home/steven/lld-t/build/docs/html"
FAILED: docs/CMakeFiles/docs-lld-html
cd /home/steven/lld-t/build/docs && /usr/bin/sphinx-build -b html -d
/home/steven/lld-t/build/docs/_doctrees-lld-html -q -W /home/steven/lld-t/docs
/home/steven/lld-t/build/docs/html
Theme error:
An error happened in rendering the page index.
Reason: TemplateNotFound()
ninja: build stopped: subcommand failed.
-
I tried running sphinx-build without -q and with -v -v (output attached). It's
complaining about a missing template called "i", which strace shows it's trying
to access as well:
32385 stat("/usr/lib/python3.7/site-packages/sphinx/themes/basic/page.html",
{st_mode=S_IFREG|0644, st_size=273, ...}) = 0
32385 stat("/home/steven/lld-t/docs/_templates/layout.html",
{st_mode=S_IFREG|0644, st_size=305, ...}) = 0
32385 stat("/home/steven/lld-t/docs/llvm-theme/layout.html",
{st_mode=S_IFREG|0644, st_size=569, ...}) = 0
32385
stat("/usr/lib/python3.7/site-packages/sphinx/themes/basic/../basic/layout.html",
{st_mode=S_IFREG|0644, st_size=7811, ...}) = 0
32385 openat(AT_FDCWD, "/home/steven/lld-t/docs/_templates/i",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
32385 openat(AT_FDCWD, "/home/steven/lld-t/docs/llvm-theme/i",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
32385 openat(AT_FDCWD,
"/usr/lib/python3.7/site-packages/sphinx/themes/basic/i", O_RDONLY|O_CLOEXEC) =
-1 ENOENT (No such file or directory)
32385 openat(AT_FDCWD, "/home/steven/lld-t/docs/llvm-theme/../i",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
32385 openat(AT_FDCWD,
"/usr/lib/python3.7/site-packages/sphinx/themes/basic/../i",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
If I run the Python 2.7 version of Sphinx, it builds without any errors. I note
that I have two different versions of Sphinx installed (1.8.5 for Python 2.7
and 2.0.1 for Pyton 3.7). Maybe a problem with Sphinx v2.0.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 41183] Implicit function declarations also trigger -Wstrict-prototypes
https://bugs.llvm.org/show_bug.cgi?id=41183 James Y Knight changed: What|Removed |Added CC||jykni...@google.com Status|NEW |RESOLVED Resolution|--- |FIXED Assignee|unassignedclangbugs@nondot. |jykni...@google.com |org | --- Comment #1 from James Y Knight --- Fixed by https://github.com/llvm/llvm-project/commit/1fe312b34b742599be26a144b5318a1c9bfc65d4 -- 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 41655] Finding Bugs in LLVM 8 with PVS-Studio
https://bugs.llvm.org/show_bug.cgi?id=41655 Bug 41655 depends on bug 41774, which changed state. Bug 41774 Summary: GetFullTypeForDeclarator - ExpectNoDerefChunk assigned twice successively https://bugs.llvm.org/show_bug.cgi?id=41774 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 41774] GetFullTypeForDeclarator - ExpectNoDerefChunk assigned twice successively
https://bugs.llvm.org/show_bug.cgi?id=41774 Leonard Chan changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #1 from Leonard Chan --- Fixed in r360089 -- 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 41790] New: When same reg is used for output and implicit-def, spill is inserted and overwrites output result
https://bugs.llvm.org/show_bug.cgi?id=41790 Bug ID: 41790 Summary: When same reg is used for output and implicit-def, spill is inserted and overwrites output result Product: libraries Version: 7.0 Hardware: Other OS: other Status: NEW Severity: normal Priority: P Component: Register Allocator Assignee: unassignedb...@nondot.org Reporter: code.kc...@gmail.com CC: llvm-bugs@lists.llvm.org, quentin.colom...@gmail.com (Paste from @llvm.dev) I ran into a case where RegAlloc would insert a spill across instruction that had same register for output operand and implicit-def. The effect this had was that spill code would immediately overwrite the output result. Is this the expected result of setting up MyInst this way? In other words, does RegAlloc know to not insert spill in case it sees that output reg is same as one of implicit-def? If this is intended (always spilling live regs across implicit-def inst?), I am puzzled on how to use MyInst that has variable output reg with static implicit-defs. Any tips would be greatly appreciated. Reduced Example: Before RegAlloc: %1:reg = COPY ...; %2:reg = MyInst %1:reg, ..., implicit-def dead $p1, ...; %3:reg = Use %2:reg RegAlloc: >> %2:reg = MyInst %1:reg, ..., implicit-def dead $p1, ...; Regs: $p1=%1 Killing last use: %1:reg Assigning %2 to $p1 Spilling %2 in $p1 to stack slot #2 <-- suspicious if this is inserting spill, unaware of output reg being same << $p1 =MyInst killed $p1, ..., implicit-def dead $p1, ...; After RegAlloc: $p1 = COPY ...; Store $p1 %stack.2; $p1 =MyInst killed $p1, ..., implicit-def dead $p1, ...; $p1 = Load %stack.2; $p2 = Use $p1, ...; -- 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 41778] -fuse-ld errors
https://bugs.llvm.org/show_bug.cgi?id=41778 Reid Kleckner changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX CC||r...@google.com --- Comment #2 from Reid Kleckner --- Closing as wontfix, since I don't think there's anything for us to do here. OP used the path form of -fuse-ld, so it doesn't make sense for clang to try to differentiate between ld.lld and ld64.lld. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 14634 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: std::all_of(SrcOps.begin(), SrcOps.end(), [&, this](const SrcOp &Op) { return Op
Status: New
Owner:
CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com,
igm...@gmail.com, mit...@google.com, bigchees...@gmail.com,
eney...@google.com, llvm-b...@lists.llvm.org, j...@chromium.org,
v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com,
akils...@apple.com
Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible
Engine-libfuzzer Proj-llvm Reported-2019-05-07
Type: Bug
New issue 14634 by ClusterFuzz-External:
llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: std::all_of(SrcOps.begin(),
SrcOps.end(), [&, this](const SrcOp &Op) { return Op
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14634
Detailed report: https://oss-fuzz.com/testcase?key=5640324354932736
Project: llvm
Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--aarch64-gisel
Fuzz target binary: llvm-isel-fuzzer--aarch64-gisel
Job Type: libfuzzer_asan_llvm
Platform Id: linux
Crash Type: ASSERT
Crash Address:
Crash State:
std::all_of(SrcOps.begin(), SrcOps.end(), [&, this](const SrcOp &Op) {
return Op
llvm::MachineIRBuilder::buildInstr
llvm::CSEMIRBuilder::buildInstr
Sanitizer: address (ASAN)
Regressed:
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201904290301:201905070306
Reproducer Testcase:
https://oss-fuzz.com/download?testcase_id=5640324354932736
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
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 41792] New: Clang assertion failure on templated friend member function
https://bugs.llvm.org/show_bug.cgi?id=41792
Bug ID: 41792
Summary: Clang assertion failure on templated friend member
function
Product: clang
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Frontend
Assignee: unassignedclangb...@nondot.org
Reporter: rtr...@google.com
CC: llvm-bugs@lists.llvm.org, neeil...@live.com,
richard-l...@metafoo.co.uk
$ cat test.ii
template
class S {
template <>
friend S* S::Run();
};
$ clang -fsyntax-only test.ii
...
clang-9: ../tools/clang/include/clang/AST/DeclTemplate.h:133: clang::NamedDecl
*clang::TemplateParameterList::getParam(unsigned int): Assertion `Idx < size()
&& "Template parameter index out-of-range"' failed.
...
#9 0x048f3494 clang::TemplateParameterList::getParam(unsigned int)
#10 0x0728dc28 (anonymous
namespace)::DependencyChecker::DependencyChecker(clang::TemplateParameterList*,
bool)
#11 0x0722ed2f DependsOnTemplateParameters(clang::QualType,
clang::TemplateParameterList*)
#12 0x0722e297
clang::Sema::MatchTemplateParametersToScopeSpecifier(clang::SourceLocation,
clang::SourceLocation, clang::CXXScopeSpec const&,
clang::TemplateIdAnnotation*, llvm::ArrayRef,
bool, bool&, bool&)
#13 0x06a1fb70 clang::Sema::ActOnFunctionDeclarator(clang::Scope*,
clang::Declarator&, clang::DeclContext*, clang::TypeSourceInfo*,
clang::LookupResult&, llvm::MutableArrayRef,
bool&)
#14 0x06c7acdb clang::Sema::ActOnFriendFunctionDecl(clang::Scope*,
clang::Declarator&, llvm::MutableArrayRef)
#15 0x067a1af7
clang::Parser::ParseCXXClassMemberDeclaration(clang::AccessSpecifier,
clang::ParsedAttributes&, clang::Parser::ParsedTemplateInfo const&,
clang::ParsingDeclRAIIObject*)
#16 0x06831070
clang::Parser::ParseSingleDeclarationAfterTemplate(clang::DeclaratorContext,
clang::Parser::ParsedTemplateInfo const&, clang::ParsingDeclRAIIObject&,
clang::SourceLocation&, clang::ParsedAttributes&, clang::AccessSpecifier)
#17 0x06830ccd
clang::Parser::ParseTemplateDeclarationOrSpecialization(clang::DeclaratorContext,
clang::SourceLocation&, clang::ParsedAttributes&, clang::AccessSpecifier)
#18 0x067a0a60
clang::Parser::ParseCXXClassMemberDeclaration(clang::AccessSpecifier,
clang::ParsedAttributes&, clang::Parser::ParsedTemplateInfo const&,
clang::ParsingDeclRAIIObject*)
#19 0x067a3204
clang::Parser::ParseCXXClassMemberDeclarationWithPragmas(clang::AccessSpecifier&,
clang::Parser::ParsedAttributesWithRange&, clang::TypeSpecifierType,
clang::Decl*)
#20 0x0679e8a2
clang::Parser::ParseCXXMemberSpecification(clang::SourceLocation,
clang::SourceLocation, clang::Parser::ParsedAttributesWithRange&, unsigned int,
clang::Decl*)
#21 0x0679d288
clang::Parser::ParseClassSpecifier(clang::tok::TokenKind,
clang::SourceLocation, clang::DeclSpec&, clang::Parser::ParsedTemplateInfo
const&, clang::AccessSpecifier, bool, clang::Parser::DeclSpecContext,
clang::Parser::ParsedAttributesWithRange&)
#22 0x06778022
clang::Parser::ParseDeclarationSpecifiers(clang::DeclSpec&,
clang::Parser::ParsedTemplateInfo const&, clang::AccessSpecifier,
clang::Parser::DeclSpecContext, clang::Parser::LateParsedAttrList*)
#23 0x0683120d
clang::Parser::ParseSingleDeclarationAfterTemplate(clang::DeclaratorContext,
clang::Parser::ParsedTemplateInfo const&, clang::ParsingDeclRAIIObject&,
clang::SourceLocation&, clang::ParsedAttributes&, clang::AccessSpecifier)
#24 0x06830ccd
clang::Parser::ParseTemplateDeclarationOrSpecialization(clang::DeclaratorContext,
clang::SourceLocation&, clang::ParsedAttributes&, clang::AccessSpecifier)
#25 0x06830656
clang::Parser::ParseDeclarationStartingWithTemplate(clang::DeclaratorContext,
clang::SourceLocation&, clang::ParsedAttributes&, clang::AccessSpecifier)
#26 0x06774629
clang::Parser::ParseDeclaration(clang::DeclaratorContext,
clang::SourceLocation&, clang::Parser::ParsedAttributesWithRange&)
#27 0x06753fd9
clang::Parser::ParseExternalDeclaration(clang::Parser::ParsedAttributesWithRange&,
clang::ParsingDeclSpec*)
#28 0x067527bf
clang::Parser::ParseTopLevelDecl(clang::OpaquePtr&, bool)
#29 0x06752123
clang::Parser::ParseFirstTopLevelDecl(clang::OpaquePtr&)
#30 0x0674ddee clang::ParseAST(clang::Sema&, bool, bool)
#31 0x046fb172 clang::ASTFrontendAction::ExecuteAction()
...
--
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 41793] New: Please backport r360212 to 8.0
https://bugs.llvm.org/show_bug.cgi?id=41793 Bug ID: 41793 Summary: Please backport r360212 to 8.0 Product: new-bugs Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: mgo...@gentoo.org CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org Blocks: 41221 Please backport the following change to 8.0. It's necessary to fix build due to changes on NetBSD end. From: Kamil Rytarowski Date: Wed, 8 May 2019 00:44:41 + Subject: [PATCH] Fix build on NetBSD 8.99.38 With recent changes the dev/nvmm/nvmm_ioctl.h header is no longer a standalone NVMM header. Disable it until the NVMM operations will stabilize and be included in the ioctl(2) interceptors. git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@360212 91177308-0d34-0410-b5e6-96231b3b80d8 Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=41221 [Bug 41221] [meta] 8.0.1 Release Blockers -- 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
