[llvm-bugs] [Bug 48557] New: Parallel algorithms fail to enforce Mandates: requirements
https://bugs.llvm.org/show_bug.cgi?id=48557
Bug ID: 48557
Summary: Parallel algorithms fail to enforce Mandates:
requirements
Product: parallel STL
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: New
Assignee: ldio...@apple.com
Reporter: zi...@kayari.org
CC: llvm-bugs@lists.llvm.org
For example:
Mandates: All of
— binary_op(init, init),
— binary_op(init, unary_op(*first)),
— binary_op(unary_op(*first), init), and
— binary_op(unary_op(*first), unary_op(*first))
are convertible to T.
This was stated with "Requires:" in C++17, but in C++20 violating the
requirement must be diagnosed.
Example:
#include
#include
int main() {
int a[]{ 1 };
auto r = std::transform_reduce(
std::execution::seq, a, a+1, 0,
[](int& a, int b) {
return a + b;
},
[](int i) { return i; });
}
This compiles without error using GCC's copy of the PSTL code.
--
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 12655 in oss-fuzz: llvm/clang-fuzzer: Abrt in llvm::llvm_unreachable_internal
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #6 on issue 12655 by ClusterFuzz-External: llvm/clang-fuzzer: Abrt in llvm::llvm_unreachable_internal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12655#c6 ClusterFuzz testcase 5669381646843904 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202012180603:202012190620 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 48558] New: using-directive injects names into wrong namespace scope
https://bugs.llvm.org/show_bug.cgi?id=48558
Bug ID: 48558
Summary: using-directive injects names into wrong namespace
scope
Product: clang
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: arthur.j.odw...@gmail.com
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org,
neeil...@live.com, richard-l...@metafoo.co.uk
// https://godbolt.org/z/8bEMfW
struct Cat {};
struct Lion : Cat {};
namespace Outer {
namespace Inner {
namespace N1 {
int foo(Cat);
}
namespace N2 {
int test();
}
}
int foo(Lion);
int Inner::N2::test() {
using namespace Inner::N1;
return (foo)(Lion());
}
}
When Clang sees the using-directive, it seems to insert a declaration of
Outer::Inner::N1::foo(Cat) into the lowest-common-ancestor namespace of Outer
(where the definition of `Inner::N2::test()` appears) and Outer::Inner::N1.
However, it SHOULD insert the declaration into the lowest-common-ancestor
namespace of Outer::Inner::N2 (where the original declaration of `test()`
appeared) and Outer::Inner::N1.
The parens in `(foo)(Lion())` are just there to turn off ADL to simplify the
example; they're not relevant to the 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 28673 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::ASTContext::getTypeInfo
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #1 on issue 28673 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::ASTContext::getTypeInfo https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=28673#c1 ClusterFuzz testcase 5681870947876864 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202012180603:202012190620 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 16077 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: Heap-buffer-overflow in llvm::object::ELFObjectFile
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #3 on issue 16077 by ClusterFuzz-External: llvm/llvm-dwarfdump-fuzzer: Heap-buffer-overflow in llvm::object::ELFObjectFilehttps://bugs.chromium.org/p/oss-fuzz/issues/detail?id=16077#c3 ClusterFuzz testcase 5687643842543616 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202012180603:202012190620 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 28816 in oss-fuzz: llvm:clang-objc-fuzzer: Stack-overflow in GetFullTypeForDeclarator
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevl...@apple.com, igm...@gmail.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2020-12-19 Type: Bug New issue 28816 by ClusterFuzz-External: llvm:clang-objc-fuzzer: Stack-overflow in GetFullTypeForDeclarator https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=28816 Detailed Report: https://oss-fuzz.com/testcase?key=4783075691200512 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-objc-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffe139d58a0 Crash State: GetFullTypeForDeclarator clang::Sema::GetTypeForDeclarator clang::Sema::ActOnBlockArguments Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202011130615:202011140605 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4783075691200512 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 48559] New: Optimizer does not take advantage of `-value == !(value -1)`
https://bugs.llvm.org/show_bug.cgi?id=48559
Bug ID: 48559
Summary: Optimizer does not take advantage of `-value ==
!(value -1)`
Product: libraries
Version: 11.0
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Scalar Optimizations
Assignee: unassignedb...@nondot.org
Reporter: ju.o...@gmail.com
CC: llvm-bugs@lists.llvm.org
Test case:
long f(long align) {
return (align - 1) & -align;
}
long g(long align) {
return (align - 1) & ~(align - 1);
}
int h(long align) {
return -align == ~(align - 1);
}
Generated assembly:
f:
leaq-1(%rdi), %rax
negq%rdi
andq%rdi, %rax
retq
g:
xorl%eax, %eax
retq
h:
movl$1, %eax
retq
--
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 48279] wrong code with "-sroa -loop-unroll -dse"
https://bugs.llvm.org/show_bug.cgi?id=48279 Florian Hahn changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED Fixed By Commit(s)||1f1145006b32533484c9ebc0f45 ||e241a02fe6c8b --- Comment #5 from Florian Hahn --- Should be fixed by 1f1145006b32533484c9ebc0f45e241a02fe6c8b -- 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 48456] wrong code with "-early-cse-memssa -jump-threading -loop-unroll -correlated-propagation -dse"
https://bugs.llvm.org/show_bug.cgi?id=48456 Florian Hahn changed: What|Removed |Added Status|NEW |RESOLVED Fixed By Commit(s)||1f1145006b32533484c9ebc0f45 ||e241a02fe6c8b Resolution|--- |FIXED --- Comment #2 from Florian Hahn --- Should be fixed by 1f1145006b32533484c9ebc0f45e241a02fe6c8b -- 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 48560] New: this_thread::sleep_for(short duration) can sleep forever on Linux
https://bugs.llvm.org/show_bug.cgi?id=48560 Bug ID: 48560 Summary: this_thread::sleep_for(short duration) can sleep forever on Linux Product: libc++ Version: 11.0 Hardware: All OS: Linux Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: unassignedclangb...@nondot.org Reporter: paul.gr...@dynatrace.com CC: llvm-bugs@lists.llvm.org, mclow.li...@gmail.com lib++ uses nanosleep in __libcpp_thread_sleep_for like this: while (nanosleep(&__ts, &__ts) == -1 && errno == EINTR); On Linux, such a nanosleep loop can run forever because of a Linux bug that's documented here: https://man7.org/linux/man-pages/man2/nanosleep.2.html#BUGS For this to happen the thread needs to receive signals at a high frequency which seems to be rather uncommon. https://github.com/golang/proposal/blob/5b63da9579c3b19294be614dcad33e20a9a4ad22/design/24543-non-cooperative-preemption.md https://github.com/golang/go/blob/go1.15.6/src/runtime/signal_unix.go#L347 https://github.com/golang/go/blob/go1.15.6/src/runtime/preempt.go#L223 This could lead to problems when on Linux, native code that uses libc++ is called from a Go thread. The Go thread executing this_thread::sleep_for will loop forever calling nanosleep and the other Go thread that tries to preempt it will also loop forever, perpetually trying to preempt it. I know this is a Linux bug, but since a lot of people are using Linux it might be worth implementing a workaround in libc++. -- 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 48561] New: Obtained 45 lldb errors when running test-release.sh for 11.0.1 rc2
https://bugs.llvm.org/show_bug.cgi?id=48561 Bug ID: 48561 Summary: Obtained 45 lldb errors when running test-release.sh for 11.0.1 rc2 Product: lldb Version: 11.0 Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: nnel...@infowest.com CC: jdevliegh...@apple.com, llvm-bugs@lists.llvm.org Created attachment 24306 --> https://bugs.llvm.org/attachment.cgi?id=24306&action=edit >From testing.11.0.1-rc2.log Ubuntu 20.10 See attached. -- 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 28827 in oss-fuzz: llvm:llvm-opt-fuzzer--x86_64-instcombine: ASSERT: isa(Val) && "cast() argument of incompatible type!"
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevl...@apple.com, igm...@gmail.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Reproducible Stability-Memory-MemorySanitizer Engine-libfuzzer OS-Linux Proj-llvm Reported-2020-12-19 Type: Bug New issue 28827 by ClusterFuzz-External: llvm:llvm-opt-fuzzer--x86_64-instcombine: ASSERT: isa(Val) && "cast() argument of incompatible type!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=28827 Detailed Report: https://oss-fuzz.com/testcase?key=5741773775306752 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: llvm-opt-fuzzer--x86_64-instcombine Job Type: libfuzzer_msan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: isa(Val) && "cast() argument of incompatible type!" llvm::InstVisitor::visit Verifier::verify Sanitizer: memory (MSAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_msan_llvm&range=202008270608:202008280607 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5741773775306752 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 47455] lld sets interpreter even with -static
https://bugs.llvm.org/show_bug.cgi?id=47455 Fangrui Song changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX -- 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 28833 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::Sema::LookupName
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevl...@apple.com, igm...@gmail.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2020-12-20 Type: Bug New issue 28833 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::Sema::LookupName https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=28833 Detailed Report: https://oss-fuzz.com/testcase?key=6282289705254912 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffd6a352ff8 Crash State: clang::Sema::LookupName clang::Sema::LookupTemplateName clang::Sema::isTemplateName Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202011130615:202011140605 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6282289705254912 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 48562] New: clang-11 crashes on the thrill project
https://bugs.llvm.org/show_bug.cgi?id=48562 Bug ID: 48562 Summary: clang-11 crashes on the thrill project Product: clang Version: trunk Hardware: PC OS: FreeBSD Status: NEW Severity: enhancement Priority: P Component: C++11 Assignee: unassignedclangb...@nondot.org Reporter: y...@tsoft.com CC: blitzrak...@gmail.com, dgre...@apple.com, erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk Please see the attached crash log. The crash occurred on the Thrill project https://github.com/thrill/thrill rev.12c5b59bca66df93b66628b3829027bd0f110dd9 -- 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
