[llvm-bugs] Issue 4608 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in clang::Parser::ParseDeclaratorInternal
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, akila_sr...@apple.com, llvm-b...@lists.llvm.org, v...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer Proj-llvm Reported-2017-12-12 Type: Bug New issue 4608 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in clang::Parser::ParseDeclaratorInternal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4608 Detailed report: https://oss-fuzz.com/testcase?key=4509429087076352 Project: llvm Fuzzer: libFuzzer_llvm_clang-fuzzer Fuzz target binary: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7fff0ddc5ed8 Crash State: clang::Parser::ParseDeclaratorInternal clang::Parser::ParseDeclaratorInternal clang::Parser::ParseMisplacedBracketDeclarator Sanitizer: address (ASAN) Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4509429087076352 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. 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 have questions for the OSS-Fuzz team, please file an issue at https://github.com/google/oss-fuzz/issues. -- 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 4609 in oss-fuzz: llvm: Stack-overflow in Evaluate
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, akila_sr...@apple.com, llvm-b...@lists.llvm.org, v...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer Proj-llvm Reported-2017-12-12 Type: Bug New issue 4609 by ClusterFuzz-External: llvm: Stack-overflow in Evaluate https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4609 Detailed report: https://oss-fuzz.com/testcase?key=4629918072700928 Project: llvm Fuzzer: libFuzzer_llvm_clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffd68090c60 Crash State: Evaluate ComplexExprEvaluator::VisitBinaryOperator clang::StmtVisitorBasebool>::Visit Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710121744:201710130152 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4629918072700928 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. 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 have questions for the OSS-Fuzz team, please file an issue at https://github.com/google/oss-fuzz/issues. -- 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 4611 in oss-fuzz: llvm: Stack-overflow in IntExprEvaluator::VisitCastExpr
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, akila_sr...@apple.com, llvm-b...@lists.llvm.org, v...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer Proj-llvm Reported-2017-12-12 Type: Bug New issue 4611 by ClusterFuzz-External: llvm: Stack-overflow in IntExprEvaluator::VisitCastExpr https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4611 Detailed report: https://oss-fuzz.com/testcase?key=4673111367614464 Project: llvm Fuzzer: libFuzzer_llvm_clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffee6192d80 Crash State: IntExprEvaluator::VisitCastExpr clang::StmtVisitorBasebool>::Visit Evaluate Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201711160610:201712080609 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4673111367614464 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. 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 have questions for the OSS-Fuzz team, please file an issue at https://github.com/google/oss-fuzz/issues. -- 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35616] -callsite-splitting gives different result if dbg.value is present
https://bugs.llvm.org/show_bug.cgi?id=35616 Mikael Holmén changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #2 from Mikael Holmén --- Fixed in rL320460. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35639] New: [X86] CompleteModel scheduler models still missing instruction schedules
https://bugs.llvm.org/show_bug.cgi?id=35639 Bug ID: 35639 Summary: [X86] CompleteModel scheduler models still missing instruction schedules Product: libraries Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: Backend: X86 Assignee: unassignedb...@nondot.org Reporter: llvm-...@redking.me.uk CC: andrew.v.tische...@gmail.com, llvm-bugs@lists.llvm.org Tablegen appears to consider an instruction as scheduled if it has either an itinerary or a sched class, allowing us to set the CompleteModel = 1 flag. But given that x86 models use itineraries OR the classes, they might not actually be tagged with both, this should raise an error. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35555] SEGV in FormatASTNodeDiagnosticArgument()
https://bugs.llvm.org/show_bug.cgi?id=3 Malcolm Parsons changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35640] New: Merge r320396 into the 5.0 branch : [Sema] Fix crash in unused-lambda-capture warning for VLAs
https://bugs.llvm.org/show_bug.cgi?id=35640 Bug ID: 35640 Summary: Merge r320396 into the 5.0 branch : [Sema] Fix crash in unused-lambda-capture warning for VLAs Product: new-bugs Version: 5.0 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: malcolm.pars...@gmail.com CC: llvm-bugs@lists.llvm.org Blocks: 34492 Is it OK to merge the following revision(s) to the 5.0 branch? Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=34492 [Bug 34492] [meta] 5.0.1 Release Blockers -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35641] New: Formatting makes code incorrect
https://bugs.llvm.org/show_bug.cgi?id=35641
Bug ID: 35641
Summary: Formatting makes code incorrect
Product: clang
Version: trunk
Hardware: Macintosh
OS: MacOS X
Status: NEW
Severity: normal
Priority: P
Component: Formatter
Assignee: unassignedclangb...@nondot.org
Reporter: vbeff...@gmail.com
CC: djas...@google.com, kli...@google.com,
llvm-bugs@lists.llvm.org
With this code:
--- a.cpp
int l() { //
int p;
}
---
And this .clang-format:
--- .clang-format
---
AlignConsecutiveDeclarations: true
---
I get the following output:
--- output
int l() { //
intp;
}
---
(which obviously does not compile).
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 31944] [PCH] Clang crashes when precompile header file with #line directive.
https://bugs.llvm.org/show_bug.cgi?id=31944 Hans Wennborg changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED CC||h...@chromium.org --- Comment #4 from Hans Wennborg --- Yes, this was fixed by the commit above. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35642] New: recognize min/max patterns as commutative
https://bugs.llvm.org/show_bug.cgi?id=35642
Bug ID: 35642
Summary: recognize min/max patterns as commutative
Product: libraries
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: Scalar Optimizations
Assignee: unassignedb...@nondot.org
Reporter: spatel+l...@rotateright.com
CC: llvm-bugs@lists.llvm.org
#include
int maxmax(int a, int b) {
return std::max(a, b) - std::max(b, a);
}
Or as IR after -O2:
define i32 @_Z6maxmaxii(i32 %a, i32 %b) {
%cmp1 = icmp slt i32 %a, %b
%sel1 = select i1 %cmp1, i32 %b, i32 %a
%cmp2 = icmp slt i32 %b, %a
%sel2 = select i1 %cmp2, i32 %a, i32 %b
%sub = sub nsw i32 %sel1, %sel2
ret i32 %sub
}
https://godbolt.org/g/hG6HMR
I think early-cse needs to know that max is commutative. We can't easily
instcombine or instsimplify our way out of this.
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35643] New: [X86] Multiple output instructions should warn if all outputs aren't scheduled
https://bugs.llvm.org/show_bug.cgi?id=35643 Bug ID: 35643 Summary: [X86] Multiple output instructions should warn if all outputs aren't scheduled Product: libraries Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: Backend: X86 Assignee: unassignedb...@nondot.org Reporter: llvm-...@redking.me.uk CC: llvm-bugs@lists.llvm.org Blocks: 32325 Bug #35636 is due to MULX64rr giving 2 outputs, but the scheduler model InstRW<> definition only poorly supports multiple outputs. We need a better way to report when not all outputs are tagged by the scheduler class. Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=32325 [Bug 32325] [META][X86] Improve implementation and use of X86 scheduler models -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35644] New: Incorrect warning generated for methods with noexcept signature and catch all handler
https://bugs.llvm.org/show_bug.cgi?id=35644
Bug ID: 35644
Summary: Incorrect warning generated for methods with noexcept
signature and catch all handler
Product: clang
Version: 5.0
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Frontend
Assignee: unassignedclangb...@nondot.org
Reporter: michael.cra...@ith-icoserve.com
CC: llvm-bugs@lists.llvm.org
Created attachment 19539
--> https://bugs.llvm.org/attachment.cgi?id=19539&action=edit
sample source file to compile demonstration
If the code below ( and attached 'main.c' ):
void f() noexcept
{
try {
throw;
}
catch (...) {
}
}
is compiled with clang 5.0.1RC3 the following warning is generated:
" 'f' has a non-throwing exception specification but can still throw
[-Wexceptions]"
which is incorrect since the throw call is caught by the catch-all handler,
therefore qualifying as non-throwing.
g++, 4.8.2 at least, does not emit any warning.
Kind regards
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 4619 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: Abrt in llvm::llvm_unreachable_internal
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, akila_sr...@apple.com, llvm-b...@lists.llvm.org, v...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer Proj-llvm Reported-2017-12-12 Type: Bug New issue 4619 by ClusterFuzz-External: llvm/llvm-dwarfdump-fuzzer: Abrt in llvm::llvm_unreachable_internal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4619 Detailed report: https://oss-fuzz.com/testcase?key=6647657620570112 Project: llvm Fuzzer: libFuzzer_llvm_llvm-dwarfdump-fuzzer Fuzz target binary: llvm-dwarfdump-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Abrt Crash Address: 0x0001 Crash State: llvm::llvm_unreachable_internal llvm::DataExtractor::getUnsigned llvm::DWARFDataExtractor::getRelocatedValue Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201711070608:201711090621 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6647657620570112 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. 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 have questions for the OSS-Fuzz team, please file an issue at https://github.com/google/oss-fuzz/issues. -- 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35645] New: [AMDGPU][MC] Incorrect parsing of ds_swizzle operands
https://bugs.llvm.org/show_bug.cgi?id=35645 Bug ID: 35645 Summary: [AMDGPU][MC] Incorrect parsing of ds_swizzle operands Product: libraries Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: Backend: AMDGPU Assignee: unassignedb...@nondot.org Reporter: dpreobrazhen...@luxoft.com CC: llvm-bugs@lists.llvm.org ds_swizzle_b32 should accept optional 'offset' and 'gds' modifiers. However if 'offset' modifier is omitted, 'gds' modifier causes a syntax error. An example of a failed test: ds_swizzle_b32 v5, v1 gds -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35494] [AMDGPU][MC][GFX9] Incorrect encoding of ttmp registers
https://bugs.llvm.org/show_bug.cgi?id=35494 Dmitry changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Dmitry --- fixed by commit 320375: http://llvm.org/viewvc/llvm-project?rev=320375&view=rev -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35559] [AMDGPU][MC][GFX9] access to tba and tma registers should be disabled
https://bugs.llvm.org/show_bug.cgi?id=35559 Dmitry changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Dmitry --- fixed by commit 320375: http://llvm.org/viewvc/llvm-project?rev=320375&view=rev -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35458] [AMDGPU][MC][GFX9] Incorrect mapping of pseudo to MC for v_add/sub/subrev_u32
https://bugs.llvm.org/show_bug.cgi?id=35458 Dmitry changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #2 from Dmitry --- Fixed by commit 319311: http://llvm.org/viewvc/llvm-project?rev=319311&view=rev -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35433] [AMDGPU][MC][DISASSEMBLER][GFX9] Incorrect decoding of GLOBAL/SCRATCH instructions
https://bugs.llvm.org/show_bug.cgi?id=35433 Dmitry changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Dmitry --- fixed by commit 319050: http://llvm.org/viewvc/llvm-project?rev=319050&view=rev -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35329] [AMDGPU][MC][GFX9] FLAT/GLOBAL/SCRATCH instructions should use 'inst_offset' instead of 'offset'
https://bugs.llvm.org/show_bug.cgi?id=35329 Dmitry changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #7 from Dmitry --- fixed by commit 318947: http://llvm.org/viewvc/llvm-project?rev=318947&view=rev -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35646] New: Clang++ creates symbol it cannot demangle.
https://bugs.llvm.org/show_bug.cgi?id=35646
Bug ID: 35646
Summary: Clang++ creates symbol it cannot demangle.
Product: clang
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: C++
Assignee: unassignedclangb...@nondot.org
Reporter: hua...@google.com
CC: dgre...@apple.com, llvm-bugs@lists.llvm.org
Consider the following program, saved as "a.cc"
a.cc
#include
std::string get_value() {
return "sparrow";
}
int main() {
static const std::string& weird = get_value();
return 0;
}
Build, get symbol for |weird| and demangle:
clang++ a.cc
llvm-nm a.out | grep weird # Output 1
llvm-nm a.out --demangle | grep weird# Output 2
Results:
Output 1
006010a0 b _ZGRZ4mainE5weird_
00601098 b _ZGVZ4mainE5weird
00601090 b _ZZ4mainE5weird
Output 2
006010a0 b _ZGRZ4mainE5weird_
00601098 b guard variable for main::weird
00601090 b main::weird
So "_ZGRZ4mainE5weird_" cannot be demangled (llvm-cxxfilt does not work
either). Interestingly, c++filt can demangle it as:
reference temporary #0 for main::weird
So it seems one of the following is broken:
(1) Mangled name generation producing an invalid value.
(2) Demangling not properly working (perhaps with extension).
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35618] Instcombine hangs because of '[InstCombine] PR35354: Convert store...' (r320157)
https://bugs.llvm.org/show_bug.cgi?id=35618 Alexey Bataev changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Alexey Bataev --- Fixed in r320525 -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35647] New: C++ standard violation: [templates][explicit instantiation][access checking][pointer to overloaded member function]
https://bugs.llvm.org/show_bug.cgi?id=35647
Bug ID: 35647
Summary: C++ standard violation: [templates][explicit
instantiation][access checking][pointer to overloaded
member function]
Product: clang
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P
Component: C++11
Assignee: unassignedclangb...@nondot.org
Reporter: martongab...@gmail.com
CC: dgre...@apple.com, llvm-bugs@lists.llvm.org
C++11 Standard / 14.7.2 (Explicit instantiation) / 12:
The usual access checking rules do not apply to names used to specify explicit
instantiations. [Note: In particular, the template arguments and names used in
the function declarator (including parameter types, return types and exception
specifications) may be private types or objects which would normally not be
accessible and the template may be a member template or member function which
would not normally be accessible. —endnote]
If there is non-overloaded member function Clang complies to the standard,
however if there is an overloaded member function it does not.
Code below:
template
struct private_access {
friend PtrType get(TagType) { return PtrValue; }
};
class Foo
{
void print0(int);
void print();
void print(int);
};
using A = void(int);
using B = A Foo::*;
struct Tag {};
template struct private_access;// OK
template struct private_access; // ERROR, OK in GCC
int main() { return 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
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35648] New: Test failure with CUDA 9.0
https://bugs.llvm.org/show_bug.cgi?id=35648 Bug ID: 35648 Summary: Test failure with CUDA 9.0 Product: clang Version: trunk Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: CUDA Assignee: unassignedclangb...@nondot.org Reporter: j@gmx.com CC: llvm-bugs@lists.llvm.org The Driver/unknown-std.cpp test is failing with CUDA 9.0 due to an unsupported architecture "sm_20" which was dropped in CUDA 9.0. I got this on revision 320484: FAIL: Clang :: Driver/unknown-std.cpp (4403 of 11748) TEST 'Clang :: Driver/unknown-std.cpp' FAILED Script: -- not /home/klinkovsky/build/builddir/llvm-svn/src/build/bin/clang /home/klinkovsky/build/builddir/llvm-svn/src/llvm/tools/clang/test/Driver/unknown-std.cpp -std=foobar -c 2>&1 | /home/klinkovsky/build/builddir/llvm-svn/src/build/bin/FileCheck --match-full-lines /home/klinkovsky/build/builddir/llvm-svn/src/llvm/tools/clang/test/Driver/unknown-std.cpp not /home/klinkovsky/build/builddir/llvm-svn/src/build/bin/clang -x objective-c++ /home/klinkovsky/build/builddir/llvm-svn/src/llvm/tools/clang/test/Driver/unknown-std.cpp -std=foobar -c 2>&1 | /home/klinkovsky/build/builddir/llvm-svn/src/build/bin/FileCheck --match-full-lines /home/klinkovsky/build/builddir/llvm-svn/src/llvm/tools/clang/test/Driver/unknown-std.cpp not /home/klinkovsky/build/builddir/llvm-svn/src/build/bin/clang -x cuda -nocudainc -nocudalib /home/klinkovsky/build/builddir/llvm-svn/src/llvm/tools/clang/test/Driver/unknown-std.cpp -std=foobar -c 2>&1 | /home/klinkovsky/build/builddir/llvm-svn/src/build/bin/FileCheck --match-full-lines --check-prefix=CHECK --check-prefix=CUDA /home/klinkovsky/build/builddir/llvm-svn/src/llvm/tools/clang/test/Driver/unknown-std.cpp -- Exit Code: 1 Command Output (stderr): -- /home/klinkovsky/build/builddir/llvm-svn/src/llvm/tools/clang/test/Driver/unknown-std.cpp:9:11: error: expected string not found in input // CHECK: error: invalid value 'foobar' in '-std=foobar' ^ :1:1: note: scanning from here clang-6.0: error: GPU arch sm_20 is supported by CUDA versions between 7.0 and 8.0 (inclusive), but installation at /usr/local/cuda is 9.0. Use --cuda-path to specify a different CUDA install, pass a different GPU arch with --cuda-gpu-arch, or pass --no-cuda-version-check. ^ :1:10: note: possible intended match here clang-6.0: error: GPU arch sm_20 is supported by CUDA versions between 7.0 and 8.0 (inclusive), but installation at /usr/local/cuda is 9.0. Use --cuda-path to specify a different CUDA install, pass a different GPU arch with --cuda-gpu-arch, or pass --no-cuda-version-check. ^ -- -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35648] Test failure with CUDA 9.0
https://bugs.llvm.org/show_bug.cgi?id=35648 Artem Belevich changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #1 from Artem Belevich --- That's been fixed in https://reviews.llvm.org/rL320506 -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35294] XRay trampolines may leave the stack unaligned
https://bugs.llvm.org/show_bug.cgi?id=35294 Dean Michael Berris changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #1 from Dean Michael Berris --- Fixed in r318261. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35556] [LLVM-COV] dead label and false conditional lead to incorrect coverage in llvm-cov
https://bugs.llvm.org/show_bug.cgi?id=35556 Vedant Kumar changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #6 from Vedant Kumar --- Great, in that case it's OK (and encouraged) to mark it Resolved | 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35630] Illegal ARM THUMB udiv instruction generated from llc with -filetype=asm, but not -filetype=obj
https://bugs.llvm.org/show_bug.cgi?id=35630 Jack Carter changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #15 from Jack Carter --- This is probably a pilot error so I want to reject it for now. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 4622 in oss-fuzz: llvm: Stack-overflow in clang::DeclContext::lookup
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, akila_sr...@apple.com, llvm-b...@lists.llvm.org, v...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer Proj-llvm Reported-2017-12-13 Type: Bug New issue 4622 by ClusterFuzz-External: llvm: Stack-overflow in clang::DeclContext::lookup https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4622 Detailed report: https://oss-fuzz.com/testcase?key=4851605913468928 Project: llvm Fuzzer: libFuzzer_llvm_clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7fff2b5b6818 Crash State: clang::DeclContext::lookup clang::DeclContext::using_directives UnqualUsingDirectiveSet::addUsingDirectives Sanitizer: address (ASAN) Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4851605913468928 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. 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 have questions for the OSS-Fuzz team, please file an issue at https://github.com/google/oss-fuzz/issues. -- 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35649] New: clang crash in diagnostics in overload failure with non-type templates
https://bugs.llvm.org/show_bug.cgi?id=35649 Bug ID: 35649 Summary: clang crash in diagnostics in overload failure with non-type templates Product: clang Version: 5.0 Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: C++ Assignee: unassignedclangb...@nondot.org Reporter: spr...@yandex-team.ru CC: dgre...@apple.com, llvm-bugs@lists.llvm.org Created attachment 19541 --> https://bugs.llvm.org/attachment.cgi?id=19541&action=edit The failing code Compilation of the attached code crashes with the following diagnostics: [=]clang++ -std=c++14 test.cpp -I`pwd`/LLVM/libcxx/include test.cpp:84:5: error: no matching function for call to 'SerializeWithSwitchersImpl' SerializeWithSwitchersImpl( ^~ #0 0x019dd014 PrintStackTraceSignalHandler(void*) (/place/home/spreis/.ya/tools/v3/168054294/bin/clang-5.0+0x19dd014) #1 0x019dd2d6 SignalHandler(int) (/place/home/spreis/.ya/tools/v3/168054294/bin/clang-5.0+0x19dd2d6) #2 0x7f40573ec330 __restore_rt (/lib/x86_64-linux-gnu/libpthread.so.0+0x10330) #3 0x02af3ef2 DiagnoseBadDeduction(clang::Sema&, clang::NamedDecl*, clang::Decl*, clang::DeductionFailureInfo&, unsigned int, bool) (/place/home/spreis/.ya/tools/v3/168054294/bin/clang-5.0+0x2af3ef2) #4 0x02adfad5 clang::OverloadCandidateSet::NoteCandidates(clang::Sema&, clang::OverloadCandidateDisplayKind, llvm::ArrayRef, llvm::StringRef, clang::SourceLocation, llvm::function_ref) (/place/home/spreis/.ya/tools/v3/168054294/bin/clang-5.0+0x2adfad5) ... -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35636] [X86] DefIdx 1 exceeds machine model writes for %rdi, dead %rax = MULX64rr killed %rax, implicit %rdx
https://bugs.llvm.org/show_bug.cgi?id=35636 octoploid changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #5 from octoploid --- Fixed. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
