[llvm-bugs] [Bug 48452] clang-tblgen crashing on x86_64 x32 ABI
https://bugs.llvm.org/show_bug.cgi?id=48452 Harald van Dijk changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Fixed By Commit(s)||f61e5ecb919b3901590328e69d3 ||e4a557eefd788 --- Comment #3 from Harald van Dijk --- The original error was fixed by D93157. Further code generation fixes have now gone in, and testing with those in shows that clang-for-x32 is now able to build clang-for-x32, tested with commit 09d0e7a7. -- 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 48452] clang-tblgen crashing on x86_64 x32 ABI
https://bugs.llvm.org/show_bug.cgi?id=48452 Simon Pilgrim changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED -- 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 48538] New: Template contsructor isntantiates invalid copy constructor
https://bugs.llvm.org/show_bug.cgi?id=48538
Bug ID: 48538
Summary: Template contsructor isntantiates invalid copy
constructor
Product: clang
Version: trunk
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: C++
Assignee: unassignedclangb...@nondot.org
Reporter: stinkingmad...@gmail.com
CC: blitzrak...@gmail.com, dgre...@apple.com,
erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org,
richard-l...@metafoo.co.uk
#include
template
struct S
{
template, U> = 0>
S(S>) {}
};
void foo(S) {}
Will yield the error
:8:32: error: copy constructor must pass its first argument by
reference
S(S>) {}
^
const &
:11:17: note: in instantiation of template class 'S' requested
here
void foo(S)
I believe the snippet is well-formed due to either [class.copy.ctor]/5
> A declaration of a constructor for a class X is ill-formed if its first
> parameter is of type cv X and
> either there are no other parameters or else all other parameters have
> default arguments.
> A member function template is never instantiated to produce such a
> constructor signature.
Or simply because it should SFINAE away, the constructor is dependent.
--
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 48539] New: ReflowComments breaks Qt translation comments
https://bugs.llvm.org/show_bug.cgi?id=48539
Bug ID: 48539
Summary: ReflowComments breaks Qt translation comments
Product: clang
Version: 10.0
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Priority: P
Component: Formatter
Assignee: unassignedclangb...@nondot.org
Reporter: jva...@gmail.com
CC: djas...@google.com, kli...@google.com,
llvm-bugs@lists.llvm.org
Qt has a concept of translation comments (see
https://doc.qt.io/qt-5/i18n-source-translation.html#translator-comments)
This gives extra meaning to //:, //=, //~.
This is a bit similar to doxygen using ///, ///<, //! or //!<
When reflown and a part of the comments are added on a new line, it should
repeat these extra characters as part of the comment token.
The reproduction:
.clang-format
=
ColumnLimit: 40
ReflowComments: true
example.cpp
===
//: This is a test. AA A AAA
QString example = tr("Example");
result.cpp
==
//: This is a test. AA A
//AAA
QString example = tr("Example");
expected.cpp
//: This is a test. AA A
//: AAA
QString example = tr("Example");
--
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 48368] Support the AArch64 variant PCS symbol st_other value
https://bugs.llvm.org/show_bug.cgi?id=48368 Adhemerval Zanella changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #1 from Adhemerval Zanella --- Implemented by https://reviews.llvm.org/rG978eb3b87bca0837d52d096c343fc70b06d9a04d -- 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 48540] New: vector type declaration in parens causes assert/OOM crash
https://bugs.llvm.org/show_bug.cgi?id=48540 Bug ID: 48540 Summary: vector type declaration in parens causes assert/OOM crash Product: clang Version: 11.0 Hardware: PC OS: All Status: NEW Severity: normal Priority: P Component: C Assignee: unassignedclangb...@nondot.org Reporter: erich.ke...@intel.com CC: blitzrak...@gmail.com, dgre...@apple.com, erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk https://godbolt.org/z/jvY5vq This valid declaration: int (__attribute__((vector_size(16))) b4[4][3][2]); causes an assertion (see below) in debug mode, and an OOM error otherwise. It apperas that the VectorTypeLoc isn't handled here in the DeclaratorLocFiller, which causes the issue. I don't have a good idea of how to implement this (or what sort of information is required here), so I'm hoping I can get some guidance. bash-4.2$ ./bin/clang -cc1 temp.c unsupported TypeLoc kind in declarator! UNREACHABLE executed at /iusers/ekeane1/workspaces/llvm-project/clang/lib/Sema/SemaType.cpp:6138! PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash backtrace, preprocessed source, and associated run script. Stack dump: 0. Program arguments: ./bin/clang -cc1 temp.c 1. temp.c:1:51: current parser token ';' #0 0x0508c787 llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) /iusers/ekeane1/workspaces/llvm-project/llvm/lib/Support/Unix/Signals.inc:563:22 #1 0x0508c83e PrintStackTraceSignalHandler(void*) /iusers/ekeane1/workspaces/llvm-project/llvm/lib/Support/Unix/Signals.inc:630:1 #2 0x0508a821 llvm::sys::RunSignalHandlers() /iusers/ekeane1/workspaces/llvm-project/llvm/lib/Support/Signals.cpp:71:20 #3 0x0508c1cf SignalHandler(int) /iusers/ekeane1/workspaces/llvm-project/llvm/lib/Support/Unix/Signals.inc:405:1 #4 0x7f9d2063d5e0 __restore_rt (/lib64/libpthread.so.0+0xf5e0) #5 0x7f9d1f1b61f7 raise (/lib64/libc.so.6+0x351f7) #6 0x7f9d1f1b78e8 abort (/lib64/libc.so.6+0x368e8) #7 0x04fdae7c bindingsErrorHandler(void*, std::__cxx11::basic_string, std::allocator > const&, bool) /iusers/ekeane1/workspaces/llvm-project/llvm/lib/Support/ErrorHandling.cpp:222:55 #8 0x08bdee51 fillAtomicQualLoc(clang::AtomicTypeLoc, clang::DeclaratorChunk const&) /iusers/ekeane1/workspaces/llvm-project/clang/lib/Sema/SemaType.cpp:6143:80 #9 0x08beeaaf clang::TypeLocVisitor<(anonymous namespace)::DeclaratorLocFiller, void>::VisitVectorTypeLoc(clang::VectorTypeLoc) /iusers/ekeane1/workspaces/llvm-project/build/tools/clang/include/clang/AST/TypeNodes.inc:77:1 #10 0x08becc8b clang::TypeLocVisitor<(anonymous namespace)::DeclaratorLocFiller, void>::Visit(clang::UnqualTypeLoc) /iusers/ekeane1/workspaces/llvm-project/build/tools/clang/include/clang/AST/TypeNodes.inc:77:1 #11 0x08bdf673 GetTypeSourceInfoForDeclarator((anonymous namespace)::TypeProcessingState&, clang::QualType, clang::TypeSourceInfo*) /iusers/ekeane1/workspaces/llvm-project/clang/lib/Sema/SemaType.cpp:6254:36 #12 0x08bdcb2d GetFullTypeForDeclarator((anonymous namespace)::TypeProcessingState&, clang::QualType, clang::TypeSourceInfo*) /iusers/ekeane1/workspaces/llvm-project/clang/lib/Sema/SemaType.cpp:5659:56 #13 0x08bdcc1c clang::Sema::GetTypeForDeclarator(clang::Declarator&, clang::Scope*) /iusers/ekeane1/workspaces/llvm-project/clang/lib/Sema/SemaType.cpp:5678:34 #14 0x0810b845 clang::Sema::HandleDeclarator(clang::Scope*, clang::Declarator&, llvm::MutableArrayRef) /iusers/ekeane1/workspaces/llvm-project/clang/lib/Sema/SemaDecl.cpp:5759:47 #15 0x0810a7e0 clang::Sema::ActOnDeclarator(clang::Scope*, clang::Declarator&) /iusers/ekeane1/workspaces/llvm-project/clang/lib/Sema/SemaDecl.cpp:5547:31 #16 0x07e42e09 clang::Parser::ParseDeclarationAfterDeclaratorAndAttributes(clang::Declarator&, clang::Parser::ParsedTemplateInfo const&, clang::Parser::ForRangeInit*) /iusers/ekeane1/workspaces/llvm-project/clang/lib/Parse/ParseDecl.cpp:2216:14 #17 0x07e42430 clang::Parser::ParseDeclGroup(clang::ParsingDeclSpec&, clang::DeclaratorContext, clang::SourceLocation*, clang::Parser::ForRangeInit*) /iusers/ekeane1/workspaces/llvm-project/clang/lib/Parse/ParseDecl.cpp:2039:35 #18 0x07e23db8 clang::Parser::ParseDeclOrFunctionDefInternal(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec&, clang::AccessSpecifier) /iusers/ekeane1/workspaces/llvm-project/clang/lib/Parse/Parser.cpp:1135:1 #19 0x07e23e72 clang::Parser::ParseDeclarationOrFunctionDefinition(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec*, clang::AccessSpecifier) /iusers/ekeane1/workspaces/llvm-project/clang/lib/Parse/Parser.cpp:1150:57 #20 0x07e23348 clang::Parser::ParseExternalDeclaration(clang
[llvm-bugs] [Bug 48541] New: [clang-analyzer] False report about moved-from object with coroutines
https://bugs.llvm.org/show_bug.cgi?id=48541
Bug ID: 48541
Summary: [clang-analyzer] False report about moved-from object
with coroutines
Product: clang
Version: trunk
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P
Component: Static Analyzer
Assignee: dcough...@apple.com
Reporter: dmitry.poluk...@gmail.com
CC: dcough...@apple.com, llvm-bugs@lists.llvm.org
Minimal reproducer is a bit long due to coroutine boilerplate
https://godbolt.org/z/P3P6ax:
#include
namespace std {
namespace experimental {
template
struct coroutine_traits { using promise_type = typename Ret::promise_type; };
template
struct coroutine_handle {
static coroutine_handle from_address(void *) noexcept;
};
template <>
struct coroutine_handle {
template
coroutine_handle(coroutine_handle) noexcept;
static coroutine_handle from_address(void *);
};
struct suspend_always {
bool await_ready() noexcept { return false; }
void await_suspend(coroutine_handle<>) noexcept {}
void await_resume() noexcept {}
};
struct suspend_never {
bool await_ready() { return true; }
void await_suspend(coroutine_handle<>) {}
void await_resume() {}
};
} // namespace experimental
} // namespace std
namespace folly {
namespace coro {
using std::experimental::suspend_always;
using std::experimental::suspend_never;
using std::experimental::coroutine_handle;
template
struct Task {
struct promise_type {
Task get_return_object();
suspend_always initial_suspend();
suspend_always final_suspend() noexcept;
void return_value(T);
void unhandled_exception();
auto yield_value(Task) { return final_suspend(); }
};
bool await_ready() { return false; }
void await_suspend(coroutine_handle<>) {}
T await_resume();
};
template<>
struct Task {
struct promise_type {
Task get_return_object();
suspend_always initial_suspend();
suspend_always final_suspend();
void return_void();
void unhandled_exception();
auto yield_value(Task) { return final_suspend(); }
};
bool await_ready() { return false; }
void await_suspend(coroutine_handle<>) {}
void await_resume() {}
};
}} // namespace folly::coro
folly::coro::Task foo() {
std::string operationsMap;
co_return operationsMap;
}
Command line options: -std=c++17 -fcoroutines-ts
:76:13: warning: Moved-from object 'operationsMap' of type
'std::basic_string' is moved [clang-analyzer-cplusplus.Move]
co_return operationsMap;
^
:76:13: note: Object 'operationsMap' of type 'std::basic_string' is
left in a valid but unspecified state after move
:76:13: note: Moved-from object 'operationsMap' of type
'std::basic_string' is moved
1 warning generated.
--
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 28709 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in GetFullTypeForDeclarator
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #1 on issue 28709 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in GetFullTypeForDeclarator https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=28709#c1 ClusterFuzz testcase 4647621188780032 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202012160609:202012170612 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 28711 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::Sema::CppLookupName
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #1 on issue 28711 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::Sema::CppLookupName https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=28711#c1 ClusterFuzz testcase 5179402254155776 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202012160609:202012170612 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 48386] LLVM 11.0.0 always rebuilds due to VCS revision
https://bugs.llvm.org/show_bug.cgi?id=48386 Tom Stellard changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED Fixed By Commit(s)|6e890ec7beb0874464a0af9f84e |6e890ec7beb0874464a0af9f84e |41a987f968b23 |41a987f968b23 d104e582838f --- Comment #5 from Tom Stellard --- Merged: d104e582838f -- 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 47800] [meta] 11.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=47800 Bug 47800 depends on bug 48386, which changed state. Bug 48386 Summary: LLVM 11.0.0 always rebuilds due to VCS revision https://bugs.llvm.org/show_bug.cgi?id=48386 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 47711] Backport rGca05601 to 11.0
https://bugs.llvm.org/show_bug.cgi?id=47711 Tom Stellard changed: What|Removed |Added Fixed By Commit(s)|ca05601 |ca05601 ||f5f8d86dc4c91ef492b919edf98 ||335d4d09188a8 Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #13 from Tom Stellard --- Merged: f5f8d86dc4c91ef492b919edf98335d4d09188a8 -- 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 47800] [meta] 11.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=47800 Bug 47800 depends on bug 47711, which changed state. Bug 47711 Summary: Backport rGca05601 to 11.0 https://bugs.llvm.org/show_bug.cgi?id=47711 What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 48542] New: ld.lld on Windows does not accept -Bstatic aliases
https://bugs.llvm.org/show_bug.cgi?id=48542 Bug ID: 48542 Summary: ld.lld on Windows does not accept -Bstatic aliases Product: lld Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: unassignedb...@nondot.org Reporter: d...@adrian-ebeling.de CC: llvm-bugs@lists.llvm.org, smithp...@googlemail.com According to ld.lld --help, there are three aliases for --Bstatic: $ ld.lld --help | grep Bstatic --Bstatic Do not link against shared libraries --dnAlias for --Bstatic --non_sharedAlias for --Bstatic --staticAlias for --Bstatic However, only --Bstatic works (version with one dash is also accepted): $ ld.lld -m i386pep --dn main.o -o main.exe lld: error: unknown argument: --dn $ ld.lld -m i386pep --non_shared main.o -o main.o2 lld: error: unknown argument: --non_shared $ ld.lld -m i386pep --static main.o -o main.o2 lld: error: unknown argument: --static Current version on my PC is "LLD 10.0.0 (compatible with GNU linkers)", but I also tried with 11.0.0. -- 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 28755 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::DeclContext::lookup
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-17 Type: Bug New issue 28755 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::DeclContext::lookup https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=28755 Detailed Report: https://oss-fuzz.com/testcase?key=5100954152206336 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffe142c1cc8 Crash State: clang::DeclContext::lookup LookupDirect clang::Sema::LookupQualifiedName Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201908200325:201908210335 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5100954152206336 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 48206] insertDebugValuesForPHIs() re-orders how assignments appear
https://bugs.llvm.org/show_bug.cgi?id=48206 Nabeel Omer changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 31268] Umbrella: debug info for optimized code
https://bugs.llvm.org/show_bug.cgi?id=31268 Bug 31268 depends on bug 48206, which changed state. Bug 48206 Summary: insertDebugValuesForPHIs() re-orders how assignments appear https://bugs.llvm.org/show_bug.cgi?id=48206 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 48544] New: Bounds check not eliminated
https://bugs.llvm.org/show_bug.cgi?id=48544
Bug ID: 48544
Summary: Bounds check not eliminated
Product: libraries
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: Scalar Optimizations
Assignee: unassignedb...@nondot.org
Reporter: jmuizel...@mozilla.com
CC: llvm-bugs@lists.llvm.org
#include
char foo(char* data, size_t len, size_t i, size_t j) {
if (i < len && j <= i) {
if (j < len) {
return data[j];
} else {
exit(1);
}
} else {
return 0;
}
}
compiles to:
foo(char*, unsigned long, unsigned long, unsigned long):
cmp rdx, rsi
jnb .L4
cmp rdx, rcx
jb .L4
cmp rsi, rcx
jbe .L3
movzx eax, BYTE PTR [rdi+rcx]
ret
.L4:
xor eax, eax
ret
.L3:
pushrax
mov edi, 1
callexit
The call to exit should be eliminated.
--
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 48545] New: Access failure to own private inherited constructor for prvalue direct-initialization
https://bugs.llvm.org/show_bug.cgi?id=48545
Bug ID: 48545
Summary: Access failure to own private inherited constructor
for prvalue direct-initialization
Product: clang
Version: 11.0
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: C++17
Assignee: unassignedclangb...@nondot.org
Reporter: e...@catmur.co.uk
CC: blitzrak...@gmail.com, erik.pilking...@gmail.com,
llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk
struct B {
void f();
private:
B(int, int = 0);
};
struct D : B { using B::B; };
void B::f() {
auto a = D{0};
auto b = D(0);
auto c = D(0, 0);
D x{0};
D y(0);
D z(0, 0);
}
Accepts: b, x, y, z. Rejects: a, c.
MSVC accepts all in C++17 mode, rejects all in C++14 mode, which apparently [1]
is due to their interpretation of the C++14 as-published wording [2].
GCC accepts all since 7.1, previously rejects all.
1. https://stackoverflow.com/a/65327682/567292
2. http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2015/p0136r1.html
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 48511] ld64.lld.darwinnew linked v8_context_snapshot_generator doesn't run on macos 10.15.7 (and possibly other macos versions)
https://bugs.llvm.org/show_bug.cgi?id=48511 Nico Weber changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #14 from Nico Weber --- http://reviews.llvm.org/rG811444d7a173e696f975f8d41626f6809439f726 -- 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 48546] New: [LoopVectorization] Invalid code after interleaving add reduction
https://bugs.llvm.org/show_bug.cgi?id=48546
Bug ID: 48546
Summary: [LoopVectorization] Invalid code after interleaving
add reduction
Product: libraries
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Loop Optimizer
Assignee: unassignedb...@nondot.org
Reporter: congzhe...@gmail.com
CC: llvm-bugs@lists.llvm.org
The following C code generate an issue as follows:
int printf(const char *, ...);
int a, b, e;
char c, d;
int main() {
d = 19;
for (; d < 45; d++) {
char *f = &c;
*f &= 1;
e = b== 0 ?:a%b;
(*f)--;
}
printf("%d\n", c);
}
This code compiled with the following flag causes a bug:
clang test.c -O2 && ./a.out
Output: 254
The correct output is '0'.
Upon further investigation, the bug is caused by the interleaving of the Loop
Vectorizer.
The follwing command produces correct code:
clang test.c -O2 -mllvm -force-vector-interleave=1 && ./a.out
The root cause is not clear yet, but it seems like there is an add reduction
that the loop vectorization legalily determines that it is safe to vectorize,
but in this case it generates an incorrect result.
The IVDescriptor.cpp:629, the function call to AddReductionVar for Add
reduction finds this to be a signed i1 add reduction, which to me seems like an
invalid type.
The test file reduction-small-size.ll is important for this because it has the
same type if reduction, but the interleaving is forced to 1, if we force it to
2 we have an invalid 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] [Bug 48547] New: LLD as a library behaves incorrectly about exiting
https://bugs.llvm.org/show_bug.cgi?id=48547 Bug ID: 48547 Summary: LLD as a library behaves incorrectly about exiting Product: lld Version: unspecified Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: unassignedb...@nondot.org Reporter: dpldob...@protonmail.com CC: llvm-bugs@lists.llvm.org, smithp...@googlemail.com lld is explicitly documented as invokable as a library at https://lld.llvm.org/ : "You can embed LLD in your program to eliminate dependencies on external linkers. All you have to do is to construct object files and command line arguments just like you would do to invoke an external linker and then call the linker’s main function, lld::elf::link, from your code." However, using this method requires passing a Boolean parameter for exiting. If it's true, the entire process dies right away. If it's false, it's left hanging unless llvm::llvm_shutdown() is manually called. This isn't the proper behaviour of a library as the calls should just to the job and not have the caller handle such 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 48548] New: LLD as a library doesn't reset its global states across calls
https://bugs.llvm.org/show_bug.cgi?id=48548 Bug ID: 48548 Summary: LLD as a library doesn't reset its global states across calls Product: lld Version: unspecified Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: unassignedb...@nondot.org Reporter: dpldob...@protonmail.com CC: llvm-bugs@lists.llvm.org, smithp...@googlemail.com lld is explicitly documented as invokable as a library at https://lld.llvm.org/ : "You can embed LLD in your program to eliminate dependencies on external linkers. All you have to do is to construct object files and command line arguments just like you would do to invoke an external linker and then call the linker’s main function, lld::elf::link, from your code." However, LLD uses a global state which isn't reset across invocations. The problem is detailed in more detail at https://github.com/ziglang/zig/issues/3825 . I guess the reporter meant items such as https://github.com/llvm/llvm-project/blob/main/lld/MachO/Driver.cpp#L695 or https://github.com/llvm/llvm-project/blob/main/lld/MachO/Driver.cpp#L777 . The latter example is especially showing because I have to call the contents of InitLLVM() myself as I compile before linking so LLD as a library should be smart not to call it a second time. -- 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 48517] Accidental equality of classes templated by pointer to local static constant of templated function
https://bugs.llvm.org/show_bug.cgi?id=48517 Richard Smith changed: What|Removed |Added Status|RESOLVED|REOPENED CC||dblai...@gmail.com Resolution|FIXED |--- --- Comment #3 from Richard Smith --- The remaining issue looks like a bug in debug information generation. If you build with -g0, the problem goes away (and, disturbingly, if you build with -g, the debug info symbols get the proper mangling and the actually-referenced-from-the-code symbols get the wrong .1 / .2 manglings). It's not clear to me if the problem goes deeper than debug info generation, 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 48549] New: Should LLD not set the RELRO program header when targeting -maarch64elf?
https://bugs.llvm.org/show_bug.cgi?id=48549 Bug ID: 48549 Summary: Should LLD not set the RELRO program header when targeting -maarch64elf? Product: lld Version: unspecified Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: ELF Assignee: unassignedb...@nondot.org Reporter: ndesaulni...@google.com CC: i...@maskray.me, kristof.be...@arm.com, llvm-bugs@lists.llvm.org, mask...@google.com, smithp...@googlemail.com, srhi...@google.com Blocks: 4068 In https://lore.kernel.org/lkml/20201214231827.gg8...@bubble.grove.modra.org/ Alan Modra notes about BFD: The default linker emulation for an aarch64-linux ld.bfd is -maarch64linux, the default for an aarch64-elf linker is -maarch64elf. They are not equivalent. If you choose -maarch64elf you get an emulation that doesn't support -z relro. Should LLD not set the RELRO program header when targeting -maarch64elf to better match compatibility with GNU BFD? 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] Issue 28760 in oss-fuzz: llvm:llvm-opt-fuzzer--x86_64-simplifycfg: ASSERT: isa(User) && "All external users must be PHI's."
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-17 Type: Bug New issue 28760 by ClusterFuzz-External: llvm:llvm-opt-fuzzer--x86_64-simplifycfg: ASSERT: isa(User) && "All external users must be PHI's." https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=28760 Detailed Report: https://oss-fuzz.com/testcase?key=4879574865412096 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: llvm-opt-fuzzer--x86_64-simplifycfg Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: isa(User) && "All external users must be PHI's." llvm::FoldBranchToCommonDest llvm::FoldBranchToCommonDest Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202012140607:202012150624 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4879574865412096 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 35063] libc++ says my user-defined type has an operator<< during sfinae - libstdc++ works as expected
https://bugs.llvm.org/show_bug.cgi?id=35063 Richard Smith changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Richard Smith --- Looks like this was in Clang 3.9 onwards. -- 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 35077] Incorrect overload resolution dependent on instantiation order
https://bugs.llvm.org/show_bug.cgi?id=35077 Richard Smith changed: What|Removed |Added CC||richard-l...@metafoo.co.uk Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #1 from Richard Smith --- Looks like this was fixed in Clang 10. -- 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 40321] declaring a template instance as friend makes all instances of the template as friend
https://bugs.llvm.org/show_bug.cgi?id=40321 Richard Smith changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #1 from Richard Smith --- Looks like PR38980: somehow access checking during class template partial specialization selection is not working quite right. *** This bug has been marked as a duplicate of bug 38980 *** -- 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 45782] Unused arguments in alias template specialisation are not treated as substitution failure
https://bugs.llvm.org/show_bug.cgi?id=45782 Richard Smith changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Richard Smith --- *** This bug has been marked as a duplicate of bug 46791 *** -- 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 45248] arch/arm/kernel/sleep.S:149:20: error: invalid reassignment of non-absolute variable 'up_b_offset' in '.equ' directive
https://bugs.llvm.org/show_bug.cgi?id=45248 Jian Cai changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #1 from Jian Cai --- Fixed on Linux https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a780e485b5768e78aef087502499714901b68cc4 -- 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 46679] [AARCH64] "expected assembly-time absolute expression"
https://bugs.llvm.org/show_bug.cgi?id=46679 Jian Cai changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Jian Cai --- Fixed in https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git/commit/?id=966a0acce2fc and https://reviews.llvm.org/rG415a4fbea7c1a39c780caa3cb7287fe09c5267d2. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 4068] [Meta] Compiling the Linux kernel with clang
https://bugs.llvm.org/show_bug.cgi?id=4068 Bug 4068 depends on bug 46679, which changed state. Bug 46679 Summary: [AARCH64] "expected assembly-time absolute expression" https://bugs.llvm.org/show_bug.cgi?id=46679 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43795] error: expected absolute expression
https://bugs.llvm.org/show_bug.cgi?id=43795 Jian Cai changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #5 from Jian Cai --- https://reviews.llvm.org/D69411 accepted and merged. -- 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 28764 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::DiagnosticsEngine::DiagState::getOrAddMapping
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-18 Type: Bug New issue 28764 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::DiagnosticsEngine::DiagState::getOrAddMapping https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=28764 Detailed Report: https://oss-fuzz.com/testcase?key=5085872710090752 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7fff2d302fb8 Crash State: clang::DiagnosticsEngine::DiagState::getOrAddMapping clang::DiagnosticIDs::getDiagnosticSeverity clang::DiagnosticIDs::getDiagnosticLevel Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202012150624:202012160609 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5085872710090752 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 28771 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::StmtVisitorBase::Visit
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-18 Type: Bug New issue 28771 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::StmtVisitorBase::Visit https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=28771 Detailed Report: https://oss-fuzz.com/testcase?key=4785418277093376 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7fff4758cac8 Crash State: clang::StmtVisitorBase::Visit clang::EvaluatedExprVisitorBase::VisitStm 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=4785418277093376 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
