[llvm-bugs] [Bug 41389] clang-tidy with EnumCastOutOfRange crashes with Assertion `op == BO_Add' failed.
https://bugs.llvm.org/show_bug.cgi?id=41389 Mikael Holmén changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Mikael Holmén --- Apparently I managed to create two identical PRs so closing this as duplicate. *** This bug has been marked as a duplicate of bug 41388 *** -- 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 41390] New: _FORTIFY_SOURCE and optimization(like -O1, -O2, etc.) prevents CUDA compilation
https://bugs.llvm.org/show_bug.cgi?id=41390
Bug ID: 41390
Summary: _FORTIFY_SOURCE and optimization(like -O1, -O2, etc.)
prevents CUDA compilation
Product: clang
Version: trunk
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: CUDA
Assignee: unassignedclangb...@nondot.org
Reporter: kazukuro0...@gmail.com
CC: llvm-bugs@lists.llvm.org
#include
int main()
{
printf("test\n");
}
This code can't be compiled when you run Clang like below:
$ clang -x cuda -O2 -D_FORTIFY_SOURCE=1 -c test.cu.cc
That's because string_fortified.h, included from string.h, tries to re-declare
some built-in functions. (See also
https://sourceware.org/git/?p=glibc.git;a=blob;f=string/string.h;h=c38eea971f4396c678598f51602082318ec5349d;hb=HEAD#l494)
So, I think __clang_cuda_runtime_wrapper.h:216 should be reconsidered.
For example:
#include
to
#if defined(__fortify_function)
#define __tmp_value __fortify_function
#undef __fortify_function
#include
#define __fortify_function __tmp_value
#undef __tmp_value
#else
#include
#endif
--
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 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 Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #8 from Hans Wennborg --- My patch was reverted in https://llvm.org/r357667 I'm working on figuring out what went wrong and fixing it. -- 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 41391] New: "Function marked read-only and write-only" assertion at -O1
https://bugs.llvm.org/show_bug.cgi?id=41391
Bug ID: 41391
Summary: "Function marked read-only and write-only" assertion
at -O1
Product: libraries
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: Interprocedural Optimizations
Assignee: unassignedb...@nondot.org
Reporter: luke@intel.com
CC: llvm-bugs@lists.llvm.org
Using clang to compile the following C code at -O1:
```
int i = 0;
void foo();
void bar() { if (!i) foo(); }
void foo() { i = 1; bar(); }
```
> clang -O1 test.c
... clang-8: llvm-project/llvm/lib/Transforms/IPO/FunctionAttrs.cpp:263: bool
addReadAttrs(const (anonymous namespace)::SCCNodeSet &, AARGetterT &&)
[AARGetterT = llvm::LegacyAARGetter &]: Assertion `!(ReadsMemory &&
WritesMemory) && "Function marked read-only and write-only"' failed.
> clang -v
clang version 9.0.0 (https://github.com/llvm/llvm-project.git
31e4fec3c021b21eae8cb7b26691632716c1e3cc)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /home/luke/Source/llvm-project/build/./bin
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/6
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/6.3.0
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/7
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/7.4.0
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/8
Selected GCC installation: /usr/lib/gcc/x86_64-linux-gnu/8
Candidate multilib: .;@m64
Selected multilib: .;@m64
--
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 41392] New: clang crashes when the offset asm instruction uses a function pointer as argument
https://bugs.llvm.org/show_bug.cgi?id=41392
Bug ID: 41392
Summary: clang crashes when the offset asm instruction uses a
function pointer as argument
Product: clang
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: C++
Assignee: unassignedclangb...@nondot.org
Reporter: zahira.ammarguel...@intel.com
CC: blitzrak...@gmail.com, dgre...@apple.com,
erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org,
richard-l...@metafoo.co.uk
This simple test case:
void (*foo)();
void goo()
{
{
__asm push offset foo
};
}
crashes compiled as C or C++. With and without -m32 option.
https://gcc.godbolt.org/z/PLTAJx
--
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 41394] New: Clang_cl precompiled headers causes missing symbols
https://bugs.llvm.org/show_bug.cgi?id=41394 Bug ID: 41394 Summary: Clang_cl precompiled headers causes missing symbols Product: clang Version: 8.0 Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: Driver Assignee: unassignedclangb...@nondot.org Reporter: li...@carewolf.com CC: llvm-bugs@lists.llvm.org, neeil...@live.com, richard-l...@metafoo.co.uk With the latest clang_cl 8.0 we have tried reenabling using precompiled headers for clang_cl on Windows with Qt. Unfortunately it doesn't work and causes very long list of undefined symbols at link time. All the missing symbols reported as referenced from PCH object file. The symbols can be both from in and outside of the library, almost all inline templated methods such as various forms of basic_string methods. There are several ways to work around the issue, most avoiding linking with PCH object file: 1) Not linking in the pch object file and doing a debug build 2) Not linking in the pch object file and compiling all other files with /Zc:dllexportInlines- 3) Not linking in the pch object file and compiling all other files with -Xclang -building-pch-with-obj 4) Manually instantiating ALL templated classes possibly used by inline methods (e.g. template class std::basic_string). Note this is not necessary with any other compiler. They first three work-arounds all achieve the same goal of making the methods generated in the PCH object file redundant, making linking with the buggy object file unnecessary. The issue simply appears to be that templated inline methods are partially generated, but the template instantiations they need are not. Likely the generated methods should been discarded unless used by another file in the library. In general it seems the far easiest to use a similar strategy as on non-windows platform and let the normal object files generate the inline symbols they need, even if that generates them more than necessary. I have tried making a few simple cases, but the issue resists reproduction with small examples and appears to require a larger library before it triggers. Tell me if you need more information. -- 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 41276] Invalid address space cast in C++17 mode (CastConsistency assertion failure)
https://bugs.llvm.org/show_bug.cgi?id=41276 Anastasia Stulova changed: What|Removed |Added Resolution|--- |FIXED 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] [Bug 41395] New: __cxa_vec_new overflow the allocation size.
https://bugs.llvm.org/show_bug.cgi?id=41395 Bug ID: 41395 Summary: __cxa_vec_new overflow the allocation size. Product: libc++abi Version: 7.0 Hardware: PC OS: All Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: unassignedb...@nondot.org Reporter: e...@efcs.ca CC: llvm-bugs@lists.llvm.org, mclow.li...@gmail.com Created attachment 21737 --> https://bugs.llvm.org/attachment.cgi?id=21737&action=edit libstdcxx_test.cpp __cxa_vec_new overflows during the calculation of the allocation size. It should throw bad alloc instead. Attached is the libstdc++ test case that caught this. -- 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 41396] New: libc++abi should report forced unwinding on thread termination.
https://bugs.llvm.org/show_bug.cgi?id=41396
Bug ID: 41396
Summary: libc++abi should report forced unwinding on thread
termination.
Product: libc++abi
Version: 7.0
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P
Component: All Bugs
Assignee: unassignedb...@nondot.org
Reporter: e...@efcs.ca
CC: llvm-bugs@lists.llvm.org, mclow.li...@gmail.com
libstdc++ throws an exception when forced unwinding occurs, for example by a
call to pthread_exit.
This allows the library to detect and avoid certain classes of bugs. For
example, libc++ hangs forever on this test, libstdc++ reports the promise as
broken.
#include
#include
#include
#include
void f() { pthread_exit(nullptr); }
int main()
{
auto fut = std::async(std::launch::async, f);
try
{
fut.get();
throw std::logic_error("Unreachable");
}
catch (const std::future_error& e)
{
assert( e.code() == std::future_errc::broken_promise );
}
}
--
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 38811] Clang fails to compile with CUDA-9.x on Windows.
https://bugs.llvm.org/show_bug.cgi?id=38811 Evgeny Mankov changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #10 from Evgeny Mankov --- The last compilation error was eliminated with the fix "[CUDA][Windows] Final fix for bug 38811 (Step 3 of 3)": https://reviews.llvm.org/D60220. There were 3 errors, now - 0. The current error log is in the attachment 21738 [details]. -- 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 26299] [meta][X86] Size optimization opportunities (in particular for 32-bit Chromium on Windows)
https://bugs.llvm.org/show_bug.cgi?id=26299 Bug 26299 depends on bug 26302, which changed state. Bug 26302 Summary: [x86] Tail call with conditional jumps https://bugs.llvm.org/show_bug.cgi?id=26302 What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 26302] [x86] Tail call with conditional jumps
https://bugs.llvm.org/show_bug.cgi?id=26302
Nikita Kniazev changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED |---
CC||nok.ra...@gmail.com
--- Comment #4 from Nikita Kniazev ---
This seems to be exactly the issue I was going to open. The following code
contains a tail call while it could just conditionally jump to the function
address:
void bar();
void foo(bool b)
{
if (b) bar();
}
and MSVC does exactly this https://godbolt.org/z/zFv3eb
Moreover, the IR from the first post still does not embed the tail call address
into the conditional jump https://godbolt.org/z/Ehc02G. The expected output in
the test committed with https://reviews.llvm.org/rL295357 is not right, as for
me. Instead of
; WIN64: jne
; WIN64: jmp foo
; WIN64: jmp bar
It has to be:
; WIN64: jne bar
; WIN64: jmp foo
Probably, bug 41261 depends on this.
--
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 41397] New: __cxa_exception doesn't match Itanium spec.
https://bugs.llvm.org/show_bug.cgi?id=41397 Bug ID: 41397 Summary: __cxa_exception doesn't match Itanium spec. Product: libc++abi Version: unspecified Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: unassignedb...@nondot.org Reporter: e...@efcs.ca CC: llvm-bugs@lists.llvm.org, mclow.li...@gmail.com Created attachment 21739 --> https://bugs.llvm.org/attachment.cgi?id=21739&action=edit libstdcxx_test.cpp To support C++11 exception point, we added a ref count member at the start of the `__cxa_exception` type. However, `__cxa_exception` is specified by the Itanium spec and in the specification it doesn't contain the new member. Since `__cxa_exception` is part of the ABI specification, users may declare their own copy of it and then attempt to access in-flight exceptions using `__cxa_get_globals()`. When this occurs the members of the `__cxa_exception` objects are at the wrong offsets and this can break users. GCC's fixs to this problem was to keep `__cxa_exception`'s layout and put the refcount in a new type `__cxa_refcounted_exception` [1]. We should consider doing similar. [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38732 -- 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 41398] New: Greedy spilling of registers before unlikely branch pessimizes likely code path
https://bugs.llvm.org/show_bug.cgi?id=41398
Bug ID: 41398
Summary: Greedy spilling of registers before unlikely branch
pessimizes likely code path
Product: libraries
Version: trunk
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: Register Allocator
Assignee: unassignedb...@nondot.org
Reporter: vgathe...@gmail.com
CC: llvm-bugs@lists.llvm.org, quentin.colom...@gmail.com
Hi, when building the following code with both clang -Os and -O3 on x86_64:
int callme();
int test_function(int a, int b) {
if (__builtin_expect(b < 10, 0)) {
a += callme();
}
return a * b;
}
generates
test_function(int, int):
pushq %rbp
pushq %rbx
pushq %rax
movl%esi, %ebx
movl%edi, %ebp
cmpl$9, %esi
jle .LBB0_1
.LBB0_2:
imull %ebx, %ebp
movl%ebp, %eax
addq$8, %rsp
popq%rbx
popq%rbp
retq
.LBB0_1:
callq callme()
addl%eax, %ebp
jmp .LBB0_2
instead of something like
test_function(int, int):
cmpl$9, %esi
jle .LBB0_1
.LBB0_2:
imull %edi, %esi
movl%esi, %eax
retq
.LBB0_1:
pushq %edi
pushq %esi
callq callme()
popq%esi
popq%edi
addl%eax, %edi
jmp .LBB0_2
While it might be a valid decision to always save to stack if there's a likely
or normal call, this is undesirable behavior when the calling function is
marked as unlikely since branch probably won't get taken and the function
probably won't get called.
As a side note, when compiling with -Os, it would make more sense to just save
esi and edi instead of saving into non-scratch registers and pushing those old
values anyways, both from a code size and stack size perspective. This isn't
really the main point of the bug though.
--
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 41399] New: Redefinition error when declaring multiple template class specializations
https://bugs.llvm.org/show_bug.cgi?id=41399 Bug ID: 41399 Summary: Redefinition error when declaring multiple template class specializations Product: clang Version: 7.0 Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: Frontend Assignee: unassignedclangb...@nondot.org Reporter: egend...@comconcepts.com CC: llvm-bugs@lists.llvm.org, neeil...@live.com, richard-l...@metafoo.co.uk Created attachment 21740 --> https://bugs.llvm.org/attachment.cgi?id=21740&action=edit Minimum code example Clang front end produces a redefinition error when declaring multiple template class specializations using c++17. This issue occurs when using clang 8.0 but I am using clang 7.0 so I figured I would open up the report for 7.0. Clang command to reproduce error: clang -std=c++17 testcase.cpp -- 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 41400] New: Segmentation fault on incorrect using directive
https://bugs.llvm.org/show_bug.cgi?id=41400
Bug ID: 41400
Summary: Segmentation fault on incorrect using directive
Product: clang
Version: 8.0
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: C++
Assignee: unassignedclangb...@nondot.org
Reporter: coil...@yandex.ru
CC: blitzrak...@gmail.com, dgre...@apple.com,
erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org,
richard-l...@metafoo.co.uk
Clang starting from version 7.0.0 (as tested on godbolt) crashes with
segmentation fault when processing the following incorrect code (minimized
input):
template class S { using S
Compiling it with clang 8.0.0:
$ clang++ crash.cpp
gives this stack trace:
Stack dump:
0. Program arguments: /usr/local/clang-8.0.0/bin/clang-8 -cc1 -triple
x86_64-unknown-linux-gnu -emit-obj -mrelax-all -disable-free
-disable-llvm-verifier -discard-value-names -main-file-name crash.cpp
-mrelocation-model static -mthread-model posix -mdisable-fp-elim -fmath-errno
-masm-verbose -mconstructor-aliases -munwind-tables -fuse-init-array
-target-cpu x86-64 -dwarf-column-info -debugger-tuning=gdb -resource-dir
/usr/local/clang-8.0.0/lib/clang/8.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/include -internal-isystem
/usr/local/clang-8.0.0/lib/clang/8.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 /home/mygrain/compiler_research/Templates -ferror-limit
19 -fmessage-length 212 -fobjc-runtime=gcc -fcxx-exceptions -fexceptions
-fdiagnostics-show-option -fcolor-diagnostics -o /tmp/crash-276b5d.o -x c++
crash.cpp -faddrsig
1. parser at end of file
2. crash.cpp:1:17: parsing struct/union/class body 'S'
#0 0x015d8e5a llvm::sys::PrintStackTrace(llvm::raw_ostream&)
(/usr/local/clang-8.0.0/bin/clang-8+0x15d8e5a)
#1 0x015d6dec llvm::sys::RunSignalHandlers()
(/usr/local/clang-8.0.0/bin/clang-8+0x15d6dec)
#2 0x015d6f57 SignalHandler(int)
(/usr/local/clang-8.0.0/bin/clang-8+0x15d6f57)
#3 0x7f4e1d2af390 __restore_rt
(/lib/x86_64-linux-gnu/libpthread.so.0+0x11390)
#4 0x031631c0 clang::NestedNameSpecifier::getKind() const
(/usr/local/clang-8.0.0/bin/clang-8+0x31631c0)
#5 0x03163966
clang::NestedNameSpecifier::containsUnexpandedParameterPack() const
(/usr/local/clang-8.0.0/bin/clang-8+0x3163966)
#6 0x02fcf3e4
clang::ASTContext::getDependentNameType(clang::ElaboratedTypeKeyword,
clang::NestedNameSpecifier*, clang::IdentifierInfo const*, clang::QualType)
const (/usr/local/clang-8.0.0/bin/clang-8+0x2fcf3e4)
#7 0x02c56885 clang::Sema::getConstructorName(clang::IdentifierInfo&,
clang::SourceLocation, clang::Scope*, clang::CXXScopeSpec&, bool)
(/usr/local/clang-8.0.0/bin/clang-8+0x2c56885)
#8 0x0295ff13 clang::Parser::ParseUnqualifiedId(clang::CXXScopeSpec&,
bool, bool, bool, bool, clang::OpaquePtr,
clang::SourceLocation*, clang::UnqualifiedId&)
(/usr/local/clang-8.0.0/bin/clang-8+0x295ff13)
#9 0x02935e01
clang::Parser::ParseUsingDeclarator(clang::DeclaratorContext,
clang::Parser::UsingDeclarator&) (/usr/local/clang-8.0.0/bin/clang-8+0x2935e01)
#10 0x02941e82
clang::Parser::ParseUsingDeclaration(clang::DeclaratorContext,
clang::Parser::ParsedTemplateInfo const&, clang::SourceLocation,
clang::SourceLocation&, clang::AccessSpecifier)
(/usr/local/clang-8.0.0/bin/clang-8+0x2941e82)
#11 0x02943c4b
clang::Parser::ParseCXXClassMemberDeclaration(clang::AccessSpecifier,
clang::ParsedAttributes&, clang::Parser::ParsedTemplateInfo const&,
clang::ParsingDeclRAIIObject*) (/usr/local/clang-8.0.0/bin/clang-8+0x2943c4b)
#12 0x029454b5
clang::Parser::ParseCXXClassMemberDeclarationWithPragmas(clang::AccessSpecifier&,
clang::Parser::ParsedAttributesWithRange&, clang::TypeSpecifierType,
clang::Decl*) (/usr/local/clang-8.0.0/bin/clang-8+0x29454b5)
#13 0x02945ddf
clang::Parser::ParseCXXMemberSpecification(clang::SourceLocation,
clang::SourceLocation, clang::Parser::ParsedAttributesWithRange&, unsigned int,
clang::Decl*) (/usr/local/clang-8.0.0/bin/clang-8+0x2945ddf)
#14 0x0294837b
clang::Parser::ParseClassSpecifier(clang::tok::TokenKind,
clang::SourceLocation, clang::DeclSpec&, clang::Parser::ParsedTemplateInfo
const&, clang::AccessSpecifier, bool, clang::Parser::DeclSpecContext,
clang::Parser::ParsedAttributesWithRange&)
(/usr/local/clang-8.0.0/bin/
[llvm-bugs] [Bug 41395] __cxa_vec_new overflow the allocation size.
https://bugs.llvm.org/show_bug.cgi?id=41395 Eric Fiselier changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #1 from Eric Fiselier --- Fixed in r357814. -- 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 41401] New: Reversion r357618 breaks when ${CMAKE_THREAD_LIBS_INIT} is empty. Probably needs quoting
https://bugs.llvm.org/show_bug.cgi?id=41401
Bug ID: 41401
Summary: Reversion r357618 breaks when
${CMAKE_THREAD_LIBS_INIT} is empty. Probably needs
quoting
Product: OpenMP
Version: unspecified
Hardware: Macintosh
OS: MacOS X
Status: NEW
Severity: normal
Priority: P
Component: Clang Compiler Support
Assignee: unassignedclangb...@nondot.org
Reporter: daphnedi...@mac.com
CC: llvm-bugs@lists.llvm.org
I get the following error running cmake:
-- sanitizer_common tests on "Darwin" will run against "asan;lsan;tsan;ubsan"
CMake Error at openmp/cmake/OpenMPTesting.cmake:126 (if):
if given arguments:
"STREQUAL" "-lpthread"
Unknown arguments specified
Call Stack (most recent call first):
openmp/CMakeLists.txt:49 (include)
I believe it is because of missing quotes around ${CMAKE_THREAD_LIBS_INIT}
--
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 41402] New: aarch64 doesn't allow pointer to static struct for "i" constrain of inline assembly
https://bugs.llvm.org/show_bug.cgi?id=41402 Bug ID: 41402 Summary: aarch64 doesn't allow pointer to static struct for "i" constrain of inline assembly Product: clang Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: Frontend Assignee: unassignedclangb...@nondot.org Reporter: ndesaulni...@google.com CC: isanb...@gmail.com, jykni...@google.com, kristof.be...@arm.com, llvm-bugs@lists.llvm.org, neeil...@live.com, richard-l...@metafoo.co.uk, srhi...@google.com Blocks: 4068 Created attachment 21741 --> https://bugs.llvm.org/attachment.cgi?id=21741&action=edit arm64_i.c See attached test case. It seems that x86_64 allows the input argument to an extended inline asm block to be a pointer to a static struct, but aarch64 does not. This pattern is used in the Linux kernel (as part of the static_key runtime patching) and without support blocks landing asm goto support Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=4068 [Bug 4068] [Meta] Compiling the Linux kernel with clang -- 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 41403] New: Stack unnecessarily used when unrolling loops on statically-sized local arrays
https://bugs.llvm.org/show_bug.cgi?id=41403
Bug ID: 41403
Summary: Stack unnecessarily used when unrolling loops on
statically-sized local arrays
Product: libraries
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Register Allocator
Assignee: unassignedb...@nondot.org
Reporter: vgathe...@gmail.com
CC: llvm-bugs@lists.llvm.org, quentin.colom...@gmail.com
Hi,
The following code results in unnecessary stack spills when unrolling the outer
loop:
#define LEN 2
// determines to what extent iteration happens in the inner loop
// (do first operation horizontally, then second horizontally)
// this unrolling of the inner loop results in bad codegen
//
// as opposed to the outer loop
// (do operation 1 on first index, then 2, etc, then go to index 2)
#define INNER_LEN 2
static_assert(LEN % INNER_LEN == 0, "length not divisible by inner width");
void test_loop_width(int *in) {
int inner1[LEN];
for (int j = 0; j < (LEN / INNER_LEN); j++) {
for (int i = 0; i < INNER_LEN; i++) {
inner1[i + j*INNER_LEN] = in[i + j*INNER_LEN];
}
for (int i = 0; i < INNER_LEN; i++) {
in[i + j*INNER_LEN] *= inner1[i + j*INNER_LEN];
}
}
}
Results in the following code getting generated:
test_loop_width(int*):
movq (%rdi), %rax
movq %rax, -8(%rsp)
imull (%rdi), %eax
movl %eax, (%rdi)
movl 4(%rdi), %eax
imull -4(%rsp), %eax
movl %eax, 4(%rdi)
retq
Recompiling this with INNER_LEN set to 1 generates the expected code of
test_loop_width(int*):
movl (%rdi), %eax
movl 4(%rdi), %ecx
imull %eax, %eax
movl %eax, (%rdi)
imull %ecx, %ecx
movl %ecx, 4(%rdi)
retq
The second vertical pattern scales to arbitrary lengths, while the horizontal
pattern uses the stack aggressively.
Ideally, llvm would not be using the stack here and would be able to recognize
that the two are equivalent and code could be reordered to not use the stack.
I don't think this is an aliasing bug since the code vectorizes for larger
lengths in each case, just that the horizontal case still uses the stack.
--
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 41404] New: Provide coverage stack depth tracing instrumentation.
https://bugs.llvm.org/show_bug.cgi?id=41404 Bug ID: 41404 Summary: Provide coverage stack depth tracing instrumentation. Product: compiler-rt Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: hwasan Assignee: unassignedb...@nondot.org Reporter: mitchphill...@outlook.com CC: llvm-bugs@lists.llvm.org "-fsanitize=hwaddress,fuzzer-no-link" (sometimes?) fails to compile on android/linux as __sancov_lowest_stack default instrumentation is missing. -- 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 41405] New: clang-cl incorrectly parses stack size
https://bugs.llvm.org/show_bug.cgi?id=41405 Bug ID: 41405 Summary: clang-cl incorrectly parses stack size Product: clang Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: C++ Assignee: unassignedclangb...@nondot.org Reporter: tiagomacar...@gmail.com CC: blitzrak...@gmail.com, dgre...@apple.com, erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk https://github.com/llvm-mirror/clang/blob/b44a5edecf19653a9fe2467ec719746b63ff9d05/include/clang/Driver/CLCompatOptions.td#L407 Should be: def _SLASH_AI : CLJoinedOrSeparate<"F">; -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 41401] Reversion r357618 breaks when ${CMAKE_THREAD_LIBS_INIT} is empty. Probably needs quoting
https://bugs.llvm.org/show_bug.cgi?id=41401 Dimitry Andric changed: What|Removed |Added CC||dimi...@andric.com, ||hah...@hahnjo.de Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #1 from Dimitry Andric --- Fixed in r357828, sorry for the breakage. -- 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 41369] llvm oss-fuzz build broken
https://bugs.llvm.org/show_bug.cgi?id=41369 Matt Morehouse changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Matt Morehouse --- Latest build succeeded. -- 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 12428 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: ASSERT: !empty()
Comment #6 on issue 12428 by ClusterFuzz-External: llvm/llvm-microsoft-demangle-fuzzer: ASSERT: !empty() https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12428#c6 ClusterFuzz has detected this issue as fixed in range 201903270300:201904052014. Detailed report: https://oss-fuzz.com/testcase?key=5687742816583680 Project: llvm Fuzzer: libFuzzer_llvm_llvm-microsoft-demangle-fuzzer Fuzz target binary: llvm-microsoft-demangle-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: !empty() llvm::ms_demangle::Demangler::demangleFunctionIdentifierCode llvm::ms_demangle::Demangler::parse Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201901070410:201901080410 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201903270300:201904052014 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5687742816583680 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 12428 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: ASSERT: !empty()
Comment #7 on issue 12428 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: ASSERT: !empty() https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12428#c7 Hooray, the fix (https://reviews.llvm.org/rL357647) worked. Can someone close this? -- 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 12432 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: ASSERT: QN->Components->Count >= 2
Comment #6 on issue 12432 by ClusterFuzz-External: llvm/llvm-microsoft-demangle-fuzzer: ASSERT: QN->Components->Count >= 2 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12432#c6 ClusterFuzz has detected this issue as fixed in range 201903270300:201904052014. Detailed report: https://oss-fuzz.com/testcase?key=5754723636871168 Project: llvm Fuzzer: libFuzzer_llvm_llvm-microsoft-demangle-fuzzer Fuzz target binary: llvm-microsoft-demangle-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: QN->Components->Count >= 2 llvm::ms_demangle::Demangler::parse llvm::microsoftDemangle Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201901070410:201901080410 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201903270300:201904052014 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5754723636871168 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 12428 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: ASSERT: !empty()
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #8 on issue 12428 by ClusterFuzz-External: llvm/llvm-microsoft-demangle-fuzzer: ASSERT: !empty() https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12428#c8 ClusterFuzz testcase 5687742816583680 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 12438 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference READ in llvm::microsoftDemangle
Comment #6 on issue 12438 by ClusterFuzz-External: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference READ in llvm::microsoftDemangle https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12438#c6 ClusterFuzz has detected this issue as fixed in range 201903270300:201904052014. Detailed report: https://oss-fuzz.com/testcase?key=5139920006414336 Project: llvm Fuzzer: libFuzzer_llvm_llvm-microsoft-demangle-fuzzer Fuzz target binary: llvm-microsoft-demangle-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x Crash State: llvm::microsoftDemangle llvm-microsoft-demangle-fuzzer.cpp Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201901070410:201901080410 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201903270300:201904052014 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5139920006414336 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 12435 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference READ in llvm::ms_demangle::Demangler::demangleVariableEncoding
Comment #6 on issue 12435 by ClusterFuzz-External: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference READ in llvm::ms_demangle::Demangler::demangleVariableEncoding https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12435#c6 ClusterFuzz has detected this issue as fixed in range 201903270300:201904052014. Detailed report: https://oss-fuzz.com/testcase?key=5678733216710656 Project: llvm Fuzzer: libFuzzer_llvm_llvm-microsoft-demangle-fuzzer Fuzz target binary: llvm-microsoft-demangle-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x0008 Crash State: llvm::ms_demangle::Demangler::demangleVariableEncoding llvm::ms_demangle::Demangler::demangleEncodedSymbol llvm::ms_demangle::Demangler::parse Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201901070410:201901080410 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201903270300:201904052014 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5678733216710656 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 12432 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: ASSERT: QN->Components->Count >= 2
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #7 on issue 12432 by ClusterFuzz-External: llvm/llvm-microsoft-demangle-fuzzer: ASSERT: QN->Components->Count >= 2 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12432#c7 ClusterFuzz testcase 5754723636871168 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 13260 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Out-of-memory in llvm_llvm-microsoft-demangle-fuzzer
Comment #4 on issue 13260 by ClusterFuzz-External: llvm/llvm-microsoft-demangle-fuzzer: Out-of-memory in llvm_llvm-microsoft-demangle-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13260#c4 ClusterFuzz has detected this issue as fixed in range 201903270300:201904052014. Detailed report: https://oss-fuzz.com/testcase?key=5762270670356480 Project: llvm Fuzzer: libFuzzer_llvm_llvm-microsoft-demangle-fuzzer Fuzz target binary: llvm-microsoft-demangle-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Out-of-memory (exceeds 2048 MB) Crash Address: Crash State: llvm_llvm-microsoft-demangle-fuzzer Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201901070410:201901080410 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201903270300:201904052014 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5762270670356480 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 12438 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference READ in llvm::microsoftDemangle
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #7 on issue 12438 by ClusterFuzz-External: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference READ in llvm::microsoftDemangle https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12438#c7 ClusterFuzz testcase 5139920006414336 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] [Bug 41406] New: abs not in
https://bugs.llvm.org/show_bug.cgi?id=41406 Bug ID: 41406 Summary: abs not in Product: libc++ Version: unspecified Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: unassignedclangb...@nondot.org Reporter: z.zoel...@gmail.com CC: llvm-bugs@lists.llvm.org, mclow.li...@gmail.com I think the "cinttypes" header should include the function: std::intmax_t abs( std::intmax_t n ); But it does not. -- 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 12435 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference READ in llvm::ms_demangle::Demangler::demangleVariableEncoding
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #7 on issue 12435 by ClusterFuzz-External: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference READ in llvm::ms_demangle::Demangler::demangleVariableEncoding https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12435#c7 ClusterFuzz testcase 5678733216710656 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 13260 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Out-of-memory in llvm_llvm-microsoft-demangle-fuzzer
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #5 on issue 13260 by ClusterFuzz-External: llvm/llvm-microsoft-demangle-fuzzer: Out-of-memory in llvm_llvm-microsoft-demangle-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13260#c5 ClusterFuzz testcase 5762270670356480 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] [Bug 41406] abs not in
https://bugs.llvm.org/show_bug.cgi?id=41406 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 14083 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: !isa(Shuf.getOperand(1)) && "Not expecting undef shuffle operand wit
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-04-06 Type: Bug New issue 14083 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: !isa(Shuf.getOperand(1)) && "Not expecting undef shuffle operand wit https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14083 Detailed report: https://oss-fuzz.com/testcase?key=5699738642415616 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: !isa(Shuf.getOperand(1)) && "Not expecting undef shuffle operand wit llvm::InstCombiner::visitShuffleVectorInst llvm::InstCombiner::run Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201903270300:201904052014 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5699738642415616 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 41407] New: Constructor initializer list indented incorrectly
https://bugs.llvm.org/show_bug.cgi?id=41407
Bug ID: 41407
Summary: Constructor initializer list indented incorrectly
Product: clang
Version: trunk
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P
Component: Formatter
Assignee: unassignedclangb...@nondot.org
Reporter: owenpi...@gmail.com
CC: djas...@google.com, kli...@google.com,
llvm-bugs@lists.llvm.org
The .clang-format file:
BreakConstructorInitializers: AfterColon
ColumnLimit: 0
ConstructorInitializerIndentWidth: 0
C++ code to be formatted:
Foo::Foo() :
foo(0),
bar(1) {
}
Incorrectly formatted to:
Foo::Foo() :
foo(0),
bar(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] Issue 14084 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference READ in llvm::ms_demangle::ConversionOperatorIdentifierNode::output
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-04-06 Type: Bug New issue 14084 by ClusterFuzz-External: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference READ in llvm::ms_demangle::ConversionOperatorIdentifierNode::output https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14084 Detailed report: https://oss-fuzz.com/testcase?key=5680572032090112 Project: llvm Fuzzer: libFuzzer_llvm_llvm-microsoft-demangle-fuzzer Fuzz target binary: llvm-microsoft-demangle-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x Crash State: llvm::ms_demangle::ConversionOperatorIdentifierNode::output llvm::ms_demangle::NodeArrayNode::output llvm::ms_demangle::VariableSymbolNode::output Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201901070410:201901080410 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5680572032090112 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 41408] New: llvm-objdump cannot disassemble `i32.const 0` in wasm object file.
https://bugs.llvm.org/show_bug.cgi?id=41408 Bug ID: 41408 Summary: llvm-objdump cannot disassemble `i32.const 0` in wasm object file. Product: tools Version: trunk Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: llvm-objdump Assignee: unassignedb...@nondot.org Reporter: higuox...@gmail.com CC: llvm-bugs@lists.llvm.org ``` llvm-objdump -d llvm/test/tools/llvm-objdump/Inputs/trivial.obj.wasm ``` gives: ``` ... ac: 41 00 | i32.const 0 ae: 10 81 80 80 80 00 | call 1 ... ``` ``` wasm-objdump -d llvm/test/tools/llvm-objdump/Inputs/trivial.obj.wasm ``` gives: ``` ... 1a: 00 41 00 1d: 10 81 80 80 80 00 except_ref.call 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
