[llvm-bugs] Issue 59746 in oss-fuzz: llvm:clang-fuzzer: ASSERT: (FRI->ColonLoc.isValid() || !DG) && "cannot find for range declaration"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 59746 by ClusterFuzz-External: llvm:clang-fuzzer: ASSERT: (FRI->ColonLoc.isValid() || !DG) && "cannot find for range declaration" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=59746#c2 ClusterFuzz testcase 4965973330100224 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_msan_llvm=202210040607:202312020611 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 59224 in oss-fuzz: llvm:clang-objc-fuzzer: ASSERT: (T->isIntegralType(Context) || T->isEnumeralType()) && "Integral type required!"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 59224 by ClusterFuzz-External: llvm:clang-objc-fuzzer: ASSERT: (T->isIntegralType(Context) || T->isEnumeralType()) && "Integral type required!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=59224#c2 ClusterFuzz testcase 4935237113872384 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_msan_llvm=202210040607:202312020611 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 61558 in oss-fuzz: llvm:clang-fuzzer: ASSERT: getResultKind() == Found && "getFoundDecl called on non-unique result"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 61558 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=61558#c2 ClusterFuzz testcase 4888003510927360 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_msan_llvm=202210040607:202312020611 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 56647 in oss-fuzz: llvm:llvm-dwarfdump-fuzzer: ASSERT: hasVal
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 56647 by ClusterFuzz-External: llvm:llvm-dwarfdump-fuzzer: ASSERT: hasVal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=56647#c2 ClusterFuzz testcase 4864795284471808 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_msan_llvm=202210040607:202312020611 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 59145 in oss-fuzz: llvm:clang-fuzzer: ASSERT: SI.isSigned() == E->getType()->isSignedIntegerOrEnumerationType() && "Invalid ev
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 59145 by ClusterFuzz-External: llvm:clang-fuzzer: ASSERT: SI.isSigned() == E->getType()->isSignedIntegerOrEnumerationType() && "Invalid ev https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=59145#c2 ClusterFuzz testcase 4854336707231744 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_msan_llvm=202210040607:202312020611 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 28410 in oss-fuzz: llvm:llvm-dwarfdump-fuzzer: Null-dereference READ in llvm::raw_ostream::operator<
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #5 on issue 28410 by ClusterFuzz-External: llvm:llvm-dwarfdump-fuzzer: Null-dereference READ in llvm::raw_ostream::operator<< https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=28410#c5 ClusterFuzz testcase 4842450686443520 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_msan_llvm=202210040607:202312020611 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 61832 in oss-fuzz: llvm:clang-fuzzer: Crash in clang::CharLiteralParser::CharLiteralParser
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 61832 by ClusterFuzz-External: llvm:clang-fuzzer: Crash in clang::CharLiteralParser::CharLiteralParser https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=61832#c2 ClusterFuzz testcase 4840018089476096 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_msan_llvm=202210040607:202312020611 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 61169 in oss-fuzz: llvm:clang-objc-fuzzer: ASSERT: it != LocalDeclMap.end() && "Invalid argument to GetAddrOfLocalVar(), no decl!"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 61169 by ClusterFuzz-External: llvm:clang-objc-fuzzer: ASSERT: it != LocalDeclMap.end() && "Invalid argument to GetAddrOfLocalVar(), no decl!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=61169#c2 ClusterFuzz testcase 4835544759402496 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_msan_llvm=202210040607:202312020611 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 49587 in oss-fuzz: llvm:clang-fuzzer: ASSERT: Kind.getKind() == InitializationKind::IK_Copy || Kind.isExplicitCast() || Kind.g
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 49587 by ClusterFuzz-External: llvm:clang-fuzzer: ASSERT: Kind.getKind() == InitializationKind::IK_Copy || Kind.isExplicitCast() || Kind.g https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=49587#c2 ClusterFuzz testcase 4827879107592192 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_msan_llvm=202210040607:202312020611 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 54723 in oss-fuzz: llvm:clang-objc-fuzzer: ASSERT: isa(CanonicalType)
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 54723 by ClusterFuzz-External: llvm:clang-objc-fuzzer: ASSERT: isa(CanonicalType) https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=54723#c2 ClusterFuzz testcase 4822994059132928 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_msan_llvm=202210040607:202312020611 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 61187 in oss-fuzz: llvm:clang-objc-fuzzer: ASSERT: !isTokenSpecial() && "Should consume special tokens with Consume*Token"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 61187 by ClusterFuzz-External: llvm:clang-objc-fuzzer: ASSERT: !isTokenSpecial() && "Should consume special tokens with Consume*Token" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=61187#c2 ClusterFuzz testcase 4733621595144192 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_msan_llvm=202210040607:202312020611 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 60816 in oss-fuzz: llvm:clang-objc-fuzzer: Abrt in llvm::llvm_unreachable_internal
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 60816 by ClusterFuzz-External: llvm:clang-objc-fuzzer: Abrt in llvm::llvm_unreachable_internal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=60816#c2 ClusterFuzz testcase 4642787715579904 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_msan_llvm=202210040607:202312020611 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 59788 in oss-fuzz: llvm:clang-pseudo-fuzzer: ASSERT: Kind == 'u' || Kind == 'U' || Kind == 'N'
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 59788 by ClusterFuzz-External: llvm:clang-pseudo-fuzzer: ASSERT: Kind == 'u' || Kind == 'U' || Kind == 'N' https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=59788#c2 ClusterFuzz testcase 4510065135845376 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_msan_llvm=202210040607:202312020611 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 74227] [mlir] --sparsification crashed with assertion failure.
Issue
74227
Summary
[mlir] --sparsification crashed with assertion failure.
Labels
mlir
Assignees
Reporter
anonymousMCS
git version: e9c6f3f5e7e23b23de4eeaa182ebfcb7d2188495
system: ```Ubuntu 20.04.6 LTS (Focal Fossa)```
reproduced with: ```mlir-opt --sparsification a.mlir```
a.mlir:
```
func.func private @func2() {
%false = arith.constant false
// Though this line is not used, the crash will disappear if delete this line.
%c2105432605_i64 = arith.constant 2105432605 : i64
%false_7 = arith.constant false
%c0 = arith.constant 0 : index
%c1 = arith.constant 1 : index
%c4 = arith.constant 4 : index
%c7 = arith.constant 7 : index
%c8 = arith.constant 8 : index
%c11 = arith.constant 11 : index
%c12 = arith.constant 12 : index
%c21 = arith.constant 21 : index
%c27 = arith.constant 27 : index
%alloc_22 = memref.alloc(%c21) {alignment = 64 : i64} : memref
%14 = bufferization.to_tensor %alloc_22 : memref
%alloc_34 = memref.alloc() : memref<20x5x5xi1>
%16 = index.shrs %c1, %c27
%c0_i32 = arith.constant 0 : i32
%23 = arith.ceildivsi %false, %false_7 : i1
%28 = index.maxu %16, %c4
%40 = index.maxs %c7, %c12
%c2105432605_i64_55 = arith.constant 2105432605 : i64
%57 = index.add %c11, %c0
%c1_68 = arith.constant 1 : index
%71 = index.shru %28, %c8
%alloc_72 = memref.alloc() {alignment = 64 : i64} : memref<20x5x5xi1>
%72 = bufferization.to_tensor %alloc_72 : memref<20x5x5xi1>
%76 = index.add %c1_68, %71
%alloc_75 = memref.alloc() {alignment = 64 : i64} : memref<20x5x5xi1>
%c20_77 = arith.constant 20 : index
%c5_79 = arith.constant 5 : index
%c5_81 = arith.constant 5 : index
%77 = arith.index_cast %c0_i32 : i32 to index
%subview = memref.subview %alloc_75[%57, %77, %c0] [%40, %c1, %c5_81] [%c1, %c1, %c1] : memref<20x5x5xi1> to memref>
%78 = scf.for %arg0 = %c0 to %c20_77 step %40 iter_args(%arg1 = %72) -> (tensor<20x5x5xi1>) {
%119 = scf.for %arg2 = %c0 to %c5_79 step %c1 iter_args(%arg3 = %arg1) -> (tensor<20x5x5xi1>) {
%subview_102 = memref.subview %alloc_75[%arg0, %arg2, %c0] [%16, %57, %c5_81] [%76, %c1, %c1] : memref<20x5x5xi1> to memref>
%alloc_103 = memref.alloc() {alignment = 64 : i64} : memref<20x5x5xi1>
memref.copy %subview_102, %subview : memref> to memref>
%122 = bufferization.to_tensor %alloc_103 : memref<20x5x5xi1>
scf.yield %122 : tensor<20x5x5xi1>
}
scf.yield %119 : tensor<20x5x5xi1>
}
vector.warp_execute_on_lane_0(%c1_68)[32] {
%mapped_108 = linalg.map ins(%78, %alloc_34, %78 : tensor<20x5x5xi1>, memref<20x5x5xi1>, tensor<20x5x5xi1>) outs(%78 : tensor<20x5x5xi1>)
(%in: i1, %in_109: i1, %in_110: i1) {
%alloc_119 = memref.alloc() {alignment = 64 : i64} : memref<13x26x13xi64>
memref.store %c2105432605_i64_55, %alloc_119[%c21, %c1, %c12] : memref<13x26x13xi64>
linalg.yield %23 : i1
}
}
return
}
```
trace:
```
mlir-opt: /data/bin/llvm-project/llvm/include/llvm/ADT/SmallVector.h:294: T& llvm::SmallVectorTemplateCommon >::operator[](llvm::SmallVectorTemplateCommon >::size_type) [with T = mlir::Value; = void; llvm::SmallVectorTemplateCommon >::reference = mlir::Value&; llvm::SmallVectorTemplateCommon >::size_type = long unsigned int]: Assertion `idx < size()' failed.
PLEASE submit a bug report to https://github.com/llvm/llvm-project/issues/ and include the crash backtrace.
Stack dump:
0. Program arguments: /data/bin/llvm-project/build/bin/mlir-opt --sparsification a.mlir
#0 0x5577cebbee8f llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) (/data/bin/llvm-project/build/bin/mlir-opt+0x1640e8f)
#1 0x5577cebbbee4 SignalHandler(int) Signals.cpp:0:0
#2 0x7f914fc4d420 __restore_rt (/lib/x86_64-linux-gnu/libpthread.so.0+0x14420)
#3 0x7f914f73800b raise (/lib/x86_64-linux-gnu/libc.so.6+0x4300b)
#4 0x7f914f717859 abort (/lib/x86_64-linux-gnu/libc.so.6+0x22859)
#5 0x7f914f717729 (/lib/x86_64-linux-gnu/libc.so.6+0x22729)
#6 0x7f914f728fd6 (/lib/x86_64-linux-gnu/libc.so.6+0x33fd6)
#7 0x5577d0240b58 (/data/bin/llvm-project/build/bin/mlir-opt+0x2cc2b58)
#8 0x5577d1a4db8a mlir::RewriterBase::replaceOpWithIf(mlir::Operation*, mlir::ValueRange, bool*, llvm::unique_function) (/data/bin/llvm-project/build/bin/mlir-opt+0x44cfb8a)
#9 0x5577d027fe09 (anonymous namespace)::LastTensorLoadCanonicalization::matchAndRewrite(mlir::scf::ForOp, mlir::PatternRewriter&) const SCF.cpp:0:0
#10 0x5577d4573038 mlir::PatternApplicator::matchAndRewrite(mlir::Operation*, mlir::PatternRewriter&, llvm::function_ref, llvm::function_ref, llvm::function_ref) (/data/bin/llvm-project/build/bin/mlir-opt+0x6ff5038)
#11 0x5577d18e81cc (anonymous namespace)::GreedyPatternRewriteDriver::processWorklist()
[llvm-bugs] [Bug 74221] [libc++][test] `nasty_char_traits::move` is incompatible with `constexpr`
Issue
74221
Summary
[libc++][test] `nasty_char_traits::move` is incompatible with `constexpr`
Labels
libc++
Assignees
Reporter
StephanTLavavej
Found while running libc++'s test suite with MSVC's STL.
`nasty_char_traits::move` is marked `constexpr` but compares unrelated pointers `s1 < s2`. This is forbidden, and `nasty_char_traits::copy` acknowledges this immediately below:
https://github.com/llvm/llvm-project/blob/38f75d606f94e6b552fd74d487b061a1f8f907fa/libcxx/test/support/nasty_string.h#L120-L141
Click to expand compiler error:
With libc++'s test suite, MSVC's STL, and Clang/LLVM, `std/strings/basic.string/string.modifiers/string_append/initializer_list.pass.cpp` emits this error:
```
D:\GitHub\STL\llvm-project\libcxx\test\std\strings\basic.string\string.modifiers\string_append\initializer_list.pass.cpp(53,17): error: static assertion _expression_ is not an integral constant _expression_
static_assert(test());
^~
D:\GitHub\STL\llvm-project\libcxx\test\support\nasty_string.h(122,10): note: comparison between '_Mypair._Myval2._Bx._Buf[3]' and '&{CharT(('a')), CharT(('b')), CharT(('c'))}[0]' has unspecified value
if (s1 < s2) {
^
D:\GitHub\STL\out\x64\out\inc\xstring(3311,13): note: in call to 'move(_Mypair._Myval2._Bx._Buf[3], &{CharT(('a')), CharT(('b')), CharT(('c'))}[0], 3)'
_Traits::move(_Old_ptr + _Old_size, _Ptr, _Count);
^
D:\GitHub\STL\out\x64\out\inc\xstring(3152,16): note: in call to '>append(&{CharT(('a')), CharT(('b')), CharT(('c'))}[0], 3)'
return append(_Ilist.begin(), _Convert_size(_Ilist.size()));
^
D:\GitHub\STL\llvm-project\libcxx\test\std\strings\basic.string\string.modifiers\string_append\initializer_list.pass.cpp(27,5): note: in call to '>append({&{CharT(('a')), CharT(('b')), CharT(('c'))}[0], &{CharT(('a')), CharT(('b')), CharT(('c'))}[3]})'
s.append({CharT('a'), CharT('b'), CharT('c')});
^
D:\GitHub\STL\llvm-project\libcxx\test\std\strings\basic.string\string.modifiers\string_append\initializer_list.pass.cpp(44,3): note: in call to 'test()'
test();
^
D:\GitHub\STL\llvm-project\libcxx\test\std\strings\basic.string\string.modifiers\string_append\initializer_list.pass.cpp(53,17): note: in call to 'test()'
static_assert(test());
^
```
In microsoft/STL's product code, I have a truly marvelous way to avoid this problem - a linear scan to detect whether the first iterator of the destination is within the source range, in which case a backward loop is necessary. See https://github.com/microsoft/STL/blob/0403d19f5461fd15983737c3f01ec34800ea9275/stl/inc/xstring#L85-L93 .
___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 74219] missing warning on loosing precision to bit fields
Issue
74219
Summary
missing warning on loosing precision to bit fields
Labels
clang:diagnostics
Assignees
Reporter
wheatman
The following code gives warnings about loosing precision when we use an int to initilize a smaller type
```
class A {
int i;
short s;
char c;
A(int x, int y, int z) :
i(x),
s(y), // warning: implicit conversion loses integer precision: 'int' to 'short' [-Wimplicit-int-conversion]
c(z) // warning: implicit conversion loses integer precision: 'int' to 'char' [-Wimplicit-int-conversion]
{}
};
```
However, if that smaller type is a bitfield as in
```
class B {
int i;
int s : 16;
int c : 8;
B(int x, int y, int z) : i(x), s(y), c(z) {}
};
```
no warnings are given
https://godbolt.org/z/7oqY78T58
This issue led to the bug in https://github.com/llvm/llvm-project/issues/71888
___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 74216] Add Profile-Guided Optimization (PGO) support to the Flang compiler
Issue 74216 Summary Add Profile-Guided Optimization (PGO) support to the Flang compiler Labels flang Assignees Reporter zamazan4ik Similar to Clang, we need to support Profile-Guided Optimization (PGO) in Flang too. Use cases for having this optimization are completely the same as we have for Clang right now - have an ability to optimize better Fortran code based on the runtime information. I propose adding the following PGO types for Flang: * IR PGO (`-fprofile-generate`/`-fprofile-use` options in Clang) * CS PGO (`fcs-profile-generate` in Clang). This option would be a good addition to IR PGO * Sampling PGO (AutoFDO + `-fprofile-sample-use` option in Clang). Having sampling PGO support is important if we want to collect PGO profiles directly from a production environment. I think there is no need to implement FE PGO (`-fprofile-instr-generate`/`-fprofile-instr-use` options in Clang) in Flang since IR PGO is a better option according to the [issue](https://github.com/llvm/llvm-project/issues/45668). As a reference, the Clang PGO [docs](https://clang.llvm.org/docs/UsersManual.html#profile-guided-optimization) can be used. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 74214] [libc++][test] User-defined `std::ctype` specialization lacks `tolower()`
Issue 74214 Summary [libc++][test] User-defined `std::ctype` specialization lacks `tolower()` Labels libc++ Assignees Reporter StephanTLavavej Found while running libc++'s test suite with MSVC's STL. The following code is non-conforming: https://github.com/llvm/llvm-project/blob/7ec4f6094e54911794c142b5d88496a220d807d6/libcxx/test/std/localization/locale.categories/category.numeric/locale.num.get/user_defined_char_type.pass.cpp#L76-L86 This specialization doesn't meet all of the Standard's requirements for `std::ctype` because it's missing a bunch of stuff. In particular, it's missing a `tolower()` member function, which is what MSVC's STL wants. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 74212] Reference initialization involving deleted conversion function wrongly diagnosed as "ambiguous"
Issue
74212
Summary
Reference initialization involving deleted conversion function wrongly diagnosed as "ambiguous"
Labels
new issue
Assignees
Reporter
t3nsor
Code:
```
struct Cat { };
struct Dog {
operator Cat();
operator Cat&() = delete;
};
Cat const& r = Dog{};
```
Clang 17.0.1 (all language versions from c++11 to c++2b) gives the wrong diagnostic, reproduced below:
```
:6:12: error: reference initialization of type 'const Cat &' with initializer of type 'Dog' is ambiguous
6 | Cat const& r = Dog{};
|^ ~
:3:5: note: candidate function
3 | operator Cat();
| ^
:4:5: note: candidate function has been explicitly deleted
4 | operator Cat&() = delete;
| ^
```
There's no ambiguity; under [[dcl.init.ref]/5.1](http://eel.is/c++draft/dcl.init.ref#5.1) and [[over.match.ref]/1.1](http://eel.is/c++draft/over.match.ref#1.1), the first stage of overload resolution involves `operator Cat&` only.
___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 74208] [flang] flang-new: error: unknown argument: '-fprofile-generate'
Issue 74208 Summary [flang] flang-new: error: unknown argument: '-fprofile-generate' Labels flang Assignees Reporter foxtran I have tried to build Fortran application with Profile-Guided Optimization (PGO). I used the following command: ``` flang-new test.f90 -c -fprofile-generate -g ``` Unfortunately, compilation was failed with the following message: ``` flang-new: error: unknown argument: '-fprofile-generate' ``` Used version: ``` flang-new --version flang-new version 18.0.0 (https://github.com/llvm/llvm-project.git 9584f5834499e6093797d4a28fde209f927ea556) ``` ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 74205] `clang` feature request: warn on incorrect tagged union value access
Issue
74205
Summary
`clang` feature request: warn on incorrect tagged union value access
Labels
clang
Assignees
Reporter
matheusmoreira
Currently `clang` does not produce a warning if the value of a tagged union that doesn't correspond to its type tag is accessed.
For example, this code:
```C
// warn.c
#include
enum T { I, F };
union U { int i; float f; };
struct S { enum T t; union U u; };
int main(void) {
struct S s = { .t = F, .u.f = 12345.67890f };
switch (s.t) {
case I:
printf("%d\n", s.u.i);
break;
case F:
// copied the above case
// but neglected to update the code
printf("%d\n", s.u.i);
break;
}
}
```
Does not produce any warning when compiled, leading to incorrect results:
```shell
$ clang -Weverything -o warn warn.c && ./warn
1178658487
```
I understand that `union`s are typically used for type punning and that such accesses are often intended by the programmer but compiler checks would still be beneficial when that's not the case. [People have created C preprocessor solutions][1] to use tagged unions safely in C. I've also seen support for safe tagged unions in newer languages like Zig.
A compiler mechanism to establish a relationship between the `union` values and their corresponding `enum` tags would be extremely useful. Something like this, perhaps:
```C
struct S {
enum T t;
union U {
int i __attribute__((tag(t, I)));
float f __attribute__((tag(t, F)));
} u;
};
```
Then `clang` would be able to warn when `union` values are accessed in a context where their specified tags are not known to be the correct value:
```C
switch (s.t) {
case I:
// i is accessed
// the tag of i is t
// t is supposed to equal I
// compiler knows t equals I because of switch case
// correct, no warning is emitted
printf("%d\n", s.u.i);
break;
case F:
// i is accessed
// the tag of i is t
// t is supposed to equal I
// compiler knows t equals F because of switch case
// incorrect, a warning is emitted
printf("%d\n", s.u.i);
break;
}
```
Relevant links:
- lone-lang/lone#1
[1]: https://github.com/Hirrolot/datatype99
___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 74202] [flang][openmp] difference of timestamps between two SYSTEM_CLOCK calls returns CPU time
Issue
74202
Summary
[flang][openmp] difference of timestamps between two SYSTEM_CLOCK calls returns CPU time
Labels
flang
Assignees
Reporter
foxtran
Having the following code (tests matrix multiplication speed in stupid way):
```
program matrix_multiply
use omp_lib
implicit none
real(8), allocatable :: A(:,:), B(:,:), C(:,:)
integer(4) :: i, j, k, nbfcn4, df4
integer(8) :: nbfcn, df
integer :: ierr, num_threads
integer(8) :: start_time, end_time, elapsed_time
integer(8) :: count,count_rate,clock_rate
real(8) :: seconds_elapsed, peak, actual
real(8) :: ts1, ts2
nbfcn4 = 635
df4 = 8645
nbfcn = nbfcn4
df = df4
allocate(A(nbfcn,nbfcn), B(df,nbfcn), C(nbfcn,df), source = 0d0)
call random_seed()
call random_number(A)
call random_number(B)
call dgemm('t','t',nbfcn,df,nbfcn,1.d0,A,nbfcn,B,df,0.d0,C,nbfcn)
call SYSTEM_CLOCK(count=start_time, count_rate=clock_rate)
call cpu_time(ts1)
do i = 1, 100
call dgemm('t','t',nbfcn,df,nbfcn,1.d0,A,nbfcn,B,df,0.d0,C,nbfcn)
end do
call SYSTEM_CLOCK(count=end_time)
call cpu_time(ts2)
elapsed_time = end_time - start_time
seconds_elapsed = real(elapsed_time) / real(clock_rate)
peak = seconds_elapsed * omp_get_max_threads() * 2.45_8 * 1e9_8 * 16._8
actual = real(2 * nbfcn*nbfcn * df, kind=8) * 100
write(*,"(F6.2,A,F6.2,' ',I0)") seconds_elapsed, "s ", actual / peak * 100._8, omp_get_max_threads()
seconds_elapsed = ts2 - ts1
peak = seconds_elapsed * omp_get_max_threads() * 2.45_8 * 1e9_8 * 16._8
actual = real(2 * nbfcn*nbfcn * df, kind=8) * 100
write(*,"(F6.2,A,F6.2,' ',I0)") seconds_elapsed, "s ", actual / peak * 100._8, omp_get_max_threads()
! time * cores * freq * ops
end program matrix_multiply
```
For current flang, it gives me the same number for CPU_TIME calls and for SYSTEM_CLOCK calls.
Example output:
```
LD_LIBRARY_PATH=/home/lokalgi/test/llvm-install/lib:D_LIBRARY_PATH OMP_NUM_THREADS=8 numactl -C 24-31 ./MM2.libblis-mt.orig.f18
23.23s 9.57 8
23.23s 9.57 8
```
At the same time, GCC produces different timings:
```
OMP_NUM_THREADS=8 numactl -C 24-31 ./MM2.libblis-mt.orig.gcc
2.14s 103.76 8
17.04s 13.05 8
```
**Expected**
- SYSTEM_CLOCK takes system time (not happens)
- CPU_TIME takes total CPU time (works now)
___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 64653 in oss-fuzz: llvm:clang-format-fuzzer: ASSERT: !eof()
Status: New Owner: CC: k...@google.com, masc...@google.com, igm...@gmail.com, sammcc...@google.com, da...@adalogics.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, jo...@devlieghere.com, 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-2023-12-02 Type: Bug New issue 64653 by ClusterFuzz-External: llvm:clang-format-fuzzer: ASSERT: !eof() https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=64653 Detailed Report: https://oss-fuzz.com/testcase?key=5218745949487104 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-format-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: !eof() clang::format::ScopedMacroState::getNextToken clang::format::UnwrappedLineParser::calculateBraceTypes Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=202309010608:202312010616 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5218745949487104 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 52203 in oss-fuzz: llvm: Fuzzing build failure
Updates: Status: Verified Comment #71 on issue 52203 by ClusterFuzz-External: llvm: Fuzzing build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=52203#c71 The latest build has succeeded, closing this issue. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 64647 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::Sema::DiagnoseEmptyLookup
Status: New Owner: CC: k...@google.com, masc...@google.com, igm...@gmail.com, sammcc...@google.com, da...@adalogics.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, jo...@devlieghere.com, 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-2023-12-02 Type: Bug New issue 64647 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::Sema::DiagnoseEmptyLookup https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=64647 Detailed Report: https://oss-fuzz.com/testcase?key=6308680655831040 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffc698808e0 Crash State: clang::Sema::DiagnoseEmptyLookup FinishOverloadedCallExpr clang::Sema::BuildOverloadedCallExpr Sanitizer: address (ASAN) Crash Revision: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=202312010616 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6308680655831040 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 51628 in oss-fuzz: llvm:clang-objc-fuzzer: ASSERT: isa(Val) && "cast() argument of incompatible type!"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 51628 by ClusterFuzz-External: llvm:clang-objc-fuzzer: ASSERT: isa(Val) && "cast() argument of incompatible type!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=51628#c2 ClusterFuzz testcase 6001372767584256 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=202309010608:202312010616 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 50788 in oss-fuzz: llvm:clang-pseudo-fuzzer: Stack-overflow in llvm::sys::unicode::compareNode
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 50788 by ClusterFuzz-External: llvm:clang-pseudo-fuzzer: Stack-overflow in llvm::sys::unicode::compareNode https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=50788#c2 ClusterFuzz testcase 5822799293317120 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=202309010608:202312010616 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 59315 in oss-fuzz: llvm:clang-fuzzer: ASSERT: SubobjectDecl && "SubobjectDecl shall be non-null"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 59315 by ClusterFuzz-External: llvm:clang-fuzzer: ASSERT: SubobjectDecl && "SubobjectDecl shall be non-null" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=59315#c2 ClusterFuzz testcase 5798108718825472 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=202309010608:202312010616 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 18311 in oss-fuzz: llvm:clang-fuzzer: ASSERT: cast(SubExpr)->getQualifier() && "fixed to a member ref with no nes
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #6 on issue 18311 by ClusterFuzz-External: llvm:clang-fuzzer: ASSERT: cast(SubExpr)->getQualifier() && "fixed to a member ref with no nes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=18311#c6 ClusterFuzz testcase 5758145414037504 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=202309010608:202312010616 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 17663 in oss-fuzz: llvm:llvm-special-case-list-fuzzer: Stack-overflow in p_ere
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #6 on issue 17663 by ClusterFuzz-External: llvm:llvm-special-case-list-fuzzer: Stack-overflow in p_ere https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=17663#c6 ClusterFuzz testcase 5744750207959040 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=202309010608:202312010616 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 18061 in oss-fuzz: llvm:llvm-special-case-list-fuzzer: Heap-buffer-overflow in p_ere
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #6 on issue 18061 by ClusterFuzz-External: llvm:llvm-special-case-list-fuzzer: Heap-buffer-overflow in p_ere https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=18061#c6 ClusterFuzz testcase 5717405149429760 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=202309010608:202312010616 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 22113 in oss-fuzz: llvm:llvm-special-case-list-fuzzer: Timeout in llvm-special-case-list-fuzzer
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #5 on issue 22113 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=22113#c5 ClusterFuzz testcase 5681235116687360 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=202309010608:202312010616 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 19043 in oss-fuzz: llvm:clang-objc-fuzzer: ASSERT: Result && "Could not evaluate expression"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #5 on issue 19043 by ClusterFuzz-External: llvm:clang-objc-fuzzer: ASSERT: Result && "Could not evaluate expression" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19043#c5 ClusterFuzz testcase 5677465905397760 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=202309010608:202312010616 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 17179 in oss-fuzz: llvm:llvm-special-case-list-fuzzer: Out-of-memory in llvm_llvm-special-case-list-fuzzer
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #6 on issue 17179 by ClusterFuzz-External: llvm:llvm-special-case-list-fuzzer: Out-of-memory in llvm_llvm-special-case-list-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=17179#c6 ClusterFuzz testcase 5636403936886784 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=202309010608:202312010616 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 50192 in oss-fuzz: llvm:clang-fuzzer: ASSERT: NextLocalOffset + Length + 1 > NextLocalOffset && NextLocalOffset + Length + 1
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 50192 by ClusterFuzz-External: llvm:clang-fuzzer: ASSERT: NextLocalOffset + Length + 1 > NextLocalOffset && NextLocalOffset + Length + 1 < https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=50192#c2 ClusterFuzz testcase 5159561195028480 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=202309010608:202312010616 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 74189] Clang-18 crash when compiled with -O2 -g -c.
Issue
74189
Summary
Clang-18 crash when compiled with -O2 -g -c.
Labels
new issue
Assignees
Reporter
iamanonymouscs
Clang-18 with -O2 -g -c crashes on the test case.
Compiler explorer: https://godbolt.org/z/MsheKq9vb
```
$cat mutant.c
struct __attribute__((packed)) A { char c1; short a1[__INT_MAX__]; };
struct __attribute__((packed)) B { char c2; short a2[100]; };
struct S { struct A p1; struct B p2[4]; };
void bar (short int);
static void
foo (struct S *q)
{
for (int i = 0; i < q->p1.c1; i++)
for (int j = 0; j < q->p2[i].c2; j++)
bar (q->p2[i].a2[j]);
}
int
main ()
{
struct S q = {};
q.p2[0].c2 = q.p2[1].c2 = 3;
foo ();
}
$clang-18 -O2 -g -c mutant.c
PLEASE submit a bug report to https://github.com/llvm/llvm-project/issues/ and include the crash backtrace, preprocessed source, and associated run script.
Stack dump:
0. Program arguments: clang-18 -O2 -g -c mutant.c
1. parser at end of file
2. Code generation
3. Running pass 'Function Pass Manager' on module 'mutant.c'.
4. Running pass 'Assignment Tracking Analysis' on function '@main'
#0 0x7ff48329b266 llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) (/usr/lib/llvm-18/bin/../lib/libLLVM-18.so.1+0xd2b266)
#1 0x7ff483299170 llvm::sys::RunSignalHandlers() (/usr/lib/llvm-18/bin/../lib/libLLVM-18.so.1+0xd29170)
#2 0x7ff48329a8c4 llvm::sys::CleanupOnSignal(unsigned long) (/usr/lib/llvm-18/bin/../lib/libLLVM-18.so.1+0xd2a8c4)
#3 0x7ff4831e8bb0 (/usr/lib/llvm-18/bin/../lib/libLLVM-18.so.1+0xc78bb0)
#4 0x7ff48dd7c980 __restore_rt (/lib/x86_64-linux-gnu/libpthread.so.0+0x12980)
#5 0x7ff4834b6e2a (/usr/lib/llvm-18/bin/../lib/libLLVM-18.so.1+0xf46e2a)
#6 0x7ff4834b2418 llvm::AssignmentTrackingAnalysis::runOnFunction(llvm::Function&) (/usr/lib/llvm-18/bin/../lib/libLLVM-18.so.1+0xf42418)
#7 0x7ff4833e10df llvm::FPPassManager::runOnFunction(llvm::Function&) (/usr/lib/llvm-18/bin/../lib/libLLVM-18.so.1+0xe710df)
#8 0x7ff4833e6dc3 llvm::FPPassManager::runOnModule(llvm::Module&) (/usr/lib/llvm-18/bin/../lib/libLLVM-18.so.1+0xe76dc3)
#9 0x7ff4833e17d4 llvm::legacy::PassManagerImpl::run(llvm::Module&) (/usr/lib/llvm-18/bin/../lib/libLLVM-18.so.1+0xe717d4)
#10 0x7ff48ba7e09f clang::EmitBackendOutput(clang::DiagnosticsEngine&, clang::HeaderSearchOptions const&, clang::CodeGenOptions const&, clang::TargetOptions const&, clang::LangOptions const&, llvm::StringRef, llvm::Module*, clang::BackendAction, llvm::IntrusiveRefCntPtr, std::unique_ptr>) (/usr/lib/llvm-18/bin/../lib/libclang-cpp.so.18+0x1ade09f)
#11 0x7ff48be145fe (/usr/lib/llvm-18/bin/../lib/libclang-cpp.so.18+0x1e745fe)
#12 0x7ff48aa30866 clang::ParseAST(clang::Sema&, bool, bool) (/usr/lib/llvm-18/bin/../lib/libclang-cpp.so.18+0xa90866)
#13 0x7ff48c888645 clang::FrontendAction::Execute() (/usr/lib/llvm-18/bin/../lib/libclang-cpp.so.18+0x28e8645)
#14 0x7ff48c806cc4 clang::CompilerInstance::ExecuteAction(clang::FrontendAction&) (/usr/lib/llvm-18/bin/../lib/libclang-cpp.so.18+0x2866cc4)
#15 0x7ff48c9031c0 clang::ExecuteCompilerInvocation(clang::CompilerInstance*) (/usr/lib/llvm-18/bin/../lib/libclang-cpp.so.18+0x29631c0)
#16 0x561c05ddd837 cc1_main(llvm::ArrayRef, char const*, void*) (/usr/lib/llvm-18/bin/clang+0x13837)
#17 0x561c05dda905 (/usr/lib/llvm-18/bin/clang+0x10905)
#18 0x7ff48c49e909 (/usr/lib/llvm-18/bin/../lib/libclang-cpp.so.18+0x24fe909)
#19 0x7ff4831e894c llvm::CrashRecoveryContext::RunSafely(llvm::function_ref) (/usr/lib/llvm-18/bin/../lib/libLLVM-18.so.1+0xc7894c)
#20 0x7ff48c49e2ae clang::driver::CC1Command::Execute(llvm::ArrayRef>, std::__cxx11::basic_string, std::allocator>*, bool*) const (/usr/lib/llvm-18/bin/../lib/libclang-cpp.so.18+0x24fe2ae)
#21 0x7ff48c4660f1 clang::driver::Compilation::ExecuteCommand(clang::driver::Command const&, clang::driver::Command const*&, bool) const (/usr/lib/llvm-18/bin/../lib/libclang-cpp.so.18+0x24c60f1)
#22 0x7ff48c46633e clang::driver::Compilation::ExecuteJobs(clang::driver::JobList const&, llvm::SmallVectorImpl>&, bool) const (/usr/lib/llvm-18/bin/../lib/libclang-cpp.so.18+0x24c633e)
#23 0x7ff48c48239c clang::driver::Driver::ExecuteCompilation(clang::driver::Compilation&, llvm::SmallVectorImpl>&) (/usr/lib/llvm-18/bin/../lib/libclang-cpp.so.18+0x24e239c)
#24 0x561c05dda25c clang_main(int, char**, llvm::ToolContext const&) (/usr/lib/llvm-18/bin/clang+0x1025c)
#25 0x561c05de7f32 main (/usr/lib/llvm-18/bin/clang+0x1df32)
#26 0x7ff48177fc87 __libc_start_main /build/glibc-CVJwZb/glibc-2.27/csu/../csu/libc-start.c:344:0
#27 0x561c05dd71ea _start (/usr/lib/llvm-18/bin/clang+0xd1ea)
clang-18: error: clang frontend command failed with exit code 139 (use -v to see invocation)
Ubuntu clang version
[llvm-bugs] Issue 33290 in oss-fuzz: llvm:clang-format-fuzzer: Stack-overflow in clang::Lexer::LexNumericConstant
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #4 on issue 33290 by ClusterFuzz-External: llvm:clang-format-fuzzer: Stack-overflow in clang::Lexer::LexNumericConstant https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=33290#c4 ClusterFuzz testcase 4820358873088000 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=202309010608:202312010616 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
