[llvm-bugs] Issue 4704 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: Abrt in handleLLVMFatalError
Updates: Labels: -Reproducible Unreproducible Comment #17 on issue 4704 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-gisel: Abrt in handleLLVMFatalError https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4704#c17 ClusterFuzz testcase 5730196100481024 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 3705 in oss-fuzz: llvm/clang-fuzzer: ASSERT: getResultKind() == Found && "getFoundDecl called on non-unique result"
Updates: Labels: -Reproducible Unreproducible Comment #18 on issue 3705 by ClusterFuzz-External: llvm/clang-fuzzer: ASSERT: getResultKind() == Found && "getFoundDecl called on non-unique result" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3705#c18 ClusterFuzz testcase 5269652176371712 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 43370] New: Clang crashes in code generation of builtin atomic operation.
https://bugs.llvm.org/show_bug.cgi?id=43370
Bug ID: 43370
Summary: Clang crashes in code generation of builtin atomic
operation.
Product: clang
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: C++
Assignee: unassignedclangb...@nondot.org
Reporter: dineshkumar.bhaska...@amd.com
CC: blitzrak...@gmail.com, dgre...@apple.com,
erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org,
richard-l...@metafoo.co.uk
clang crashes during the compilation of a test program
compiled using command : clang test.cpp
---
// test.cpp
typedef unsigned long long uint64_t;
template
void fun()
{
uint64_t v[2];
__atomic_store_n(v, 0, 0);
}
int main()
{
fun<3>();
}
---
Backtrace and run scritps
0. Program arguments: /root/clang/bin/clang-10 -cc1 -triple
x86_64-unknown-linux-gnu -emit-obj -mrelax-all -disable-free -main-file-name
test.cpp -mrelocation-model static -mthread-model posix -mframe-pointer=all
-fmath-errno -masm-verbose -mconstructor-aliases -mun
wind-tables -fuse-init-array -target-cpu x86-64 -dwarf-column-info
-debugger-tuning=gdb -resource-dir /root/clang/lib/clang/10.0.0
-internal-isystem
/usr/lib/gcc/x86_64-linux-gnu/5.4.0/../../../../include/c++/5.4.0
-internal-isystem /usr/lib/gcc/x86_64-linux-gnu/5.4.0/..
/../../../include/x86_64-linux-gnu/c++/5.4.0 -internal-isystem
/usr/lib/gcc/x86_64-linux-gnu/5.4.0/../../../../include/x86_64-linux-gnu/c++/5.4.0
-internal-isystem
/usr/lib/gcc/x86_64-linux-gnu/5.4.0/../../../../include/c++/5.4.0/backward
-internal-isystem /usr/local/inc
lude -internal-isystem /root/clang/lib/clang/10.0.0/include
-internal-externc-isystem /usr/include/x86_64-linux-gnu
-internal-externc-isystem /include -internal-externc-isystem /usr/include
-fdeprecated-macro -fdebug-compilation-dir /root/llvm-project/llvm/build
-ferror-
limit 19 -fmessage-length 0 -fobjc-runtime=gcc -fcxx-exceptions -fexceptions
-fdiagnostics-show-option -fcolor-diagnostics -faddrsig -o /tmp/test-73c289.o
-x c++ test.cpp
1. parser at end of file
2. Per-file LLVM IR generation
3. test.cpp:5:6: Generating code for declaration 'fun'
#0 0x02994349 llvm::sys::PrintStackTrace(llvm::raw_ostream&)
/root/llvm-project/llvm/lib/Support/Unix/Signals.inc:532:11
#1 0x029944f9 PrintStackTraceSignalHandler(void*)
/root/llvm-project/llvm/lib/Support/Unix/Signals.inc:593:1
#2 0x02992dc6 llvm::sys::RunSignalHandlers()
/root/llvm-project/llvm/lib/Support/Signals.cpp:67:5
#3 0x02994c4b SignalHandler(int)
/root/llvm-project/llvm/lib/Support/Unix/Signals.inc:384:1
#4 0x7fec2810d390 __restore_rt
(/lib/x86_64-linux-gnu/libpthread.so.0+0x11390)
#5 0x7fec26ea0428 raise (/lib/x86_64-linux-gnu/libc.so.6+0x35428)
#6 0x7fec26ea202a abort (/lib/x86_64-linux-gnu/libc.so.6+0x3702a)
#7 0x7fec26e98bd7 (/lib/x86_64-linux-gnu/libc.so.6+0x2dbd7)
#8 0x7fec26e98c82 (/lib/x86_64-linux-gnu/libc.so.6+0x2dc82)
#9 0x02c989e5 clang::QualType::getCommonPtr() const
/root/llvm-project/llvm/tools/clang/include/clang/AST/Type.h:660:59
#10 0x02c98995 clang::QualType::getTypePtr() const
/root/llvm-project/llvm/tools/clang/include/clang/AST/Type.h:6149:26
#11 0x02c985d5 clang::QualType::operator->() const
/root/llvm-project/llvm/tools/clang/include/clang/AST/Type.h:701:5
#12 0x0303ceca
clang::CodeGen::CodeGenFunction::EmitAtomicExpr(clang::AtomicExpr*)
/root/llvm-project/llvm/tools/clang/lib/CodeGen/CGAtomic.cpp:748:40
#13 0x031c9600 (anonymous
namespace)::ScalarExprEmitter::VisitAtomicExpr(clang::AtomicExpr*)
/root/llvm-project/llvm/tools/clang/lib/CodeGen/CGExprScalar.cpp:4422:14
#14 0x031c4734 clang::StmtVisitorBase::Visit(clang::Stmt*)
/root/llvm-project/llvm/build/tools/clang/include/clang/AST/StmtNodes.inc:611:1
#15 0x031bb349 (anonymous
namespace)::ScalarExprEmitter::Visit(clang::Expr*)
/root/llvm-project/llvm/tools/clang/lib/CodeGen/CGExprScalar.cpp:425:3
#16 0x031bb293
clang::CodeGen::CodeGenFunction::EmitScalarExpr(clang::Expr const*, bool)
/root/llvm-project/llvm/tools/clang/lib/CodeGen/CGExprScalar.cpp:4435:3
#17 0x03162747 clang::CodeGen::CodeGenFunction::EmitAnyExpr(clang::Expr
const*, clang::CodeGen::AggValueSlot, bool)
/root/llvm-project/llvm/tools/clang/lib/CodeGen/CGExpr.cpp:199:12
#18 0x0316266d
clang::CodeGen::CodeGenFunction::EmitIgnoredExpr(clang::Expr const*)
/root/llvm-project/llvm/tools/clang/lib/CodeGen/CGExpr.cpp:184:19
#19 0x02db1030 clang::CodeGen::CodeGenFunction::EmitStmt(clang::Stmt
const*, llvm::ArrayRef)
/root/llvm-project/llvm/tools/clang/lib/CodeGen/CGStmt.cpp:114:34
#20 0x02db9120
clang::CodeGen::CodeGenFunction::EmitCompoundStmtWithoutScope(cl
[llvm-bugs] Issue 4755 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: I.use_empty() && "Cannot erase instruction that is used!"
Updates: Labels: -Reproducible Unreproducible Comment #13 on issue 4755 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: I.use_empty() && "Cannot erase instruction that is used!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4755#c13 ClusterFuzz testcase 5484688949903360 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 43369] New: Large compile time regression when building CheckerRegistry.cpp using Visual Studio 2017 on Windows
https://bugs.llvm.org/show_bug.cgi?id=43369 Bug ID: 43369 Summary: Large compile time regression when building CheckerRegistry.cpp using Visual Studio 2017 on Windows Product: new-bugs Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: douglas_y...@playstation.sony.com CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org After upstream commit r369961, compiling the file clang\lib\StaticAnalyzer\Frontend\CheckerRegistry.cpp with optimizations enabled on Windows using Visual Studio 2017 has greatly increased in the amount of time needed to compile on my machine. I generated preprocessed files using r369960 and r369961 and built each on my machine with the following results: C:\sandbox\r369961\upstream>..\timecmd.cmd "C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.16.27023\bin\HostX64\x64\CL.exe" /c CheckerRegistry.good.i /TP /wd4624 /O2 Microsoft (R) C/C++ Optimizing Compiler Version 19.16.27031.1 for x64 Copyright (C) Microsoft Corporation. All rights reserved. CheckerRegistry.good.i command took 0:0:29.97 (29.97s total) C:\sandbox\r369961\upstream>..\timecmd.cmd "C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.16.27023\bin\HostX64\x64\CL.exe" /c CheckerRegistry.bad.i /TP /wd4624 /O2 Microsoft (R) C/C++ Optimizing Compiler Version 19.16.27031.1 for x64 Copyright (C) Microsoft Corporation. All rights reserved. CheckerRegistry.bad.i command took 0:10:4.87 (604.87s total) Note the time required to compile went from ~30 seconds to around 10 minutes! Other files in the build of clang may also be affected, but this one seems to stand out the most on my machine as it was causing timeouts in our distributed build system due to the long compilation time. I am attaching preprocessed copies of the CheckerRegistry.cpp file to help ease reproduction. CheckerRegistry.good.i is a preprocessed version of the file from r269960, and CheckerRegistry.bad.i is a preprocessed version of the file from r269961. To build, simply use options /TP /O2, and optionally /wd4624 to silence a warning. -- 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 43368] New: [LLD][MIPS][FreeBSD] ld -b binary outputs objects with no ABI flags
https://bugs.llvm.org/show_bug.cgi?id=43368 Bug ID: 43368 Summary: [LLD][MIPS][FreeBSD] ld -b binary outputs objects with no ABI flags Product: new-bugs Version: unspecified Hardware: PC OS: FreeBSD Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: kev...@freebsd.org CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org Created attachment 22532 --> https://bugs.llvm.org/attachment.cgi?id=22532&action=edit git(1) diff against our contrib tree Our firmware kmod build is kind of funky, I think- we start off by linking together an object from our binary blob: $ ld.lld -b binary -m elf32btsmip_fbsd -r -d -o blob.fwo blob We then build a stub module that uses _binary_blob_start/end and passes it through our firmware(9) interface. We hit the following error when we go to link the final .ko: ld.lld: error: otusfw_init.o: ABI 'o32' is incompatible with target ABI 'n64 The problem is easy to spot: $ readelf -a otusfw_init.fwo| egrep 'Class:|Flags:' Class: ELF32 Flags: 0, mips1 lld assumes that no flags means n64, and none are set because we didn't have any input files that we could have gleaned it from. BFD doesn't seem to set flags, but I don't know that BFD was doing ABI check on all of the input objects. Regardless, I propose the attached patch. The attached patch, in the absence of input files to derive flags from, takes it from the -m flag. The -m flag gives us enough to know which ABI we're emulating, so we might as well apply them to the resulting blob to appease 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 12439 in oss-fuzz: llvm/llvm-itanium-demangle-fuzzer: Stack-overflow in llvm::itanium_demangle::AbstractManglingParser
Comment #13 on issue 12439 by ClusterFuzz-External: llvm/llvm-itanium-demangle-fuzzer: Stack-overflow in llvm::itanium_demangle::AbstractManglingParser https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12439#c13 ClusterFuzz found another reproducible variant for this bug on libfuzzer_asan_llvm job: https://oss-fuzz.com/testcase?key=573354855232. -- 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 12439 in oss-fuzz: llvm/llvm-itanium-demangle-fuzzer: Stack-overflow in llvm::itanium_demangle::AbstractManglingParser
Comment #12 on issue 12439 by ClusterFuzz-External: llvm/llvm-itanium-demangle-fuzzer: Stack-overflow in llvm::itanium_demangle::AbstractManglingParser https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12439#c12 ClusterFuzz found another reproducible variant for this bug on libfuzzer_asan_llvm job: https://oss-fuzz.com/testcase?key=5697327544664064. -- 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 12439 in oss-fuzz: llvm/llvm-itanium-demangle-fuzzer: Stack-overflow in llvm::itanium_demangle::AbstractManglingParser
Comment #11 on issue 12439 by ClusterFuzz-External: llvm/llvm-itanium-demangle-fuzzer: Stack-overflow in llvm::itanium_demangle::AbstractManglingParser https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12439#c11 ClusterFuzz found another reproducible variant for this bug on libfuzzer_asan_llvm job: https://oss-fuzz.com/testcase?key=5631550711922688. -- 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 43367] New: [ICE] Assertion failed: Invalid modifier for QualType argument
https://bugs.llvm.org/show_bug.cgi?id=43367
Bug ID: 43367
Summary: [ICE] Assertion failed: Invalid modifier for QualType
argument
Product: clang
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P
Component: Frontend
Assignee: unassignedclangb...@nondot.org
Reporter: tras...@gmail.com
CC: llvm-bugs@lists.llvm.org, neeil...@live.com,
richard-l...@metafoo.co.uk
struct exception
{};
class bad_cast : exception
{
bad_cast(char* m) : exception(m)
{}
};
$ clang++ -v
clang version 10.0.0 (https://github.com/llvm/llvm-project.git
0cfb78e52af247366e6e8fe00a906022bf4abca5)
Target: x86_64-pc-windows-msvc
$ clang++.exe -c test.cpp
error: no matching constructor for initialization of 'exception'
Assertion failed: Modifier.empty() && Argument.empty() && "Invalid modifier for
QualType argument", file clang\lib\AST\ASTDiagnostic.cpp, line 385
Stack dump:
1. test.cpp:6:5: current parser token '{'
2. test.cpp:3:1: parsing struct/union/class body 'bad_cast'
clang::FormatASTNodeDiagnosticArgument() + 0xF5F bytes(s),
clang\lib\AST\ASTDiagnostic.cpp, line 388
clang::Diagnostic::FormatDiagnostic() + 0x748 bytes(s),
clang\lib\Basic\Diagnostic.cpp, line 991 + 0x158 byte(s)
clang::Diagnostic::FormatDiagnostic() + 0xAB bytes(s),
clang\lib\Basic\Diagnostic.cpp, line 772
clang::TextDiagnosticPrinter::HandleDiagnostic() + 0x55 bytes(s),
clang\lib\Frontend\TextDiagnosticPrinter.cpp, line 119
clang::DiagnosticIDs::ProcessDiag() + 0x1F7 bytes(s),
clang\lib\Basic\DiagnosticIDs.cpp, line 704 + 0x42 byte(s)
clang::DiagnosticsEngine::EmitCurrentDiagnostic() + 0x78 bytes(s),
clang\lib\Basic\Diagnostic.cpp, line 516 + 0xB byte(s)
clang::Sema::EmitCurrentDiagnostic() + 0x21A bytes(s), clang\lib\Sema\Sema.cpp,
line 1369 + 0xB byte(s)
DiagnoseBadConversion() + 0x3415 bytes(s), clang\lib\Sema\SemaOverload.cpp,
line 9935 + 0x55 byte(s)
clang::OverloadCandidateSet::NoteCandidates() + 0x196D bytes(s),
clang\lib\Sema\SemaOverload.cpp, line 10887 + 0x968 byte(s)
clang::OverloadCandidateSet::NoteCandidates() + 0x142 bytes(s),
clang\lib\Sema\SemaOverload.cpp, line 10865
clang::InitializationSequence::Diagnose()
--
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 43366] New: If dyn_cast(X) is non-null, assume X is non-null as well?
https://bugs.llvm.org/show_bug.cgi?id=43366
Bug ID: 43366
Summary: If dyn_cast(X) is non-null, assume X is non-null
as well?
Product: clang
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: Static Analyzer
Assignee: dcough...@apple.com
Reporter: llvm-...@redking.me.uk
CC: dcough...@apple.com, llvm-bugs@lists.llvm.org,
noqnoq...@gmail.com
Noticed here:
https://llvm.org/reports/scan-build/report-AArch64TargetTransformInfo.cpp-getValueType-12-1.html#EndPath
if (auto *VTy = dyn_cast(Ty)) {
Type *EltTy = VTy->getElementType();
// Lower vectors of pointers to native pointer types.
if (auto *PTy = dyn_cast(EltTy)) {
EVT PointerTy(getPointerTy(DL, PTy->getAddressSpace()));
EltTy = PointerTy.getTypeForEVT(Ty->getContext());
}
return EVT::getVectorVT(Ty->getContext(), EVT::getEVT(EltTy, false),
VTy->getElementCount());
}
The warning says that Ty->getContext() can be a null pointer, but if we know
that VTy is non-null and is a dyn_cast from Ty, then shouldn't Ty be known to
be non-null?
--
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 43365] New: Merge r372186 and r372187 to 9.0 branch: [ARM] VFPv2 only supports 16 D registers.
https://bugs.llvm.org/show_bug.cgi?id=43365 Bug ID: 43365 Summary: Merge r372186 and r372187 to 9.0 branch: [ARM] VFPv2 only supports 16 D registers. Product: libraries Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: Backend: ARM Assignee: unassignedb...@nondot.org Reporter: efrie...@quicinc.com CC: llvm-bugs@lists.llvm.org, oliver.stann...@arm.com, peter.sm...@linaro.org, t.p.northo...@gmail.com, ties.st...@arm.com These fix a very easy to reproduce miscompile if the user specifies -mfpu=vfpv2 (or an equivalent -mcpu flag). Probably not that important for general usage, since it only affects pre-v7 ARM targets with an FPU, but it's a showstopper if you need to target one of those specific CPUs. Should be low risk in terms of correctness, but I'm not sure whether we're allowed to remove target features in a point release. Maybe on the branch we could keep the "vfp2d16" and "vfp2d16sp" target features, but make them no-ops. -- 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 43364] New: [Umbrella] Pointer cast representation problems.
https://bugs.llvm.org/show_bug.cgi?id=43364
Bug ID: 43364
Summary: [Umbrella] Pointer cast representation problems.
Product: clang
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: Static Analyzer
Assignee: dcough...@apple.com
Reporter: noqnoq...@gmail.com
CC: dcough...@apple.com, llvm-bugs@lists.llvm.org
An umbrella bug for figuring out how to fix our representation of pointer
casts. The main problem with the current representation is that there are
multiple ways of representing the same pointer, however there's no canonical
way of representing a pointer, so different parts of the Analyzer are doing
this differently and only accidentally work together more or less nicely.
Here are a few examples of how they don't really work together nicely:
(1) In http://lists.llvm.org/pipermail/cfe-dev/2019-September/063308.html we
have two different symbolic values for the same actual pointer value, which
wear different constraints after dereferencing:
reg_$1},0
S64b,Item}->xxs>: { [-2147483648, 0] }
reg_$2}->xxs>: { [1, 2147483647]
}
(2) Here's another example that's a bit more controversial due to strict
aliasing violation, but still problematic and slightly more obvious:
typedef struct {
int RetCode;
} A;
typedef struct {
int RetCode;
} B;
int blah(A *param, int *x) {
if (param->RetCode != 0) // reg_$1}->RetCode>
return ((B *) param)->RetCode; // reg_$2{element{B, 0 S32b,
SymRegion{reg_$0}->RetCore}
*x = 1;
return 0;
}
int foo(A* param) {
int x;
if (blah(param, &x) != 0) {
return 0;
}
return x; // false positive: "returning garbage value".
}
Here we have in the following:
param->RetCode: reg_$1}->RetCode>
((B *) param)->RetCode: reg_$2{element{B, 0 S32b,
SymRegion{reg_$0}->RetCore}
(3) The following bugs of this kind are already fixed in a non-principled
manner:
https://reviews.llvm.org/D38797
https://reviews.llvm.org/D46224
https://reviews.llvm.org/D46415
https://reviews.llvm.org/D51191
https://reviews.llvm.org/D52189
https://reviews.llvm.org/D55875
(4) This is also a piece of technical debt that causes annoyance when writing
new code:
https://reviews.llvm.org/D40939
https://reviews.llvm.org/D41250
https://reviews.llvm.org/D67079#inline-602514
--
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 43363] New: Segfault/Assertion failure in ___kmp_fast_free
https://bugs.llvm.org/show_bug.cgi?id=43363 Bug ID: 43363 Summary: Segfault/Assertion failure in ___kmp_fast_free Product: OpenMP Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: Runtime Library Assignee: unassignedb...@nondot.org Reporter: lennart.br...@posteo.de CC: llvm-bugs@lists.llvm.org Created attachment 22530 --> https://bugs.llvm.org/attachment.cgi?id=22530&action=edit reproducer and asan/gdb traces Hi everyone, I ran into an issue which causes crashes of our application when compiled with Clang and libomp (8.0.1 each). I was able to reproduce it with version 9.0.0rc6 of libomp compiled with debug symbols and ASan. Most of the time, ASan reports a SEGV caused by a READ operation in ___kmp_fast_free (according to GDB at kmp_alloc.cpp:1956, according to ASan in kmp_alloc.cpp:1944). Sometimes one of the following assertions fails: https://github.com/llvm/llvm-project/blob/12f174e98c3514755b21db2f040544c0b2ed5f67/openmp/runtime/src/kmp_alloc.cpp#L1970-L1976 https://github.com/llvm/llvm-project/blob/12f174e98c3514755b21db2f040544c0b2ed5f67/openmp/runtime/src/kmp_alloc.cpp#L1980 To reproduce the crash I have attached some example code (crash_omp.cpp) which is based on one of our test cases. I tried to strip all unnecessary code and make the example as small as possible. Hence, the code itself probably does not make much sense anymore. On my machine the crash appears usually in iteration 4 of the loop in the main function. Compile it as: $ clang++ -o crash_omp -std=c++17 -fopenmp=libomp -g -fsanitize=address crash_omp.cpp I run Arch Linux on x86_64 and used the following versions of libomp and Clang: libomp 9.0.0-rc6 (from https://github.com/llvm/llvm-project/archive/llvmorg-9.0.0-rc6.tar.gz) compiled with: cmake .. -G Ninja \ -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++ \ -DCMAKE_C_FLAGS=-fsanitize=address \ -DCMAKE_BUILD_TYPE=Debug \ -DCMAKE_INSTALL_PREFIX=/usr $ clang++ --version clang version 8.0.1 (tags/RELEASE_801/final) Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/bin Attachments: * crash_omp.cpp * asan_output.txt * gdb_stacktrace.txt Please let me know if you need more information. Best Lennart PS: While debugging I noticed that #pragma omp taskloop num_tasks(n) default(shared) with n == 0 causes libomp to perform a division by 0 which results in a crash with SIGFPE. I don't know if this behavior is intended or an error message is preferred here. (The spec requires n to be positive https://www.openmp.org/spec-html/5.0/openmpsu47.html) -- 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 4068] [Meta] Compiling the Linux kernel with clang
https://bugs.llvm.org/show_bug.cgi?id=4068 Bug 4068 depends on bug 42309, which changed state. Bug 42309 Summary: Asm goto expected a symbol reference https://bugs.llvm.org/show_bug.cgi?id=42309 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- 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 42309] Asm goto expected a symbol reference
https://bugs.llvm.org/show_bug.cgi?id=42309 Nick Desaulniers changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #5 from Nick Desaulniers --- I can no longer reproduce the issue/test case from the bug Description with ToT clang. I believe this was fixed by r368478 or r368477. Please reopen with new test cases if this is still an issue. -- 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 43362] New: InterpStack.cpp fails to build with gcc after r371834
https://bugs.llvm.org/show_bug.cgi?id=43362 Bug ID: 43362 Summary: InterpStack.cpp fails to build with gcc after r371834 Product: new-bugs Version: trunk Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: lukebe...@hotmail.com CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org After http://llvm.org/viewvc/llvm-project?view=revision&revision=371834 I cannot build clang with recent builds of gcc. It is failing with the following errors: /clang/lib/AST/Interp/InterpStack.cpp:35:31: note: ‘malloc’ is defined in header ‘’; did you forget to ‘#include ’? /clang/lib/AST/Interp/InterpStack.cpp: In member function ‘void clang::interp::InterpStack::shrink(size_t)’: /clang/lib/AST/Interp/InterpStack.cpp:67:7: error: ‘free’ was not declared in this scope 67 | free(Chunk->Next); | ^~~~ /clang/lib/AST/Interp/InterpStack.cpp:67:7: note: ‘free’ is defined in header ‘’; did you forget to ‘#include ’? tools/clang/lib/AST/CMakeFiles/obj.clangAST.dir/build.make:1286: recipe for target 'tools/clang/lib/AST/CMakeFiles/obj.clangAST.dir/Interp/InterpStack.cpp.o' failed make[3]: *** [tools/clang/lib/AST/CMakeFiles/obj.clangAST.dir/Interp/InterpStack.cpp.o] Error 1 CMakeFiles/Makefile2:24317: recipe for target 'tools/clang/lib/AST/CMakeFiles/obj.clangAST.dir/all' failed make[2]: *** [tools/clang/lib/AST/CMakeFiles/obj.clangAST.dir/all] Error 2 make[2]: *** Waiting for unfinished jobs -- 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 6158 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: RC && "This value type is not natively supported!"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #13 on issue 6158 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: RC && "This value type is not natively supported!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6158#c13 ClusterFuzz testcase 6518991817277440 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201909180332:201909190331 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 4749 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: LHS.getValueType() == MVT::f16 || LHS.getValueType() == MVT::f32 || LHS.getValue
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #13 on issue 4749 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: LHS.getValueType() == MVT::f16 | | LHS.getValueType() == MVT::f32 || LHS.getValue https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4749#c13 ClusterFuzz testcase 6194536985395200 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201909180332:201909190331 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 17412 in oss-fuzz: llvm:llvm-special-case-list-fuzzer: Timeout in llvm-special-case-list-fuzzer
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #1 on issue 17412 by ClusterFuzz-External: llvm:llvm-special-case-list-fuzzer: Timeout in llvm-special-case-list-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=17412#c1 ClusterFuzz testcase 6195196412297216 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201909180332:201909190331 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 6527 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in ComplexExprEvaluator::VisitBinaryOperator
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #11 on issue 6527 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in ComplexExprEvaluator::VisitBinaryOperator https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6527#c11 ClusterFuzz testcase 5861530882015232 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201909180332:201909190331 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 3353 in oss-fuzz: llvm: ASSERT: CodeDC && !CodeDC->isFileContext() && "statement expr not in code context"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #17 on issue 3353 by ClusterFuzz-External: llvm: ASSERT: CodeDC && !CodeDC->isFileContext() && "statement expr not in code context" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3353#c17 ClusterFuzz testcase 5900679908425728 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201909180332:201909190331 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 3264 in oss-fuzz: llvm: ASSERT: Ancestor->getEntity() == CurContext && "ancestor context mismatch"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #19 on issue 3264 by ClusterFuzz-External: llvm: ASSERT: Ancestor->getEntity() == CurContext && "ancestor context mismatch" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3264#c19 ClusterFuzz testcase 5840450994831360 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201909180332:201909190331 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 17498 in oss-fuzz: llvm:clang-fuzzer: ASSERT: DD && "queried property of class with no definition"
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 OS-Linux Proj-llvm Reported-2019-09-19 Type: Bug New issue 17498 by ClusterFuzz-External: llvm:clang-fuzzer: ASSERT: DD && "queried property of class with no definition" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=17498 Detailed Report: https://oss-fuzz.com/testcase?key=6243912833826816 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: DD && "queried property of class with no definition" clang::CXXRecordDecl::data getDefaultInitValue Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201909180332:201909190331 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6243912833826816 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 15536 in oss-fuzz: llvm/clang-fuzzer: Null-dereference READ in clang::Sema::~Sema
Updates: Labels: Deadline-Approaching Comment #1 on issue 15536 by sheriff...@chromium.org: llvm/clang-fuzzer: Null-dereference READ in clang::Sema::~Sema https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15536#c1 This bug is approaching its deadline for being fixed, and will be automatically derestricted within 7 days. If a fix is planned within 2 weeks after the deadline has passed, a grace extension can be granted. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 15534 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-loop_unroll: Null-dereference READ in BitcodeReader::parseFunctionBody
Updates: Labels: Deadline-Approaching Comment #1 on issue 15534 by sheriff...@chromium.org: llvm/llvm-opt-fuzzer--x86_64-loop_unroll: Null-dereference READ in BitcodeReader::parseFunctionBody https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15534#c1 This bug is approaching its deadline for being fixed, and will be automatically derestricted within 7 days. If a fix is planned within 2 weeks after the deadline has passed, a grace extension can be granted. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 15525 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-guard_widening: ASSERT: V->getType() == flattenPointerTypes(CurFullTy) && "Incorrect fully structured ty
Updates: Labels: Deadline-Approaching Comment #1 on issue 15525 by sheriff...@chromium.org: llvm/llvm-opt-fuzzer--x86_64-guard_widening: ASSERT: V->getType() == flattenPointerTypes(CurFullTy) && "Incorrect fully structured ty https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15525#c1 This bug is approaching its deadline for being fixed, and will be automatically derestricted within 7 days. If a fix is planned within 2 weeks after the deadline has passed, a grace extension can be granted. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 15520 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-licm: Abrt in llvm::Expected >::fatalUncheckedExpecte
Updates: Labels: Deadline-Approaching Comment #1 on issue 15520 by sheriff...@chromium.org: llvm/llvm-opt-fuzzer--x86_64-licm: Abrt in llvm::Expected ::fatalUncheckedExpecte https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15520#c1 This bug is approaching its deadline for being fixed, and will be automatically derestricted within 7 days. If a fix is planned within 2 weeks after the deadline has passed, a grace extension can be granted. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43361] New: Suboptimal codegen for binary search
https://bugs.llvm.org/show_bug.cgi?id=43361
Bug ID: 43361
Summary: Suboptimal codegen for binary search
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
Created attachment 22529
--> https://bugs.llvm.org/attachment.cgi?id=22529&action=edit
microbenchmark
Consider
int bs(int a[], int low, int high, int find)
{
int middle;
while( low <= high )
{
middle = ( low + high ) / 2;
if ( find == a[middle])
return middle;
else if ( find < a[middle])
high = middle - 1;
else
// Variant2:
// else if ( find > a[middle])
low = middle + 1;
}
return -1;
}
bs(int*, int, int, int): # @bs(int*, int, int, int)
mov eax, -1
cmp esi, edx
jle .LBB0_2
.LBB0_4:
ret
.LBB0_7:# in Loop: Header=BB0_2 Depth=1
add r8d, 1
mov esi, r8d
cmp esi, edx
jg .LBB0_4
.LBB0_2:# =>This Inner Loop Header: Depth=1
lea r9d, [rsi + rdx]
mov r8d, r9d
shr r8d, 31
add r8d, r9d
sar r8d
movsxd r9, r8d
mov r9d, dword ptr [rdi + 4*r9]
cmp r9d, ecx
je .LBB0_3
cmp r9d, ecx
jle .LBB0_7
add r8d, -1
mov edx, r8d
cmp esi, edx
jle .LBB0_2
jmp .LBB0_4
.LBB0_3:
mov eax, r8d
ret
1) why jmp .LBB0_4? just "ret" ?
2) this codegen looks very supoptimal
cmp r9d, ecx
je .LBB0_3
cmp r9d, ecx
jle .LBB0_7
gcc9 -O3
time ./a.out
Element is present at index 3
real0m0,226s
user0m0,221s
sys 0m0,005s
clang trunk -O3
time ./a.out
Element is present at index 3
real0m0,290s
user0m0,286s
sys 0m0,005s
clang trunk -O3 Variant 2 (codegen is full of cmovs)
time ./a.out
Element is present at index 3
real0m0,732s
user0m0,728s
sys 0m0,004s
-mllvm -phi-node-folding-threshold=1 - No changes in perf.
-mllvm -phi-node-folding-threshold=0 - No cmovs, better perf:
time ./a.out
Element is present at index 3
real0m0,293s
user0m0,289s
sys 0m0,004s
Tested on Intel Haswell
--
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 4575 in oss-fuzz: llvm/clang-fuzzer: ASSERT: DD && "queried property of class with no definition"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #16 on issue 4575 by ClusterFuzz-External: llvm/clang-fuzzer: ASSERT: DD && "queried property of class with no definition" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4575#c16 ClusterFuzz testcase 5106944990773248 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201909180332:201909190331 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 6157 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-gvn: ASSERT: !isa(TI) && "Cannot split critical edge from IndirectBrInst"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #11 on issue 6157 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-gvn: ASSERT: !isa(TI) && "Cannot split critical edge from IndirectBrInst" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6157#c11 ClusterFuzz testcase 4975040933134336 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201909180332:201909190331 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 3169 in oss-fuzz: llvm: ASSERT: RHS.U.VAL != 0 && "Divide by zero?"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #21 on issue 3169 by ClusterFuzz-External: llvm: ASSERT: RHS.U.VAL != 0 && "Divide by zero?" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3169#c21 ClusterFuzz testcase 4964641463599104 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201909180332:201909190331 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 17492 in oss-fuzz: llvm:clangd-fuzzer: Timeout in clangd-fuzzer
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 Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2019-09-19 Type: Bug New issue 17492 by ClusterFuzz-External: llvm:clangd-fuzzer: Timeout in clangd-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=17492 Detailed Report: https://oss-fuzz.com/testcase?key=5663380743913472 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clangd-fuzzer Job Type: libfuzzer_msan_llvm Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: clangd-fuzzer Sanitizer: memory (MSAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_msan_llvm&range=201906280305:201906290306 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5663380743913472 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 41221] [meta] 8.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=41221 Nico Weber changed: What|Removed |Added CC||nicolaswe...@gmx.de 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 39106] [meta] 7.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=39106 Nico Weber changed: What|Removed |Added Status|NEW |RESOLVED CC||nicolaswe...@gmx.de 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 42474] [meta] 9.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=42474 Hans Wennborg changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #21 from Hans Wennborg --- The -final tag is in. 9.0.1 blockers are tracked by https://bugs.llvm.org/show_bug.cgi?id=43360 -- 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 36649] [meta] 6.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=36649 Nico Weber changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED CC||nicolaswe...@gmx.de -- 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 43360] New: [meta] 9.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=43360 Bug ID: 43360 Summary: [meta] 9.0.1 Release Blockers Product: new-bugs Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: nicolaswe...@gmx.de CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org Tracking bug for 9.0.1. -- 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 43359] New: [AMDGPU][MC] Relocatable expressions are not counted as literals
https://bugs.llvm.org/show_bug.cgi?id=43359 Bug ID: 43359 Summary: [AMDGPU][MC] Relocatable expressions are not counted as literals Product: libraries Version: trunk Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: Backend: AMDGPU Assignee: unassignedb...@nondot.org Reporter: dpreobrazhen...@luxoft.com CC: llvm-bugs@lists.llvm.org Relocatable expressions may be used as operands; however they are not accounted for when computing the total number of literals used by an instruction. Examples: // All GPUs s_sub_u32 s0, 123, 123 // ok s_sub_u32 s0, 123, 456 // error s_sub_u32 s0, 123, x // ok, but should trigger an error // GFX10 v_bfe_u32 v0, v1, 123, 123 // ok v_bfe_u32 v0, v1, 123, 456 // error v_bfe_u32 v0, v1, 123, x// ok, but should trigger an error // GFX9 v_bfe_u32 v0, v2, v3, v4 // ok v_bfe_u32 v0, v2, v3, 123 // error v_bfe_u32 v0, v2, v3, x // breaks assembler (should trigger an error) -- 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 43279] Add llvm-reduce component to bugzilla
https://bugs.llvm.org/show_bug.cgi?id=43279 Kristof Beyls changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED CC||kristof.be...@arm.com --- Comment #4 from Kristof Beyls --- (In reply to David Blaikie from comment #3) > Yeah, I watch all the bugs anyway - but having me as a default-CC on > llvm-reduce bugs sounds good - thanks! Thanks David, I just added you to the default-CC for llvm-reduce. -- 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 17483 in oss-fuzz: llvm:clang-fuzzer: Timeout in clang-fuzzer
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 Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2019-09-19 Type: Bug New issue 17483 by ClusterFuzz-External: llvm:clang-fuzzer: Timeout in clang-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=17483 Detailed Report: https://oss-fuzz.com/testcase?key=5649598428741632 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: clang-fuzzer Sanitizer: address (ASAN) Crash Revision: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&revision=201909180332 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5649598428741632 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 22749] Internal compiler Cannot select FMADD
https://bugs.llvm.org/show_bug.cgi?id=22749 Sanjay Patel changed: What|Removed |Added Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #2 from Sanjay Patel --- (In reply to Craig Topper from comment #1) > There are no attachments. And its quite old. Can we close this? I don't see how we can do anything with this report as-is. Feel free to reopen with repro steps/attachments if there's still a 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] Issue 17477 in oss-fuzz: llvm:llvm-opt-fuzzer--x86_64-guard_widening: Out-of-memory in llvm-opt-fuzzer--x86_64-guard_widening
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 Reproducible Stability-Memory-MemorySanitizer Engine-libfuzzer OS-Linux Proj-llvm Reported-2019-09-19 Type: Bug New issue 17477 by ClusterFuzz-External: llvm:llvm-opt-fuzzer--x86_64-guard_widening: Out-of-memory in llvm-opt-fuzzer--x86_64-guard_widening https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=17477 Detailed Report: https://oss-fuzz.com/testcase?key=5690663382810624 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: llvm-opt-fuzzer--x86_64-guard_widening Job Type: libfuzzer_msan_llvm Platform Id: linux Crash Type: Out-of-memory (exceeds 2048 MB) Crash Address: Crash State: llvm-opt-fuzzer--x86_64-guard_widening Sanitizer: memory (MSAN) Crash Revision: https://oss-fuzz.com/revisions?job=libfuzzer_msan_llvm&revision=201906300300 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5690663382810624 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 43358] New: c++ parser crash on invalid code
https://bugs.llvm.org/show_bug.cgi?id=43358
Bug ID: 43358
Summary: c++ parser crash on invalid code
Product: clang
Version: 8.0
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: C++11
Assignee: unassignedclangb...@nondot.org
Reporter: emmanuel.th...@inria.fr
CC: blitzrak...@gmail.com, dgre...@apple.com,
erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org,
richard-l...@metafoo.co.uk
Created attachment 22526
--> https://bugs.llvm.org/attachment.cgi?id=22526&action=edit
complete source code
clang++ 8.0.1-3+b1 encounters a c++ crash on the attached code. I acknowledge
the fact that the code is invalid, but a parser crash should not occur.
Test source file, output, and reproducer attached.
template
struct pool {
bool ok() const { return happy; }
template struct proxy {
bool ok() { return T::f.ok(); }
};
};
template class obj {
typedef pool pool_t;
static pool_t f;
public:
typedef typename pool_t::template proxy proxy_t;
template<> friend struct pool_t::proxy; // ***parser crash***
};
extern template class obj;
int main()
{
obj::proxy_t dummy;
return dummy.ok();
}
Here's a small bit of the full stack trace
#4 0x016e777e
clang::Sema::MatchTemplateParametersToScopeSpecifier(clang::SourceLocation,
clang::SourceLocation, clang::CXXScopeSpec const&,
clang::TemplateIdAnnotation*,
llvm::ArrayRef, bool, bool&, bool&)
(/usr/lib/llvm-8/bin/clang+0x16e777e)
#5 0x016fb471
clang::Sema::ActOnClassTemplateSpecialization(clang::Scope*, unsigned
int, clang::Sema::TagUseKind, clang::SourceLocation, clang::SourceLocation,
clang::TemplateIdAnnotation&, clang::ParsedAttributesView const&,
llvm::MutableArrayRef,
clang::Sema::SkipBodyInfo*)
(/usr/lib/llvm-8/bin/clang+0x16fb471)
--
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 17461 in oss-fuzz: llvm:llvm-isel-fuzzer--wasm32-O2: Timeout in llvm-isel-fuzzer--wasm32-O2
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 Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2019-09-19 Type: Bug New issue 17461 by ClusterFuzz-External: llvm:llvm-isel-fuzzer--wasm32-O2: Timeout in llvm-isel-fuzzer--wasm32-O2 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=17461 Detailed Report: https://oss-fuzz.com/testcase?key=5645320205107200 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: llvm-isel-fuzzer--wasm32-O2 Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: llvm-isel-fuzzer--wasm32-O2 Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201903130407:201903140334 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5645320205107200 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 43357] New: [NEWGVN] Assertion `BeforeCC->isEquivalentTo(AfterCC) && "Value number changed after main loop completed!"' failed.
https://bugs.llvm.org/show_bug.cgi?id=43357 Bug ID: 43357 Summary: [NEWGVN] Assertion `BeforeCC->isEquivalentTo(AfterCC) && "Value number changed after main loop completed!"' failed. Product: libraries Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: Register Allocator Assignee: unassignedb...@nondot.org Reporter: david.bolvan...@gmail.com CC: llvm-bugs@lists.llvm.org, quentin.colom...@gmail.com Created attachment 22525 --> https://bugs.llvm.org/attachment.cgi?id=22525&action=edit Newgvn crash See attached file (it is a part of the zstd). -- 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 17443 in oss-fuzz: llvm:llvm-dwarfdump-fuzzer: Out-of-memory in llvm-dwarfdump-fuzzer
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 OS-Linux Proj-llvm Reported-2019-09-19 Type: Bug New issue 17443 by ClusterFuzz-External: llvm:llvm-dwarfdump-fuzzer: Out-of-memory in llvm-dwarfdump-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=17443 Detailed Report: https://oss-fuzz.com/testcase?key=5100960413646848 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: llvm-dwarfdump-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Out-of-memory (exceeds 2048 MB) Crash Address: Crash State: llvm-dwarfdump-fuzzer Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201804130530:201804140527 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5100960413646848 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
