[llvm-bugs] [Bug 37334] Assertion `DT && "DT should be available to update LoopInfo!"' failed. with -break-crit-edges
https://bugs.llvm.org/show_bug.cgi?id=37334 Mikael Holmén changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Mikael Holmén --- Fixed in r332583. -- 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 37203] PHI node has multiple entries for the same basic block with different incoming values!
https://bugs.llvm.org/show_bug.cgi?id=37203 bjorn.a.petters...@ericsson.com changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #2 from bjorn.a.petters...@ericsson.com --- Solved in rL332577: [SROA] Handle PHI with multiple duplicate predecessors) See https://reviews.llvm.org/rL332577 -- 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 37494] New: [llvm-mca] Add bottleneck hint messages
https://bugs.llvm.org/show_bug.cgi?id=37494 Bug ID: 37494 Summary: [llvm-mca] Add bottleneck hint messages Product: new-bugs Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: llvm-...@redking.me.uk CC: andrea.dibia...@gmail.com, clement.cour...@gmail.com, gchate...@google.com, greg.bedw...@sony.com, llvm-bugs@lists.llvm.org, matthew.da...@sony.com Similar to IACA, it'd be useful if llvm-mca could hint at the bottleneck in the tested code snippet: e.g. loop dependency resource 'X' usage load-store frontend -- 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 37495] New: LLDB shows wrong results when execute 'register read' at non-zero frame on Windows
https://bugs.llvm.org/show_bug.cgi?id=37495 Bug ID: 37495 Summary: LLDB shows wrong results when execute 'register read' at non-zero frame on Windows Product: lldb Version: 6.0 Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: kenji.koyan...@gmail.com CC: llvm-bugs@lists.llvm.org Created attachment 20312 --> https://bugs.llvm.org/attachment.cgi?id=20312&action=edit patch for 6.0.0 The result of 'register read' command at deeper than frame #0 was same as frame #0. Further, 'thread return' command had no effect on current thread. I think that the behavior is different between TargetThreadWindows and ThreadElfCore. These commands worked correctly when I revised TargetThreadWindows with reference to ThreadElfCore. -- 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 37339] FunctionComparator::cmpInlineAsm is overly restrictive
https://bugs.llvm.org/show_bug.cgi?id=37339 Nikita Popov changed: What|Removed |Added Fixed By Commit(s)||r331990 Status|NEW |RESOLVED Resolution|--- |FIXED CC||nikita@gmail.com --- Comment #2 from Nikita Popov --- This has been fixed by https://reviews.llvm.org/rL331990. -- 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 37496] New: Sometimes LLDB freeze after launching process
https://bugs.llvm.org/show_bug.cgi?id=37496 Bug ID: 37496 Summary: Sometimes LLDB freeze after launching process Product: lldb Version: 6.0 Hardware: PC OS: All Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: kenji.koyan...@gmail.com CC: llvm-bugs@lists.llvm.org Created attachment 20313 --> https://bugs.llvm.org/attachment.cgi?id=20313&action=edit patch for 6.0.0 Sometimes(1 of 5-7 times) LLDB freeze at Process::WaitForProcessToStop after launching process. I am using lldb for Windows, but I think that it is not a OS-specific issue. I inserted a log and tried to run LLDB. Process::SetPublicState called with argument eStateLaunching -> eStateStopped -> eStateLaunching. I think there is a problem in the processing order of broadcast events. It worked fine if consume the event before calling SetPublicState in Process::Launch. But this is not the best solution. -- 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 37497] New: [llvm-exegesis] Update docs to cover all command line options
https://bugs.llvm.org/show_bug.cgi?id=37497 Bug ID: 37497 Summary: [llvm-exegesis] Update docs to cover all command line options Product: new-bugs Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: llvm-...@redking.me.uk CC: andrea.dibia...@gmail.com, clement.cour...@gmail.com, craig.top...@gmail.com, fil...@gmail.com, gchate...@google.com, greg.bedw...@sony.com, llvm-bugs@lists.llvm.org http://llvm.org/docs/CommandGuide/llvm-exegesis.html This is getting very out of date, with no reference to how the analysis mode is to be used etc. Ideally there would be examples of usage/output as well. -- 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 37498] New: [llvm-exegesis] Support opcode lists for benchmarking
https://bugs.llvm.org/show_bug.cgi?id=37498 Bug ID: 37498 Summary: [llvm-exegesis] Support opcode lists for benchmarking Product: new-bugs Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: llvm-...@redking.me.uk CC: andrea.dibia...@gmail.com, clement.cour...@gmail.com, craig.top...@gmail.com, fil...@gmail.com, gchate...@google.com, greg.bedw...@sony.com, llvm-bugs@lists.llvm.org It'd be very helpful if we could provide a list of opcodes and have the output generated for each of them: e.g. llvm-exegesis -benchmark-mode=latency -opcode-name=PMULLDrr,VPMULLDrr,VPMULLDYrr A comma separated list would be preferred but allowing repeated -opcode-name= options would be acceptable: e.g. llvm-exegesis -benchmark-mode=latency -opcode-name=PMULLDrr -opcode-name=VPMULLDrr -opcode-name=VPMULLDYrr -- 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 4068] [Meta] Compiling the Linux kernel with clang
https://bugs.llvm.org/show_bug.cgi?id=4068 Bug 4068 depends on bug 37180, which changed state. Bug 37180 Summary: "S" arm64 assembly constraint unrecognized https://bugs.llvm.org/show_bug.cgi?id=37180 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 37180] "S" arm64 assembly constraint unrecognized
https://bugs.llvm.org/show_bug.cgi?id=37180 Peter Smith changed: What|Removed |Added Status|NEW |RESOLVED CC||peter.sm...@linaro.org Resolution|--- |FIXED --- Comment #1 from Peter Smith --- I've made an attempt to fix this with https://reviews.llvm.org/D46745 r332444 it resurrects the S support from the original pre-merged AArch64 backend. clang test updated in https://reviews.llvm.org/D46932 r332606. -- 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 37499] New: [AVX512] LLVM ERROR: Cannot select: v8i16 = vselect v8i16, v8i16, v8i16
https://bugs.llvm.org/show_bug.cgi?id=37499
Bug ID: 37499
Summary: [AVX512] LLVM ERROR: Cannot select: v8i16 = vselect
v8i16, v8i16, v8i16
Product: new-bugs
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: ilia.tara...@intel.com
CC: llvm-bugs@lists.llvm.org
This test fails at "X86 DAG->DAG Instruction Selection" with error "Cannot
select: 0x1ad76e8: v8i16 = vselect 0x1ad7ea0, undef:v8i16, 0x1ad7548" :
= nice.c ==
#include
void foo (void)
{
__m128i x = _mm_setr_epi16(1, 1, 1, 1, 1, 1, 1, 1);
__m512i y;
int mask = 0x1;
x = _mm512_mask_cvtepi64_epi16(x, mask, y);
goo(x);
}
===
>>> clang -v
clang version 7.0.0 (trunk 332600)
Target: x86_64-unknown-linux-gnu
Thread model: posix
...
>>> clang -c nice.c -O2 -march=knl
fatal error: error in backend: Cannot select: t29: v8i16 = vselect t38,
undef:v8i16, t25
t38: v8i16 = extract_subvector t37, Constant:i64<0>
t37: v16i16 = truncate t36
t36: v16i32 = vselect t32, t34, t35
t32: v16i1 = insert_subvector undef:v16i1, t19, Constant:i64<0>
t31: v16i1 = undef
t19: v8i1 = bitcast Constant:i8<1>
t5: i8 = Constant<1>
t30: i64 = Constant<0>
t34: v16i32 = BUILD_VECTOR Constant:i32<-1>, Constant:i32<-1>,
Constant:i32<-1>, Constant:i32<-1>, Constant:i32<-1>, Constant:i32<-1>,
Constant:i32<-1>, Constant:i32<-1>, Constant:i32<-1>, Constant:i32<-1>,
Constant:i32<-1>, Constant:i32<-1>, Constant:i32<-1>, Constant:i32<-1>,
Constant:i32<-1>, Constant:i32<-1>
t33: i32 = Constant<-1>
t33: i32 = Constant<-1>
t33: i32 = Constant<-1>
t33: i32 = Constant<-1>
t33: i32 = Constant<-1>
t33: i32 = Constant<-1>
t33: i32 = Constant<-1>
t33: i32 = Constant<-1>
t33: i32 = Constant<-1>
t33: i32 = Constant<-1>
t33: i32 = Constant<-1>
t33: i32 = Constant<-1>
t33: i32 = Constant<-1>
t33: i32 = Constant<-1>
t33: i32 = Constant<-1>
t33: i32 = Constant<-1>
t35: v16i32 = BUILD_VECTOR Constant:i32<0>, Constant:i32<0>,
Constant:i32<0>, Constant:i32<0>, Constant:i32<0>, Constant:i32<0>,
Constant:i32<0>, Constant:i32<0>, Constant:i32<0>, Constant:i32<0>,
Constant:i32<0>, Constant:i32<0>, Constant:i32<0>, Constant:i32<0>,
Constant:i32<0>, Constant:i32<0>
t14: i32 = Constant<0>
t14: i32 = Constant<0>
t14: i32 = Constant<0>
t14: i32 = Constant<0>
t14: i32 = Constant<0>
t14: i32 = Constant<0>
t14: i32 = Constant<0>
t14: i32 = Constant<0>
t14: i32 = Constant<0>
t14: i32 = Constant<0>
t14: i32 = Constant<0>
t14: i32 = Constant<0>
t14: i32 = Constant<0>
t14: i32 = Constant<0>
t14: i32 = Constant<0>
t14: i32 = Constant<0>
t30: i64 = Constant<0>
t17: v8i16 = undef
t25: v8i16 = bitcast t24
t24: v2i64,ch = load<(load 16 from constant-pool)> t0, t27, undef:i64
t27: i64 = X86ISD::Wrapper TargetConstantPool:i64<<8 x i16> > 0
t26: i64 = TargetConstantPool<<8 x i16> > 0
t22: i64 = undef
In function: foo
clang-7: error: clang frontend command failed with exit code 70 (use -v to see
invocation)
clang version 7.0.0 (trunk 332600)
Target: x86_64-unknown-linux-gnu
...
Here is IR reproducer:
= fine.ll =
define void @foo()#0 {
%1 = tail call <8 x i16> @llvm.x86.avx512.mask.pmov.qw.512(<8 x i64> undef,
<8 x i16> , i8 1)
%2 = tail call i32 @goo(<8 x i16> %1)
ret void
}
declare i32 @goo(<8 x i16>)
declare <8 x i16> @llvm.x86.avx512.mask.pmov.qw.512(<8 x i64>, <8 x i16>, i8)
attributes #0 = { "target-features"="+avx512f" }
===
>>> llc fine.ll
LLVM ERROR: Cannot select: t26: v8i16 = vselect t35, undef:v8i16, t22
t35: v8i16 = extract_subvector t34, Constant:i64<0>
t34: v16i16 = truncate t33
t33: v16i32 = vselect t29, t31, t32
t29: v16i1 = insert_subvector undef:v16i1, t16, Constant:i64<0>
t28: v16i1 = undef
t16: v8i1 = bitcast Constant:i8<1>
t5: i8 = Constant<1>
t27: i64 = Constant<0>
t31: v16i32 = BUILD_VECTOR Constant:i32<-1>, Constant:i32<-1>,
Constant:i32<-1>, Constant:i32<-1>, Constant:i32<-1>, Constant:i32<-1>,
Constant:i32<-1>, Constant:i32<-1>, Constant:i32<-1>, Constant:i32<-1>,
Constant:i32<-1>, Constant:i32<-1>, Constant:i32<-1>, Constant:i32<-1>,
Constant:i32<-1>, Constant:i32<-1>
t30: i32 = Constant<-1>
t30: i32 = Constant<-1>
t30: i32 = Constant<-1>
t30: i32 = Constant<-
[llvm-bugs] [Bug 37500] New: Add wildcard + multiple files support to all update_*_test_checks.py scripts
https://bugs.llvm.org/show_bug.cgi?id=37500 Bug ID: 37500 Summary: Add wildcard + multiple files support to all update_*_test_checks.py scripts Product: new-bugs Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: llvm-...@redking.me.uk CC: greg.bedw...@sony.com, llvm-bugs@lists.llvm.org, spatel+l...@rotateright.com update_mca_test_checks.py can take wildcards and multiple files as inputs and will update all the files (continuing to the next file after encountering/dumping any errors). It'd be great if all the update scripts could do 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 37501] New: Assertion failure in clang::ento::ExprEngine::VisitLogicalExpr(...): N->pred_size() == 1
https://bugs.llvm.org/show_bug.cgi?id=37501
Bug ID: 37501
Summary: Assertion failure in
clang::ento::ExprEngine::VisitLogicalExpr(...):
N->pred_size() == 1
Product: clang
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Static Analyzer
Assignee: dcough...@apple.com
Reporter: ale...@google.com
CC: ekarpen...@apple.com, llvm-bugs@lists.llvm.org,
noqnoq...@gmail.com
$ cat test-ExprEngine__VisitLogicalExpr.c
a, c, d;
*b;
e() {
for (;;) f(b[a] > (d < c ?: 0) || b[a] < (e < c ?: 0));
}
$ clang-tidy -checks=-*,clang-analyzer* test-ExprEngine__VisitLogicalExpr.c --
assertion failed at
llvm/tools/clang/lib/StaticAnalyzer/Core/ExprEngineC.cpp:664 in void
clang::ento::ExprEngine::VisitLogicalExpr(const clang::BinaryOperator *,
clang::ento::ExplodedNode *, clang::ento::ExplodedNodeSet &): N->pred_size() ==
1
@ 0x556be4198cb6 __assert_fail
@ 0x556be1f1dcf3 clang::ento::ExprEngine::VisitLogicalExpr()
@ 0x556be1ef5cce clang::ento::ExprEngine::Visit()
@ 0x556be1ef168e clang::ento::ExprEngine::ProcessStmt()
@ 0x556be1ef13ab clang::ento::ExprEngine::processCFGElement()
@ 0x556be1f14f8e clang::ento::CoreEngine::HandleBlockEntrance()
@ 0x556be1f1480e clang::ento::CoreEngine::dispatchWorkItem()
@ 0x556be1f144bd clang::ento::CoreEngine::ExecuteWorkList()
@ 0x556be1c4a0bc (anonymous
namespace)::AnalysisConsumer::ActionExprEngine()
@ 0x556be1c49c36 (anonymous namespace)::AnalysisConsumer::HandleCode()
@ 0x556be1c359c4 (anonymous
namespace)::AnalysisConsumer::HandleTranslationUnit()
--
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 37502] New: _mm_set_ps is lowered badly with sse4
https://bugs.llvm.org/show_bug.cgi?id=37502
Bug ID: 37502
Summary: _mm_set_ps is lowered badly with sse4
Product: libraries
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: Backend: X86
Assignee: unassignedb...@nondot.org
Reporter: jmuizel...@mozilla.com
CC: llvm-bugs@lists.llvm.org
__m128 f(float aYScale, float aXScale) {
return _mm_set_ps(aYScale, aXScale, aYScale, aXScale);
}
With -mssse3 this compiles to:
unpcklps%xmm0, %xmm1# xmm1 =
xmm1[0],xmm0[0],xmm1[1],xmm0[1]
movddup %xmm1, %xmm0# xmm0 = xmm1[0,0]
with -mssse4 this compiles to:
movaps %xmm1, %xmm2
insertps$16, %xmm0, %xmm2 # xmm2 = xmm2[0],xmm0[0],xmm2[2,3]
insertps$32, %xmm1, %xmm2 # xmm2 = xmm2[0,1],xmm1[0],xmm2[3]
insertps$48, %xmm0, %xmm2 # xmm2 = xmm2[0,1,2],xmm0[0]
movaps %xmm2, %xmm0
llvm-mca -mcpu=haswell agrees that the ssse3 version is better:
Iterations: 1
Instructions: 2
Total Cycles: 5
Dispatch Width: 4
IPC:0.40
vs
Iterations: 1
Instructions: 5
Total Cycles: 8
Dispatch Width: 4
IPC:0.62
--
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 6527 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in ComplexExprEvaluator::VisitBinaryOperator
Updates: Labels: Deadline-Approaching Comment #2 on issue 6527 by sheriff...@chromium.org: llvm/clang-fuzzer: Stack-overflow in ComplexExprEvaluator::VisitBinaryOperator https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6527#c2 This bug is approaching its deadline for being fixed, and will be automatically derestricted within 7 days. If a fix is planned within 2 weeks after the deadline has passed, a grace extension can be granted. - Your friendly Sheriffbot -- 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 6528 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-indvars: Out-of-memory in llvm_llvm-opt-fuzzer--x86_64-indvars
Updates: Labels: Deadline-Approaching Comment #2 on issue 6528 by sheriff...@chromium.org: llvm/llvm-opt-fuzzer--x86_64-indvars: Out-of-memory in llvm_llvm-opt-fuzzer--x86_64-indvars https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6528#c2 This bug is approaching its deadline for being fixed, and will be automatically derestricted within 7 days. If a fix is planned within 2 weeks after the deadline has passed, a grace extension can be granted. - Your friendly Sheriffbot -- 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 37503] New: Assertion failure in clang::ento::SValBuilder::evalBinOp
https://bugs.llvm.org/show_bug.cgi?id=37503
Bug ID: 37503
Summary: Assertion failure in
clang::ento::SValBuilder::evalBinOp
Product: clang
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Static Analyzer
Assignee: dcough...@apple.com
Reporter: ale...@google.com
CC: ekarpen...@apple.com, llvm-bugs@lists.llvm.org,
noqnoq...@gmail.com
$ cat test-SValBuilder__evalBinOp.cc
void strcpy(char *, char *);
class a {
public:
static void *b();
};
char c;
char ***f;
void d() {
*(unsigned char **)f = (unsigned char *)a::b();
char **e = *f;
strcpy(*e, &c);
}
$ clang-tidy -checks=-*,clang-analyzer* test-SValBuilder__evalBinOp.cc --
assertion failed at clang/lib/StaticAnalyzer/Core/SValBuilder.cpp:427 in
clang::ento::SVal
clang::ento::SValBuilder::evalBinOp(clang::ento::ProgramStateRef,
BinaryOperator::Opcode, clang::ento::SVal, clang::ento::SVal, clang::QualType):
op == BO_Add
@ 0x5646c4981cb6 __assert_fail
@ 0x5646c266903c clang::ento::SValBuilder::evalBinOp()
@ 0x5646c26691bc clang::ento::SValBuilder::evalEQ()
@ 0x5646c261bfe5 (anonymous namespace)::CStringChecker::assumeZero()
@ 0x5646c261c1eb (anonymous namespace)::CStringChecker::checkNonNull()
@ 0x5646c261e9ac (anonymous
namespace)::CStringChecker::evalStrcpyCommon()
@ 0x5646c261acf2 (anonymous namespace)::CStringChecker::evalStrcpy()
@ 0x5646c2619822 clang::ento::eval::Call::_evalCall<>()
@ 0x5646c26cd24e clang::ento::CheckerManager::runCheckersForEvalCall()
@ 0x5646c2710683 clang::ento::ExprEngine::evalCall()
@ 0x5646c2710412 clang::ento::ExprEngine::VisitCallExpr()
@ 0x5646c26de913 clang::ento::ExprEngine::Visit()
@ 0x5646c26da68e clang::ento::ExprEngine::ProcessStmt()
@ 0x5646c26da3ab clang::ento::ExprEngine::processCFGElement()
@ 0x5646c26fe065 clang::ento::CoreEngine::HandlePostStmt()
@ 0x5646c26fd4bd clang::ento::CoreEngine::ExecuteWorkList()
@ 0x5646c24330bc (anonymous
namespace)::AnalysisConsumer::ActionExprEngine()
@ 0x5646c2432c36 (anonymous namespace)::AnalysisConsumer::HandleCode()
@ 0x5646c241e9c4 (anonymous
namespace)::AnalysisConsumer::HandleTranslationUnit()
--
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 24986] Regression in __uuidof support: &__uuidof(X) template parameter turns into __uuidof(X)
https://bugs.llvm.org/show_bug.cgi?id=24986 Nico Weber changed: What|Removed |Added Resolution|--- |FIXED CC||nicolaswe...@gmx.de Status|NEW |RESOLVED --- Comment #13 from Nico Weber --- r332614, with what I think is the 'quick hack fix' mentioned in comment 7. -- 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 13707] [meta] VCPP compatibility issues
https://bugs.llvm.org/show_bug.cgi?id=13707 Bug 13707 depends on bug 24986, which changed state. Bug 24986 Summary: Regression in __uuidof support: &__uuidof(X) template parameter turns into __uuidof(X) https://bugs.llvm.org/show_bug.cgi?id=24986 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 13707] [meta] VCPP compatibility issues
https://bugs.llvm.org/show_bug.cgi?id=13707 Bug 13707 depends on bug 12845, which changed state. Bug 12845 Summary: Missing __VA_ARGS__ extension in Microsoft mode https://bugs.llvm.org/show_bug.cgi?id=12845 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 12845] Missing __VA_ARGS__ extension in Microsoft mode
https://bugs.llvm.org/show_bug.cgi?id=12845 Nico Weber changed: What|Removed |Added Status|NEW |RESOLVED CC||nicolaswe...@gmx.de Resolution|--- |FIXED --- Comment #7 from Nico Weber --- This seems to be working 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] [Bug 37504] New: Lambda should implicitly capture constexpr variable
https://bugs.llvm.org/show_bug.cgi?id=37504
Bug ID: 37504
Summary: Lambda should implicitly capture constexpr variable
Product: clang
Version: 6.0
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: C++14
Assignee: unassignedclangb...@nondot.org
Reporter: ufosp...@gmail.com
CC: llvm-bugs@lists.llvm.org
Created attachment 20314
--> https://bugs.llvm.org/attachment.cgi?id=20314&action=edit
sample to reproduce the issue
In the example attached, constexpr std::size_t i should be captured with empty
capture list [] but it is not the case in certain conditions. Works fine with
g++ 7.3.0:
constexpr std::size_t i = 100;
// this is OK
run([] { std::cout << i << '\n'; });
// this fails to compile
run([/*i*/] {
std::vector v(1, i);
std::cout << v[0] << '\n';
});
In my real code, I need [i] to make it compile as here but if I write [i], I
get the following warning:
warning: lambda capture 'i' is not required to be captured for this use
[-Wunused-lambda-capture]
which is strange because if I remove i from the capture list, it does not
compile.
I do not get this warning with this sample, I did not find how to reproduce it
in a small sample.
I do not know if this is correct but this page:
http://en.cppreference.com/w/cpp/language/lambda
says:
"A lambda expression can read the value of a variable without capturing it if
the variable
- has const non-volatile integral or enumeration type and has been initialized
with a constant expression, or
- is constexpr and trivially copy constructible."
I have not been able to find where it comes from in the standard. The 2014
standard says in 5.1.2.12 :
"A lambda-expression with an associated capture-default that does not
explicitly capture this or a variable with automatic storage duration (this
excludes any id-expression that has been found to refer to an init-capture’s
associated non-static data member), is said to implicitly capture the entity
(i.e., this or a variable) if the compound-statement:
— odr-uses (3.2) the entity, or
— names the entity in a potentially-evaluated expression (3.2) where the
enclosing full-expression depends on a generic lambda parameter declared within
the reaching scope of the lambda-expression.
But this is unclear to me.
--
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 37505] New: Missing intrinsics 4FMAPS and 4VNNIW not implemented
https://bugs.llvm.org/show_bug.cgi?id=37505 Bug ID: 37505 Summary: Missing intrinsics 4FMAPS and 4VNNIW not implemented Product: clang Version: 6.0 Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: Headers Assignee: unassignedclangb...@nondot.org Reporter: christophe.j.he...@gmail.com CC: llvm-bugs@lists.llvm.org GCC 7 supports them. I tested 4FMAPS with GCC 7 and it is working. It would be great to support these intrinsics as they are #1 reason for KNM. -- 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 28154] [meta] Add support for CodeView, the MSVC-compatible debug information format
https://bugs.llvm.org/show_bug.cgi?id=28154 Zachary Turner 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 13707] [meta] VCPP compatibility issues
https://bugs.llvm.org/show_bug.cgi?id=13707 Bug 13707 depends on bug 28154, which changed state. Bug 28154 Summary: [meta] Add support for CodeView, the MSVC-compatible debug information format https://bugs.llvm.org/show_bug.cgi?id=28154 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 37506] New: vector operations fail to optimize to _mm_testz_si128 / _mm256_testz_si256
https://bugs.llvm.org/show_bug.cgi?id=37506
Bug ID: 37506
Summary: vector operations fail to optimize to _mm_testz_si128
/ _mm256_testz_si256
Product: new-bugs
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: gonzalob...@gmail.com
CC: llvm-bugs@lists.llvm.org
I expect the pmovmskb below to be optimized to a _mm_testz_si128 (see it live:
https://godbolt.org/g/RvyWRR).
The Rust code generating this is:
pub fn is_ascii_vector128(s: &[u8]) -> Result<(), usize> {
use ::simd::*;
let mut i = 0;
let v128 = u8x16::splat(128);
let zero = u8x16::splat(0);
let len = s.len();
while i + u8x16::lanes() * 2 <= len {
let x = unsafe { u8x16::load_unaligned_unchecked(&s.get_unchecked(i..))
};
let y = unsafe { u8x16::load_unaligned_unchecked(&s.get_unchecked(i +
u8x16::lanes()..)) };
let x: u8x16 = x & v128;
let y: u8x16 = y & v128;
if !x.eq(zero).all() || !y.eq(zero).all() {
break;
}
i += u8x16::lanes() * 2;
}
Err(i)
}
The LLVM-IR is:
declare i32 @llvm.x86.sse2.pmovmskb.128(<16 x i8>)
define { i64, i64 } @is_ascii_vector128([0 x i8]* %s.0, i64 %s.1) #0 {
start:
%0 = icmp ult i64 %s.1, 32
br i1 %0, label %bb5, label %bb7.preheader
bb7.preheader:; preds = %start
br label %bb7
bb4: ; preds = %bb17
%1 = add i64 %4, 32
%2 = icmp ugt i64 %1, %s.1
br i1 %2, label %bb5, label %bb7
bb5: ; preds = %bb4, %bb7, %bb17,
%start
%i.0.lcssa = phi i64 [ 0, %start ], [ %i.041, %bb17 ], [ %i.041, %bb7 ], [ %4,
%bb4 ]
%3 = insertvalue { i64, i64 } { i64 1, i64 undef }, i64 %i.0.lcssa, 1
ret { i64, i64 } %3
bb7: ; preds = %bb7.preheader,
%bb4
%4 = phi i64 [ %1, %bb4 ], [ 32, %bb7.preheader ]
%i.041 = phi i64 [ %4, %bb4 ], [ 0, %bb7.preheader ]
%5 = getelementptr inbounds [0 x i8], [0 x i8]* %s.0, i64 0, i64 %i.041
%x.0..sroa_cast.i31 = bitcast i8* %5 to <16 x i8>*
%x.0.copyload.i32 = load <16 x i8>, <16 x i8>* %x.0..sroa_cast.i31, align 1
%x.0.copyload.i32.lobit = ashr <16 x i8> %x.0.copyload.i32,
%x.0.copyload.i32.lobit.not = xor <16 x i8> %x.0.copyload.i32.lobit,
%6 = tail call i32 @llvm.x86.sse2.pmovmskb.128(<16 x i8>
%x.0.copyload.i32.lobit.not)
%7 = icmp eq i32 %6, 65535
br i1 %7, label %bb17, label %bb5
bb17: ; preds = %bb7
%8 = or i64 %i.041, 16
%9 = getelementptr inbounds [0 x i8], [0 x i8]* %s.0, i64 0, i64 %8
%x.0..sroa_cast.i = bitcast i8* %9 to <16 x i8>*
%x.0.copyload.i = load <16 x i8>, <16 x i8>* %x.0..sroa_cast.i, align 1
%x.0.copyload.i.lobit = ashr <16 x i8> %x.0.copyload.i,
%x.0.copyload.i.lobit.not = xor <16 x i8> %x.0.copyload.i.lobit,
%10 = tail call i32 @llvm.x86.sse2.pmovmskb.128(<16 x i8>
%x.0.copyload.i.lobit.not) #10
%11 = icmp eq i32 %10, 65535
br i1 %11, label %bb4, label %bb5
}
attributes #0 = { "target-features"="+sse4.1" }
--
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 37507] New: Add a scheduling model for Nehalem
https://bugs.llvm.org/show_bug.cgi?id=37507 Bug ID: 37507 Summary: Add a scheduling model for Nehalem Product: libraries Version: trunk Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: Backend: X86 Assignee: unassignedb...@nondot.org Reporter: jmuizel...@mozilla.com CC: llvm-bugs@lists.llvm.org ~40% of Firefox users don't have AVX. This is rough proxy for machines that are older than Sandybridge. It would be nice to have a scheduling model for older machines even if just for use with llvm-mca. Perhaps llvm-exegesis can make producing it easier? -- 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 36649] [meta] 6.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=36649 Bug 36649 depends on bug 37491, which changed state. Bug 37491 Summary: Please merge 332444 into 6.0.1 https://bugs.llvm.org/show_bug.cgi?id=37491 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 37491] Please merge 332444 into 6.0.1
https://bugs.llvm.org/show_bug.cgi?id=37491 Tom Stellard changed: What|Removed |Added Fixed By Commit(s)|r332444 |r332444 r332644 Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #5 from Tom Stellard --- Merged: r332644 -- 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 37508] New: Clang parsing the header file in spite of not finding it
https://bugs.llvm.org/show_bug.cgi?id=37508 Bug ID: 37508 Summary: Clang parsing the header file in spite of not finding it Product: clang Version: 4.0 Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: C++ Assignee: unassignedclangb...@nondot.org Reporter: mmanu.chaturv...@gmail.com CC: dgre...@apple.com, llvm-bugs@lists.llvm.org Created attachment 20315 --> https://bugs.llvm.org/attachment.cgi?id=20315&action=edit Can be run like this: `bash main.sh clang-4.0` This may not be a bug but a feature. Script to reproduce is attached. When gcc-5.4 is used as the compiler, we end up with one error which says that the compiler couldn't find the header file. However, when clang-4.0 is used as the compiler, we end up with two error messages, one claiming that it couldn't find the header file and that it can be included with quotes, and then that there is a syntax error in the header file. It seems like this is some kind of "FixIt" that clang-4.0 does by looking into the directory and making a useful recommendation, but I wonder if parsing the header file anyways and displaying syntax errors is something it should be doing. Sorry for the spam if this is behavior is intentional. -- 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 36649] [meta] 6.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=36649 Bug 36649 depends on bug 37444, which changed state. Bug 37444 Summary: Merge r330926 and r330927 into the 6.0.1 release (ConfigFiles) https://bugs.llvm.org/show_bug.cgi?id=37444 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 37444] Merge r330926 and r330927 into the 6.0.1 release (ConfigFiles)
https://bugs.llvm.org/show_bug.cgi?id=37444 Tom Stellard changed: What|Removed |Added Status|NEW |RESOLVED Fixed By Commit(s)|r330926 r330927 |r330926 r330927 r332649 ||r332650 Resolution|--- |FIXED --- Comment #3 from Tom Stellard --- Merged: r332649 r332650 -- 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 36594] Merge r324581 into the 6.0 branch : [AArch64] Don't materialize 0 with "fmov h0, .." when FullFP16 is not supported
https://bugs.llvm.org/show_bug.cgi?id=36594 Tom Stellard changed: What|Removed |Added Status|REOPENED|RESOLVED Fixed By Commit(s)|r323816 r324581 |r323816 r324581 r332651 ||r332655 Resolution|--- |FIXED --- Comment #7 from Tom Stellard --- Merged: r332651 r332655 -- 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 36649] [meta] 6.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=36649 Bug 36649 depends on bug 36594, which changed state. Bug 36594 Summary: Merge r324581 into the 6.0 branch : [AArch64] Don't materialize 0 with "fmov h0, .." when FullFP16 is not supported https://bugs.llvm.org/show_bug.cgi?id=36594 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 37509] New: Merge r331990 into the 6.0 branch : [PR37339] Fix assertion in FunctionComparator::cmpInlineAsm
https://bugs.llvm.org/show_bug.cgi?id=37509 Bug ID: 37509 Summary: Merge r331990 into the 6.0 branch : [PR37339] Fix assertion in FunctionComparator::cmpInlineAsm Product: new-bugs Version: 6.0 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: tstel...@redhat.com CC: llvm-bugs@lists.llvm.org Blocks: 36649 Is it OK to merge the following revision(s) to the 6.0 branch? Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=36649 [Bug 36649] [meta] 6.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 37510] New: RewriteStatepointsForGC don't relocate aggregate members
https://bugs.llvm.org/show_bug.cgi?id=37510 Bug ID: 37510 Summary: RewriteStatepointsForGC don't relocate aggregate members Product: libraries Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: Scalar Optimizations Assignee: unassignedb...@nondot.org Reporter: r...@gmx.net CC: llvm-bugs@lists.llvm.org It seems that the RewriteStatepointsForGC pass doesn't relocate pointer members of an aggregate SSA value that would otherwise, as top-level SSA values, be relocated. This is rather surprising and should probably be fixed, since the pointer can not be reached otherwise, and so could be invalidated by the next function 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 37471] Merge r332342 into the 6.0 branch : [MergeFunctions] Fix merging of small weak functions
https://bugs.llvm.org/show_bug.cgi?id=37471 Tom Stellard changed: What|Removed |Added Fixed By Commit(s)|r332342 |r332342 r332662 Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Tom Stellard --- Merged: r332662 -- 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 36649] [meta] 6.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=36649 Bug 36649 depends on bug 37471, which changed state. Bug 37471 Summary: Merge r332342 into the 6.0 branch : [MergeFunctions] Fix merging of small weak functions https://bugs.llvm.org/show_bug.cgi?id=37471 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 37492] Type merging in some PDBs results in bad pointer typedefs
https://bugs.llvm.org/show_bug.cgi?id=37492 Reid Kleckner changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Reid Kleckner --- This was a bug in type merging, but only in the *compile* step, not the link step, which was pretty weird. The bug was in global type hashing, which is what the compiler always uses now. The linker doesn't. Should be fixed by r332664, it was a one line fix to include the record prefix in the hashed bytes. -- 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 37511] New: Supoptimal jumps in code generation
https://bugs.llvm.org/show_bug.cgi?id=37511
Bug ID: 37511
Summary: Supoptimal jumps in code generation
Product: libraries
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Common Code Generator Code
Assignee: unassignedb...@nondot.org
Reporter: david.bolvan...@gmail.com
CC: llvm-bugs@lists.llvm.org
Hello,
code:
int main () {
std::ifstream is ("test.txt", std::ifstream::binary);
if (is) {
// get length of file:
is.seekg (0, is.end);
int length = is.tellg();
is.seekg (0, is.beg);
}
return 0;
}
clang++ -O3 -stdlib=libc++
Lines with look strange for me.
X86 ASM:
...
pop r15
ret
jmp .LBB0_15 **
.LBB0_15:
mov r15, rax
mov qword ptr [rsp], offset vtable for std::__1::basic_ifstream >+24
mov qword ptr [rsp + 184], offset vtable for std::__1::basic_ifstream >+64
jmp .LBB0_16
mov r15, rax **
.LBB0_16:
mov rdi, rbx
call std::__1::basic_filebuf
>::~basic_filebuf()
jmp .LBB0_17
mov r15, rax **
.LBB0_17:
...
Godbolt link: https://godbolt.org/g/iSAZxM (lines 70 - 80)
--
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 37485] LLDB reads wrong registers on 64bit Windows
https://bugs.llvm.org/show_bug.cgi?id=37485 Stella Stamenova changed: What|Removed |Added Resolution|--- |FIXED CC||sti...@microsoft.com Status|NEW |RESOLVED --- Comment #3 from Stella Stamenova --- I committed your patch to the mainline. Thanks! This fixed 8 or so tests in the lldbsuite as well. -- 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 37512] New: Please merge r331925 and r331928 into 6.0.1
https://bugs.llvm.org/show_bug.cgi?id=37512 Bug ID: 37512 Summary: Please merge r331925 and r331928 into 6.0.1 Product: new-bugs Version: 6.0 Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: manojgu...@google.com CC: aa...@aaronballman.com, llvm-bugs@lists.llvm.org, ndesaulni...@google.com, tstel...@redhat.com Blocks: 36649 r331925 adds support for __attribute((no_stack_protector)) needed for a Linux kernel crash issue. r331928 is fix for a test case that was missed in r331925. https://reviews.llvm.org/rL331925 https://reviews.llvm.org/rL331928 Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=36649 [Bug 36649] [meta] 6.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 36649] [meta] 6.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=36649 Bug 36649 depends on bug 37509, which changed state. Bug 37509 Summary: Merge r331990 into the 6.0 branch : [PR37339] Fix assertion in FunctionComparator::cmpInlineAsm https://bugs.llvm.org/show_bug.cgi?id=37509 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 37509] Merge r331990 into the 6.0 branch : [PR37339] Fix assertion in FunctionComparator::cmpInlineAsm
https://bugs.llvm.org/show_bug.cgi?id=37509 Tom Stellard changed: What|Removed |Added Fixed By Commit(s)|r331990 |r331990 r332678 Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Tom Stellard --- Merged: r332678 -- 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 37504] Lambda should implicitly capture constexpr variable
https://bugs.llvm.org/show_bug.cgi?id=37504 Frédéric changed: What|Removed |Added Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #6 from Frédéric --- OK, I went to the end of this and I am sorry to have disturbed you but it seems that I was wrong. The thing is that in the same function I had multiple lambdas referring to a constexpr std::size_t. And for some of them I could remove the capture and not for the others. So the warning was related to one of the lambda, and I tried to remove all captures so it did not work. I now understand that if a lambda uses a constexpr variable in a call with a const reference, the constexpr must be capture to have a reference at the time of the call where the reference to the original variable is not accessible. Thanks for your help. -- 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 37513] New: `__has_feature(is_aggregate)` returns `false` even though `__is_aggregate` exists.
https://bugs.llvm.org/show_bug.cgi?id=37513
Bug ID: 37513
Summary: `__has_feature(is_aggregate)` returns `false` even
though `__is_aggregate` exists.
Product: clang
Version: 5.0
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: C++
Assignee: unassignedclangb...@nondot.org
Reporter: mcyp...@gmail.com
CC: dgre...@apple.com, llvm-bugs@lists.llvm.org
The following program prints 1, indicating that `__has_feature(is_aggregate)`
returned `false`, even though `__is_aggregate` is defined.
```
#include
#if __has_feature(is_aggregate)
#error feature
#endif
#if __has_extension(is_aggregate)
#error extension
#endif
struct Agg {};
int main() {
std::cout << __is_aggregate(Agg);
}
```
https://wandbox.org/permlink/mvOCKdmZGaxKoRAu
--
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
