[llvm-bugs] [Bug 39779] -Wunsequenced warning on OR operator
https://bugs.llvm.org/show_bug.cgi?id=39779 Bruno Ricci changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Bruno Ricci --- Committed in 8a571538dff6dbc1b7f4fed6aed8be7ec1a00a8d -- 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 43052] -Wsequence-point misses some cases; also produces false positives for C++17
https://bugs.llvm.org/show_bug.cgi?id=43052 Bruno Ricci changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Bruno Ricci --- I am marking this as resolved fixed. The first example was actually ok, and the second example now triggers a warning after 7394c15178ed9cb7bd04585526a1e73396e60e17 in pre-C++17 modes. -- 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 22197] False warning: unsequenced modification and access to
https://bugs.llvm.org/show_bug.cgi?id=22197 Bruno Ricci changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #2 from Bruno Ricci --- Fixed by 8a571538dff6dbc1b7f4fed6aed8be7ec1a00a8d. (note that for the record, the term "sequence point" is a term which applies to C and pre-C++11 C++, modern C++ defines the sequencing relation as a partial order) -- 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 44111] error in backend: Cannot emit physreg copy instruction, after _mm_hadd_pd
https://bugs.llvm.org/show_bug.cgi?id=44111 Sanjay Patel changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #5 from Sanjay Patel --- Confirmed that this is a duplicate. *** This bug has been marked as a duplicate of bug 43402 *** -- 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 44272] [CLANG-CL] 64x inline assembler function call/jump miscompiled
https://bugs.llvm.org/show_bug.cgi?id=44272 Eric Astor changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Fixed By Commit(s)||dc5b614fa9a1 -- 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 19631 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in GetDiagInfo
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #1 on issue 19631 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in GetDiagInfo https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19631#c1 ClusterFuzz testcase 5700296722612224 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201912200437:201912220428 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 19315 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::StmtVisitorBase::Visit
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #1 on issue 19315 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::StmtVisitorBaseComplexExprEvaluator, bool>::Visit https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19315#c1 ClusterFuzz testcase 5831514587922432 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201912200437:201912220428 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 19628 in oss-fuzz: llvm:llvm-opt-fuzzer--x86_64-instcombine: Timeout in llvm-opt-fuzzer--x86_64-instcombine
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #1 on issue 19628 by ClusterFuzz-External: llvm:llvm-opt-fuzzer--x86_64-instcombine: Timeout in llvm-opt-fuzzer--x86_64-instcombine https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19628#c1 ClusterFuzz testcase 5134770543788032 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201912200437:201912220428 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 44363] New: Segmentation fault when expanding C++ 11 template
https://bugs.llvm.org/show_bug.cgi?id=44363
Bug ID: 44363
Summary: Segmentation fault when expanding C++ 11 template
Product: clang
Version: 8.0
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Priority: P
Component: C++14
Assignee: unassignedclangb...@nondot.org
Reporter: evandroc...@hotmail.com
CC: blitzrak...@gmail.com, erik.pilking...@gmail.com,
llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk
I was just building some simple template code and the clang compiler crashed.
It crashes both with clang 5 (windows release) and 8 (cygwin release).
This is the command line output from clang 5 and 8, plus the source code:
Professional@PROFESSIONAL-PC$ whereis clang
clang: /usr/bin/clang /usr/lib/clang /cygdrive/c/Program
Files/LLVM/bin/clang.exe /usr/share/man/man1/clang.1.gz
$ clang++ -Xclang -ast-print -fsyntax-only test_debugger.cpp > main.exe
clang-8: error: unable to execute command: Segmentation fault (core dumped)
clang-8: error: clang frontend command failed due to signal (use -v to see
invocation)
clang version 8.0.1 (tags/RELEASE_801/final)
Target: x86_64-unknown-windows-cygnus
Thread model: posix
InstalledDir: /usr/bin
clang-8: note: diagnostic msg: PLEASE submit a bug report to and include the
crash backtrace, preprocessed source, and associated run script.
clang-8: error: unable to execute command: Segmentation fault (core dumped)
clang-8: note: diagnostic msg: Error generating preprocessed source(s).
$ /cygdrive/c/Program\ Files/LLVM/bin/clang.exe -Xclang -ast-print
-fsyntax-only test_debugger.cpp > main.exe
Wrote crash dump file
"C:\Users\PROFES~1\AppData\Local\Temp\clang.exe-2c8cc4.dmp"
clang.exe: error: clang frontend command failed due to signal (use -v to see
invocation)
clang version 5.0.1 (tags/RELEASE_501/final)
Target: x86_64-pc-windows-msvc
Thread model: posix
InstalledDir: C:\Program Files\LLVM\bin
clang.exe: note: diagnostic msg: PLEASE submit a bug report to
http://llvm.org/bugs/ and include the crash backtrace, preprocessed source, and
associated run script.
clang.exe: note: diagnostic msg: Error generating preprocessed source(s).
Source code:
#include
#define STATIC_ASSERT(...) static_assert(__VA_ARGS__, #__VA_ARGS__)
template< unsigned int PathIndex, unsigned int PathLength >
constexpr unsigned int findlastslash(const char (&path)[PathLength])
{
constexpr const unsigned int end = PathLength - PathIndex;
return (end >= 0 && path[end] != '/' && path[end] != '\\') ? findlastslash<
PathIndex - 1 >( path ) : ( end + 1 );
}
int main(int argc, char const *argv[])
{
STATIC_ASSERT( findlastslash< 1 >( "cppdebugger/test_debugger.cpp" ) == 17
);
}
--
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 19666 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in IntExprEvaluator::VisitBinaryOperator
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, d...@google.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-12-23 Type: Bug New issue 19666 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in IntExprEvaluator::VisitBinaryOperator https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19666 Detailed Report: https://oss-fuzz.com/testcase?key=5660131463528448 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffe3c7cf9c0 Crash State: IntExprEvaluator::VisitBinaryOperator clang::StmtVisitorBasebool>::Visit IntExprEvaluator::VisitCastExpr Sanitizer: address (ASAN) Crash Revision: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&revision=201912220428 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5660131463528448 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 44365] New: -Wpragma-once-outside-header warns in a modular header unit
https://bugs.llvm.org/show_bug.cgi?id=44365 Bug ID: 44365 Summary: -Wpragma-once-outside-header warns in a modular header unit Product: clang Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: -New Bugs Assignee: unassignedclangb...@nondot.org Reporter: da...@doublewise.net CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org, neeil...@live.com, richard-l...@metafoo.co.uk When compiling a header unit consisting of #pragma once and passing the flag -Wpragma-once-outside-header, clang emits a warning. It should not emit a warning -- header units can still be included like normal. -- 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 19668 in oss-fuzz: llvm:llvm-itanium-demangle-fuzzer: Stack-overflow in llvm::itanium_demangle::NestedName::printLeft
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, d...@google.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-12-23 Type: Bug New issue 19668 by ClusterFuzz-External: llvm:llvm-itanium-demangle-fuzzer: Stack-overflow in llvm::itanium_demangle::NestedName::printLeft https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19668 Detailed Report: https://oss-fuzz.com/testcase?key=5702813841883136 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: llvm-itanium-demangle-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffc2781bff8 Crash State: llvm::itanium_demangle::NestedName::printLeft 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=5702813841883136 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 44366] New: Error when compiling large `if` blocks on riscv64-linux-gnu
https://bugs.llvm.org/show_bug.cgi?id=44366
Bug ID: 44366
Summary: Error when compiling large `if` blocks on
riscv64-linux-gnu
Product: clang
Version: 9.0
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P
Component: LLVM Codegen
Assignee: unassignedclangb...@nondot.org
Reporter: adrien.sf...@gmail.com
CC: llvm-bugs@lists.llvm.org, neeil...@live.com,
richard-l...@metafoo.co.uk
When compiling a program to riscv64-linux-gnu target with large "if" blocks
(which compiles to at least 2^19 bytes of code to make the jump an indirect
branch), clang gives the following error:
error in backend: Unable to insert indirect branch
It seems like a issue on PIE generation, since compiling with --target=riscv64
is successful.
The following is an example source:
int a(int c) {
if (c < 12345) {
#define A \
{ int d = c % 12345; int e = c ^ d * 12345; \
int f = c * d % e % 12345; c = f; }
#define B A A A A A A
#define C B B B B B B
#define D C C C C C C
#define E D D D D D D
E E E E E
}
return c;
}
One can reproduce the error by compiling the source with
clang -O0 --target=riscv64-linux-gnu -c
--
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 44367] New: private clause not working in offload
https://bugs.llvm.org/show_bug.cgi?id=44367 Bug ID: 44367 Summary: private clause not working in offload Product: OpenMP Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: Clang Compiler Support Assignee: unassignedclangb...@nondot.org Reporter: xw111lu...@gmail.com CC: llvm-bugs@lists.llvm.org The private clause in target seems all broken. I got all identical addresses of the variable marked private. https://github.com/ye-luo/openmp-target/blob/master/hands-on/tests/private/target_teams_distribute_private.c https://github.com/ye-luo/openmp-target/blob/master/hands-on/tests/private/target_teams_distribute_parallel_for_private.c I found this broken in all the clang derived offload compilers. GCC works fine. With private(a) on "teams distribute" and "parallel for", per-team and per-thread copy of a should be created. So all the address should be different. -- 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
