[llvm-bugs] [Bug 47911] New: Compilation for 32-bit Windows crashes
https://bugs.llvm.org/show_bug.cgi?id=47911 Bug ID: 47911 Summary: Compilation for 32-bit Windows crashes Product: new-bugs Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: albert.te...@gmail.com CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org Created attachment 24080 --> https://bugs.llvm.org/attachment.cgi?id=24080&action=edit Information about build process I tried to compile the master version (1e32df2f91f1aa1f8cd400ce50a621578fa0534e) for with the 32-bit Microsoft Visual Studio compiler (on 64 bit Windows 10) but got a crash in the compilation with the request to submit as bug report. I've added the information about the build process in an attachment -- 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 47912] New: Warnings when compiling with 32-bit windows compiler
https://bugs.llvm.org/show_bug.cgi?id=47912 Bug ID: 47912 Summary: Warnings when compiling with 32-bit windows compiler Product: new-bugs Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: albert.te...@gmail.com CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org Created attachment 24081 --> https://bugs.llvm.org/attachment.cgi?id=24081&action=edit Details of complation and warnings When I compile my simple file: #include #include "clang/Tooling/CompilationDatabase.h" #include "clang/Tooling/Tooling.h" with the 32-bit Microsoft Visual studio (on Windows 10 64-bit) I get a lot of warnings like: E:\Programs\LLVM\llvm-project\llvm\include\llvm/Support/type_traits.h(79): warning C4624: 'llvm::detail::copy_construction_triviality_helper': destructor was implicitly defined as deleted with [ T=std::string ] The full details can be found in the attachment. In my case it happens with the 9.0.1. version but I see the same problem with the current master (1e32df2f91f1aa1f8cd400ce50a621578fa0534e) (could not complete this build as there was a compilation crash of LLVM / clang) and I've had a report that it also happens with the 5.0.0 version so it looks like a long standing problem. -- 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 47913] New: OS selection box in bugzilla
https://bugs.llvm.org/show_bug.cgi?id=47913 Bug ID: 47913 Summary: OS selection box in bugzilla Product: Bugzilla Admin Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: Mail Assignee: unassignedb...@nondot.org Reporter: albert.te...@gmail.com CC: kristof.be...@gmail.com, llvm-bugs@lists.llvm.org, r...@google.com, t.p.northo...@gmail.com Would be nice to have in the OS selection box also "Windows 10" in the bugzilla GUI -- 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 47914] New: Compilation master (691eb814c1ae38d5015bf070dfed3fd54d542582 ) on Cygwin
https://bugs.llvm.org/show_bug.cgi?id=47914 Bug ID: 47914 Summary: Compilation master (691eb814c1ae38d5015bf070dfed3fd54d542582 ) on Cygwin Product: new-bugs Version: trunk Hardware: PC OS: other Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: albert.te...@gmail.com CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org I tried to compile the master version (691eb814c1ae38d5015bf070dfed3fd54d542582 ) on Cygwin with GCC 9.3.0 and got the error: [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/CrashRecoveryContext.cpp.o /cygdrive/e/Programs/LLVM/llvm-project/llvm/lib/Support/CrashRecoveryContext.cpp:348:25: error: elements of array ‘sigaction PrevActions [6]’ have incomplete type 348 | static struct sigaction PrevActions[NumSignals]; | ^~~ /cygdrive/e/Programs/LLVM/llvm-project/llvm/lib/Support/CrashRecoveryContext.cpp:348:25: error: storage size of ‘PrevActions’ isn’t known /cygdrive/e/Programs/LLVM/llvm-project/llvm/lib/Support/CrashRecoveryContext.cpp: In function ‘void CrashRecoverySignalHandler(int)’: /cygdrive/e/Programs/LLVM/llvm-project/llvm/lib/Support/CrashRecoveryContext.cpp:374:3: error: ‘sigemptyset’ was not declared in this scope 374 | sigemptyset(&SigMask); | ^~~ /cygdrive/e/Programs/LLVM/llvm-project/llvm/lib/Support/CrashRecoveryContext.cpp:375:3: error: ‘sigaddset’ was not declared in this scope 375 | sigaddset(&SigMask, Signal); | ^ /cygdrive/e/Programs/LLVM/llvm-project/llvm/lib/Support/CrashRecoveryContext.cpp:376:15: error: ‘SIG_UNBLOCK’ was not declared in this scope 376 | sigprocmask(SIG_UNBLOCK, &SigMask, nullptr); | ^~~ /cygdrive/e/Programs/LLVM/llvm-project/llvm/lib/Support/CrashRecoveryContext.cpp:376:3: error: ‘sigprocmask’ was not declared in this scope 376 | sigprocmask(SIG_UNBLOCK, &SigMask, nullptr); | ^~~ /cygdrive/e/Programs/LLVM/llvm-project/llvm/lib/Support/CrashRecoveryContext.cpp: In function ‘void installExceptionOrSignalHandlers()’: /cygdrive/e/Programs/LLVM/llvm-project/llvm/lib/Support/CrashRecoveryContext.cpp:393:20: error: aggregate ‘sigaction Handler’ has incomplete type and cannot be defined 393 | struct sigaction Handler; |^~~ /cygdrive/e/Programs/LLVM/llvm-project/llvm/lib/Support/CrashRecoveryContext.cpp:396:3: error: ‘sigemptyset’ was not declared in this scope 396 | sigemptyset(&Handler.sa_mask); | ^~~ /cygdrive/e/Programs/LLVM/llvm-project/llvm/lib/Support/CrashRecoveryContext.cpp:399:52: error: invalid use of incomplete type ‘struct sigaction’ 399 | sigaction(Signals[i], &Handler, &PrevActions[i]); |^ /cygdrive/e/Programs/LLVM/llvm-project/llvm/lib/Support/CrashRecoveryContext.cpp:348:15: note: forward declaration of ‘struct sigaction’ 348 | static struct sigaction PrevActions[NumSignals]; | ^ /cygdrive/e/Programs/LLVM/llvm-project/llvm/lib/Support/CrashRecoveryContext.cpp: In function ‘void uninstallExceptionOrSignalHandlers()’: /cygdrive/e/Programs/LLVM/llvm-project/llvm/lib/Support/CrashRecoveryContext.cpp:406:51: error: invalid use of incomplete type ‘struct sigaction’ 406 | sigaction(Signals[i], &PrevActions[i], nullptr); | ^ /cygdrive/e/Programs/LLVM/llvm-project/llvm/lib/Support/CrashRecoveryContext.cpp:348:15: note: forward declaration of ‘struct sigaction’ 348 | static struct sigaction PrevActions[NumSignals]; | ^ make[2]: *** [lib/Support/CMakeFiles/LLVMSupport.dir/build.make:460: lib/Support/CMakeFiles/LLVMSupport.dir/CrashRecoveryContext.cpp.o] Error 1 make[1]: *** [CMakeFiles/Makefile2:14907: lib/Support/CMakeFiles/LLVMSupport.dir/all] Error 2 make: *** [Makefile:172: all] Error 2 -- 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 47915] New: [LoopInterchange] Loops should not interchanged due to dependencies
https://bugs.llvm.org/show_bug.cgi?id=47915
Bug ID: 47915
Summary: [LoopInterchange] Loops should not interchanged due to
dependencies
Product: libraries
Version: trunk
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P
Component: Loop Optimizer
Assignee: unassignedb...@nondot.org
Reporter: chenge...@huawei.com
CC: llvm-bugs@lists.llvm.org
$ clang -mllvm -enable-loopinterchange -O2 reproducer.c -w && ./a.out
4096
0
4096
0
$ clang -O0 reproducer.c -w && ./a.out
4096
4096
4096
4096
reproducer.c:
#include
int a;
int c[4][4];
*f = &a;
void test_deps() {
for (int i = 0; i <= 3; i++) {
for (int j = 0; j <= 3; j++) {
*f ^= 0x1000;
c[j][i] = *f;
}
}
}
main() {
test_deps();
for (int k = 0; k < 4; k++)
printf("%d\n", c[0][k]);
}
--
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 47916] New: fatal error: error in backend: Cannot select: t184: v2i64 = PPCISD::SCALAR_TO_VECTOR_PERMUTED t107
https://bugs.llvm.org/show_bug.cgi?id=47916
Bug ID: 47916
Summary: fatal error: error in backend: Cannot select: t184:
v2i64 = PPCISD::SCALAR_TO_VECTOR_PERMUTED t107
Product: libraries
Version: 11.0
Hardware: Other
OS: FreeBSD
Status: NEW
Severity: release blocker
Priority: P
Component: Backend: PowerPC
Assignee: unassignedb...@nondot.org
Reporter: pku...@anongoth.pl
CC: llvm-bugs@lists.llvm.org, nemanja.i@gmail.com
FreeBSD head, LLVM 11.0.0, powerpc64le
Release blocker, because it breaks bootstrapping openjdk8 with default flags.
Test case:
class a;
class b {
public:
a *operator->();
};
class c {
public:
void m_fn1(int d) { e = d; }
void f(int d) { g = d; }
int e;
int g;
};
class a {
public:
c *h();
};
b i;
void j(unsigned d, int *k, unsigned *l) {
c *m = i->h();
while (d--) {
m->m_fn1(*k++);
m->f(*l++);
m++;
}
}
Compile with:
/usr/bin/clang++ -cc1 -triple powerpc64le-unknown-freebsd13.0 -emit-obj
-target-cpu pwr7 -O2 -vectorize-loops classFileParser-e4fcc9.cpp
Result:
fatal error: error in backend: Cannot select: t184: v2i64 =
PPCISD::SCALAR_TO_VECTOR_PERMUTED t107
t107: i64,ch = load<(load 8 from %ir.scevgep108, align 4, !tbaa !2,
!alias.scope !6)> t0, t14, undef:i64
t14: i64 = add t9, Constant:i64<8>
t9: i64 = add t4, t8
t4: i64,ch = CopyFromReg t0, Register:i64 %50
t3: i64 = Register %50
t8: i64,ch = CopyFromReg t0, Register:i64 %8
t7: i64 = Register %8
t13: i64 = Constant<8>
t11: i64 = undef
In function: _Z1jjPiPj
--
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 26216 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::Parser::ParseStatementOrDeclarationAfterAttributes
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #1 on issue 26216 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::Parser::ParseStatementOrDeclarationAfterAttributes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26216#c1 ClusterFuzz testcase 5144332027559936 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202010190618:202010200603 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 26192 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in llvm::detail::IEEEFloat::convertFromStringSpecials
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #1 on issue 26192 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in llvm::detail::IEEEFloat::convertFromStringSpecials https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26192#c1 ClusterFuzz testcase 5423925506605056 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202010190618:202010200603 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 47917] New: Provide release tarballs along LLVM releases
https://bugs.llvm.org/show_bug.cgi?id=47917 Bug ID: 47917 Summary: Provide release tarballs along LLVM releases Product: libclc Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: unassignedb...@nondot.org Reporter: aaronpuch...@alice-dsl.net CC: llvm-bugs@lists.llvm.org, tstel...@redhat.com Currently there are no release tarballs for libclc, at least I can't see any under https://github.com/llvm/llvm-project/releases/tag/llvmorg-11.0.0 and https://libclc.llvm.org/ just says you have to clone the monorepo. Could we have tarballs for libclc alongside with every LLVM release? I know that libclc has a different versioning scheme, but libc++ is also largely backwards-compatible and is still at SO version 1.0. Still we have tarballs for that. -- 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 26200 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::StmtVisitorBase::Visit
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #1 on issue 26200 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::StmtVisitorBase::Visit https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26200#c1 ClusterFuzz testcase 5761703847133184 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202010190618:202010200603 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 26283 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::Lexer::Lex
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #1 on issue 26283 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::Lexer::Lex https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26283#c1 ClusterFuzz testcase 4792468803158016 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202010190618:202010200603 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 47918] New: parseSystemVersionPList assumes three numbers in the version number
https://bugs.llvm.org/show_bug.cgi?id=47918 Bug ID: 47918 Summary: parseSystemVersionPList assumes three numbers in the version number Product: compiler-rt Version: unspecified Hardware: Macintosh OS: MacOS X Status: NEW Severity: normal Priority: P Component: compiler-rt Assignee: unassignedb...@nondot.org Reporter: a...@drissman.com CC: llvm-bugs@lists.llvm.org In an (non-public) Chromium bug, https://crbug.com/1138707, we see a crash in parseSystemVersionPList on macOS Big Sur: std::__1::__throw_out_of_range(char const*) + stdexcept:0 abort_message + abort_message.cpp:32 parseSystemVersionPList + extensions::CpuInfoProvider::QueryInfo() + cpu_info_provider.cc:44 The `extensions` code is from Chromium; parseSystemVersionPList appears to be the version from LLVM’s compiler-rt/lib/builtins/os_version_check.c. If we look at the implementation of parseSystemVersionPList on LLVM ToT we see (https://github.com/llvm/llvm-project/blob/master/compiler-rt/lib/builtins/os_version_check.c#L193): sscanf(VersionStr, "%d.%d.%d", &GlobalMajor, &GlobalMinor, &GlobalSubminor); It’s parsing the field “ProductVersion” from /System/Library/CoreServices/SystemVersion.plist. If we look at that file on Big Sur (20A5395g in this case) we see: ProductVersion 11.0 and there are only two numbers and one period. I can’t say with 100% certainty that it is that specific line, but something appears to occasionally crash Chromium on Big Sur inside a compiler-added parseSystemVersionPList() call. -- 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 26127 in oss-fuzz: llvm:clang-objc-fuzzer: Stack-overflow in clang::DeclSpec::Finish
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #1 on issue 26127 by ClusterFuzz-External: llvm:clang-objc-fuzzer: Stack-overflow in clang::DeclSpec::Finish https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26127#c1 ClusterFuzz testcase 565051791872 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202010190618:202010200603 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 26205 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::NumericLiteralParser::GetFloatValue
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #1 on issue 26205 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::NumericLiteralParser::GetFloatValue https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26205#c1 ClusterFuzz testcase 5675278032175104 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202010190618:202010200603 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 26129 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::DiagnosticIDs::ProcessDiag
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #1 on issue 26129 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::DiagnosticIDs::ProcessDiag https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26129#c1 ClusterFuzz testcase 5985045720072192 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202010190618:202010200603 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 47533] LLD is doing undesirable identical code folding when invoked with -Wl, --icf=safe
https://bugs.llvm.org/show_bug.cgi?id=47533 Fangrui Song changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #5 from Fangrui Song --- *** This bug has been marked as a duplicate of bug 36272 *** -- 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 47919] New: image2d_depth_t shouldn't be available in OpenCL 1.1
https://bugs.llvm.org/show_bug.cgi?id=47919
Bug ID: 47919
Summary: image2d_depth_t shouldn't be available in OpenCL 1.1
Product: clang
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: OpenCL
Assignee: unassignedclangb...@nondot.org
Reporter: marco.antogn...@arm.com
CC: anastasia.stul...@arm.com, llvm-bugs@lists.llvm.org
When compiling the following for OpenCL 1.1 Clang doesn't reject the usage of
image2d_depth_t.
float bar(read_only image2d_depth_t image, sampler_t sampler, int2 coord) {
return read_imagef(image, sampler, coord);
}
https://godbolt.org/z/MsjKjr
The image2d_depth_t type
- is defined in extension cl_khr_depth_images for OpenCL 1.2 (and the
extension is disabled by default), and
- is a core feature in OpenCL 2.0 and later.
Interestingly, Clang accepts this program when using -fdeclare-opencl-builtins.
It is rejected when using `opencl-c.h`, but for another (valid) reason: the
overload of read_imagef using this image type is not available.
Somewhat related to Bug 47882.
--
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 36778] Use-list order not preserved for some constant values
https://bugs.llvm.org/show_bug.cgi?id=36778 David Stenberg changed: What|Removed |Added Status|CONFIRMED |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 47913] OS selection box in bugzilla
https://bugs.llvm.org/show_bug.cgi?id=47913 Reid Kleckner changed: What|Removed |Added Resolution|--- |WONTFIX Status|NEW |RESOLVED --- Comment #1 from Reid Kleckner --- That would be useful, but our efforts are focused on migrating from Bugzilla to GitHub. Unless we have a plan to migrate the additional information as tags for github issues, it doesn't seem worth changing the Bugzilla schema at this 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 47920] New: Unnecessary break when line is at line length and ends with NS_SWIFT_NAME()
https://bugs.llvm.org/show_bug.cgi?id=47920 Bug ID: 47920 Summary: Unnecessary break when line is at line length and ends with NS_SWIFT_NAME() Product: clang Version: trunk Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: Formatter Assignee: unassignedclangb...@nondot.org Reporter: bhamilto...@gmail.com CC: djas...@google.com, kli...@google.com, llvm-bugs@lists.llvm.org https://reviews.llvm.org/D89425 introduces a bug for lines that are at the line length limit and end with `NS_SWIFT_NAME()` or `CF_SWIFT_NAME()`. For example, with `NS_SWIFT_NAME(foo(bar:))`, before the diff, the colon after `foo(bar:` had `L=97`: ``` M=0 C=0 T=ObjCMethodExpr S=0 F=0 B=0 BK=0 P=63 Name=colon L=97 PPK=2 FakeLParens= FakeRParens=1 II=0x0 Text=':' ``` and after, it has `L=98`: M=0 C=0 T=Unknown S=1 F=1 B=0 BK=0 P=43 Name=colon L=98 PPK=2 FakeLParens= FakeRParens=0 II=0x0 Text=':' `L` is `Line.Level`. I don't understand why it would increase by 1 here. -- 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 47921] New: va_arg() with type 'id' produces incorrect output
https://bugs.llvm.org/show_bug.cgi?id=47921 Bug ID: 47921 Summary: va_arg() with type 'id' produces incorrect output Product: clang Version: 8.0 Hardware: Other OS: OpenBSD Status: NEW Keywords: compile-fail Severity: normal Priority: P Component: C Assignee: unassignedclangb...@nondot.org Reporter: antho...@gmx.co.uk CC: blitzrak...@gmail.com, dgre...@apple.com, erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk Created attachment 24084 --> https://bugs.llvm.org/attachment.cgi?id=24084&action=edit This reproduces the bug, compile with -DUSE_HACK to apply the workaround mentioned. When I use va_arg, providing type 'id', the return values are incorrect. In the source code I have attached, I have a function taking a variable number of arguments of type 'id', I pass in 3 arguments, and return the third out of it. The value of this third agument returned should be equal to the third argument passed in. However it is not. When I instead change the type passed to va_arg() to 'void*', (I guess this works as they're both the same size?), I get the expected result. I've tried to boil my example code down to demonstrate it as simple as possible, however this behavior is present when I try to use the GNUstep system too, and indeed the 'fix' of replacing occurances of va_arg(*, id) with va_arg(*, void*) results in a completely stable system. Here's an example shell session using the code I have attached: netty$ cc bug.m -o bug netty$ ./bug netty$ echo $? 1 netty$ cc -DUSE_HACK bug.m -o bug netty$ ./bug netty$ echo $? 0 netty$ cc -v OpenBSD clang version 8.0.1 (tags/RELEASE_801/final) (based on LLVM 8.0.1) Target: powerpc-unknown-openbsd6.7 Thread model: posix InstalledDir: /usr/bin netty$ uname -a OpenBSD netty.my.domain 6.7 GENERIC#714 macppc -- 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 47922] New: Suboptimal lowering of conditional binop identity
https://bugs.llvm.org/show_bug.cgi?id=47922 Bug ID: 47922 Summary: Suboptimal lowering of conditional binop identity Product: libraries Version: trunk Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: Backend: X86 Assignee: unassignedb...@nondot.org Reporter: laytonki...@gmail.com CC: craig.top...@gmail.com, llvm-bugs@lists.llvm.org, llvm-...@redking.me.uk, pengfei.w...@intel.com, spatel+l...@rotateright.com The x86 backend fails to notice when expanding selects/phis will cause things like addition of 0 and emits unnecessary instructions. examples: https://godbolt.org/z/j5onGK I would potentially be interested in looking into this, but I am fairly new to LLVM. This would be my first time working on one of the backends. If anyone could point me in the right direction as to where to begin, that would be great. -- 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 47923] New: __attribute__((warn_result_unused)) broken for ObjC Methods in Macros
https://bugs.llvm.org/show_bug.cgi?id=47923
Bug ID: 47923
Summary: __attribute__((warn_result_unused)) broken for ObjC
Methods in Macros
Product: clang
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: dmacl...@gmail.com
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org,
neeil...@live.com, richard-l...@metafoo.co.uk
Overview:
An Objective C call in a macro has its warning about unused results suppressed
which is different than a C function call. I would expect these to be
equivalent in this regard.
```
#import
__attribute__((warn_unused_result)) static id ReturnSomethingC() { return nil;
}
@interface TestClass : NSObject
+ (id)returnSomething __attribute__((warn_unused_result));
@end
@implementation TestClass
+ (id)returnSomething { return nil; }
@end
#define DOSOMETHING_OBJC [TestClass returnSomething]
#define DOSOMETHING_C ReturnSomethingC()
int main(int argc, const char * argv[]) {
@autoreleasepool {
[TestClass returnSomething]; // <-- Here I get the warning
ReturnSomethingC(); // <-- Here I get the warning
DOSOMETHING_C; // <-- Here I get the warning
DOSOMETHING_OBJC; // <-- How do I get a warning here?
}
return 0;
}
```
it appears that Objc Messages are considered after suppression
https://github.com/llvm/llvm-project/blob/89f7ccea6f6488c443655880229c54db1f180153/clang/lib/Sema/SemaStmt.cpp#L324
--
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 26539 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::DiagnosticIDs::isUnrecoverable
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-10-20 Type: Bug New issue 26539 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::DiagnosticIDs::isUnrecoverable https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26539 Detailed Report: https://oss-fuzz.com/testcase?key=5637772372869120 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffcc7588d98 Crash State: clang::DiagnosticIDs::isUnrecoverable clang::DiagnosticIDs::ProcessDiag clang::DiagnosticsEngine::EmitCurrentDiagnostic Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202010190618:202010200603 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5637772372869120 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 47924] New: Better codegen for vector elem set at variable index
https://bugs.llvm.org/show_bug.cgi?id=47924
Bug ID: 47924
Summary: Better codegen for vector elem set at variable index
Product: libraries
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Backend: X86
Assignee: unassignedb...@nondot.org
Reporter: david.bolvan...@gmail.com
CC: craig.top...@gmail.com, llvm-bugs@lists.llvm.org,
llvm-...@redking.me.uk, pengfei.w...@intel.com,
spatel+l...@rotateright.com
#define N 32
typedef int T;
typedef T V __attribute__((vector_size(N)));
V vec_set (V v, int idx, T val)
{
v[idx] = val;
return v;
}
=>
V vec_set_opt (V v, int idx, T val)
{
V valv = (V){idx, idx, idx, idx, idx, idx, idx, idx};
V mask = ((V){0, 1, 2, 3, 4, 5, 6, 7} == valv);
v = (v & ~mask) | (valv & mask);
return v;
}
Clang -O3 -mavx2
vec_set(int __vector(8), int, int): # @vec_set(int
__vector(8), int, int)
pushrbp
mov rbp, rsp
and rsp, -32
sub rsp, 64
vmovaps ymmword ptr [rsp], ymm0
and edi, 7
mov dword ptr [rsp + 4*rdi], esi
vmovaps ymm0, ymmword ptr [rsp]
mov rsp, rbp
pop rbp
ret
.LCPI1_0:
.long 0 # 0x0
.long 1 # 0x1
.long 2 # 0x2
.long 3 # 0x3
.long 4 # 0x4
.long 5 # 0x5
.long 6 # 0x6
.long 7 # 0x7
vec_set_opt(int __vector(8), int, int): # @vec_set_opt(int
__vector(8), int, int)
vmovd xmm1, edi
vpbroadcastdymm1, xmm1
vmovdqa ymm2, ymmword ptr [rip + .LCPI1_0] # ymm2 = [0,1,2,3,4,5,6,7]
vpcmpeqdymm1, ymm1, ymm2
vblendvps ymm0, ymm0, ymm2, ymm1
ret
https://godbolt.org/z/zvYMzT
--
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 47807] -frounding-math breaks float initializers
https://bugs.llvm.org/show_bug.cgi?id=47807 Richard Smith changed: What|Removed |Added Fixed By Commit(s)||7e801ca Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Richard Smith --- Yes, that change will / should have fixed this issue. -- 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 47925] New: [ASan] -fno-common generates a comdat with asan options
https://bugs.llvm.org/show_bug.cgi?id=47925
Bug ID: 47925
Summary: [ASan] -fno-common generates a comdat with asan
options
Product: clang
Version: trunk
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P
Component: LLVM Codegen
Assignee: unassignedclangb...@nondot.org
Reporter: wolfgang_p...@playstation.sony.com
CC: llvm-bugs@lists.llvm.org, neeil...@live.com,
richard-l...@metafoo.co.uk
The following trivial source generates a comdat for 'bar' when using ASan:
/*==*/
char bar;
/*==*/
clang -emit-llvm -S -fsanitize=address -fdata-sections
-fsanitize-address-globals-dead-stripping -c bar.c
bar.ll:
@bar = dso_local global { i8, [63 x i8] } zeroinitializer, comdat, align 32
Without either -fsanitize-address-globals-dead-stripping or -fdata-sections no
comdat is generated.
The consequence is that we don't find some ODR violations at link time with
these options.
Note that commit
https://github.com/llvm/llvm-project/commit/3d9a0445cce368b55dc3a573bc91fe902bbb977f
changed the default to -fno-common. Before, you would have to give -fno-common
on the command line to trigger this behaviour.
--
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 47926] New: Variable of dependent non-literal type in constexpr not correctly diagnosed
https://bugs.llvm.org/show_bug.cgi?id=47926
Bug ID: 47926
Summary: Variable of dependent non-literal type in constexpr
not correctly diagnosed
Product: clang
Version: trunk
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: C++2a
Assignee: unassignedclangb...@nondot.org
Reporter: ca...@carter.net
CC: blitzrak...@gmail.com, erik.pilking...@gmail.com,
llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk
This TU:
template
constexpr bool f() {
if (!__builtin_is_constant_evaluated()) {
[[maybe_unused]] T t;
}
return true;
}
struct nonliteral {
~nonliteral() {}
};
static_assert(f(), "should fail");
is ill-formed per N4868 [dcl.constexpr]/3.5.3 "The definition of a constexpr
function shall satisfy the following requirements:... its function-body shall
not enclose... a definition of a variable of non-literal type ...". Clang fails
to diagnose this TU (https://godbolt.org/z/xoMGxs).
--
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 47927] New: Shift UB in emitLegacyZExt when "from" type is >= 64-bit
https://bugs.llvm.org/show_bug.cgi?id=47927
Bug ID: 47927
Summary: Shift UB in emitLegacyZExt when "from" type is >=
64-bit
Product: libraries
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P
Component: DebugInfo
Assignee: unassignedb...@nondot.org
Reporter: v...@apple.com
CC: jdevliegh...@apple.com, keith.wal...@arm.com,
llvm-bugs@lists.llvm.org,
paul_robin...@playstation.sony.com
Clang trips an "out of bounds shift" UBSan diagnostic when compiling
__fixunsxfti from compiler-rt.
A reduced test:
```
; RUN: llc -filetype=obj -o - %s | llvm-dwarfdump -
define void @t(i64 %x) !dbg !6 {
call void @llvm.dbg.value(metadata i64 %x, metadata !9,
metadata !DIExpression(DW_OP_LLVM_convert, 64,
DW_ATE_unsigned,
DW_OP_LLVM_convert, 128,
DW_ATE_unsigned)), !dbg !11
ret void, !dbg !12
}
declare void @llvm.dbg.value(metadata, metadata, metadata)
!llvm.dbg.cu = !{!0}
!llvm.debugify = !{!3, !4}
!llvm.module.flags = !{!5}
!0 = distinct !DICompileUnit(language: DW_LANG_C, file: !1, producer:
"debugify", isOptimized: true, runtimeVersion: 0, emissionKind: FullDebug,
enums: !2)
!1 = !DIFile(filename: "legacy-zext.ll", directory: "/")
!2 = !{}
!3 = !{i64 2}
!4 = !{i64 1}
!5 = !{i64 2, !"Debug Info Version", i32 3}
!6 = distinct !DISubprogram(name: "t", linkageName: "t", scope: null, file: !1,
line: 1, type: !7, scopeLine: 1, spFlags: DISPFlagDefinition |
DISPFlagOptimized, unit: !0, retainedNodes: !8)
!7 = !DISubroutineType(types: !2)
!8 = !{!9}
!9 = !DILocalVariable(name: "1", scope: !6, file: !1, line: 1, type: !10)
!10 = !DIBasicType(name: "ty64", size: 32, encoding: DW_ATE_unsigned)
!11 = !DILocation(line: 1, column: 1, scope: !6)
!12 = !DILocation(line: 2, column: 1, scope: !6)
```
Here's the code that trips the UBSan diagnostic:
```
void DwarfExpression::emitLegacyZExt(unsigned FromBits) {
// (X & (1 << FromBits - 1))
emitOp(dwarf::DW_OP_constu);
emitUnsigned((1ULL << FromBits) - 1); //<<< HERE (FromBits >= 64)
emitOp(dwarf::DW_OP_and);
}
```
This legacy zext operation is a fallback DW_OP_convert implementation when
targeting Dwarf 4.
One way to address the diagnostic might be to plumb APInt through
DwarfExpression, MCStreamer, MCAsmStreamer, ByteStreamer, DIEInteger and so on.
I'm not sure whether that's a direction others in the community want to go. The
complexity of the change seems somewhat out of proportion to the problem it's
trying to fix.
Is there some other way to implement the legacy zext? Or should we try not to
emit it if we can't emit the mask?
--
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 26544 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::FunctionProtoType::getExceptionSpecInfo
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-10-21 Type: Bug New issue 26544 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::FunctionProtoType::getExceptionSpecInfo https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26544 Detailed Report: https://oss-fuzz.com/testcase?key=5086308986519552 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffd45262a18 Crash State: clang::FunctionProtoType::getExceptionSpecInfo clang::FunctionProtoType::getExtProtoInfo clang::FunctionProtoType::Profile Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202010190618:202010200603 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5086308986519552 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 26545 in oss-fuzz: llvm:clang-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-10-21 Type: Bug New issue 26545 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in GetFullTypeForDeclarator https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26545 Detailed Report: https://oss-fuzz.com/testcase?key=5738448230809600 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffee3b1bac0 Crash State: GetFullTypeForDeclarator clang::Sema::GetTypeForDeclarator clang::Sema::HandleDeclarator Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202010190618:202010200603 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5738448230809600 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 47928] New: "Did you mean" suggests deprecated namespaces before non-deprecated ones
https://bugs.llvm.org/show_bug.cgi?id=47928
Bug ID: 47928
Summary: "Did you mean" suggests deprecated namespaces before
non-deprecated ones
Product: clang
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: C++
Assignee: unassignedclangb...@nondot.org
Reporter: arthur.j.odw...@gmail.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/YT1Tra
namespace Views {
int Take();
}
namespace [[deprecated("use Views instead")]] View {
using Views::Take;
}
int main() {
int x = ::Take();
}
:10:13: error: no member named 'Take' in the global namespace; did you
mean 'View::Take'?
int x = ::Take();
^~
View::Take
:6:18: note: 'View::Take' declared here
using Views::Take;
^
This is reduced from a real piece of code using Range-v3
ranges::view{,s}::take. It seems completely backwards that Clang would suggest
the deprecated synonym (from the using-declaration) rather than the true
version from the non-deprecated namespace.
Perhaps Clang is just thinking that the edit distance between "" and "views" is
longer than the edit distance between "" and "view". However, I think it would
be a nice UX improvement to also consider what kind of entity is being
suggested (is it just a synonym for something from a different namespace? then
follow the symlink) and whether the suggested entity has been explicitly
deprecated (then maybe don't consider it a candidate for suggestion at all).
--
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 47340] hang on x86_64-linux-gnu with `-mllvm -polly -O2` and above
https://bugs.llvm.org/show_bug.cgi?id=47340 Michael Kruse changed: What|Removed |Added Fixed By Commit(s)||7175cffb2133048018df74c1b49 ||d1d4962ea18f2 Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Michael Kruse --- Should be fixed in 7175cffb2133048018df74c1b49d1d4962ea18f2 Thanks for the report. -- 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 26553 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::Sema::DiagnoseEmptyLookup
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-10-21 Type: Bug New issue 26553 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::Sema::DiagnoseEmptyLookup https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26553 Detailed Report: https://oss-fuzz.com/testcase?key=6034678957735936 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffd92892ff8 Crash State: clang::Sema::DiagnoseEmptyLookup clang::Sema::ActOnIdExpression clang::Parser::ParseCastExpression Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201808300127:201808310127 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6034678957735936 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
