[llvm-bugs] [Bug 45083] Assertion `E->isRValue() && "missing lvalue-to-rvalue conv in bool condition"' failed
https://bugs.llvm.org/show_bug.cgi?id=45083 Hans Wennborg changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #12 from Hans Wennborg --- (In reply to Hans Wennborg from comment #10) > (In reply to Luke from comment #9) > > Reopening to track 10.x backport of bdad0a1b7927 > > Pushed to 10.x as 3a843031a5ad83a00d2603f623881cb2b2bf719d. Thanks, Richard! The current status is that bdad0a1b7927 was reverted on master. A new fix landed yesterday as 5c845c1c50ac89a6f12557d1571678f3d1432478. I'm currently waiting to see how that fares, and if all is well, I will push that to 10.x as well. Keeping the bug open in the meantime. -- 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 44555] [meta] 10.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=44555 Bug 44555 depends on bug 45083, which changed state. Bug 45083 Summary: Assertion `E->isRValue() && "missing lvalue-to-rvalue conv in bool condition"' failed https://bugs.llvm.org/show_bug.cgi?id=45083 What|Removed |Added Status|RESOLVED|REOPENED 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 45173] New: cannot access any object in global module fragment from exported template function
https://bugs.llvm.org/show_bug.cgi?id=45173
Bug ID: 45173
Summary: cannot access any object in global module fragment
from exported template function
Product: clang
Version: 10.0
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Priority: P
Component: Modules
Assignee: unassignedclangb...@nondot.org
Reporter: sw6u...@gmail.com
CC: dgre...@apple.com, llvm-bugs@lists.llvm.org,
richard-l...@metafoo.co.uk
Created attachment 23220
--> https://bugs.llvm.org/attachment.cgi?id=23220&action=edit
source files - build with build.bat or build.sh
// accessing foo ( which is defined in global-module-fragment )
// in an exported-non-template-function succeeded
// but failed in an exported-template-function.
// see attached files and build with build.bat or build.sh
// my_module.cppm
module;
#include "foo.h" // inline void foo() {}
export module my_module;
export namespace my_module
{
void bar()
{
::foo(); // OK
}
template< class Type >
void baz()
{
::foo(); // 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
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 44555] [meta] 10.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=44555 Bug 44555 depends on bug 45124, which changed state. Bug 45124 Summary: clang-10 regression with __thread and deduction guides https://bugs.llvm.org/show_bug.cgi?id=45124 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 45124] clang-10 regression with __thread and deduction guides
https://bugs.llvm.org/show_bug.cgi?id=45124 Hans Wennborg changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #7 from Hans Wennborg --- (In reply to Sylvestre Ledru from comment #6) > @Hans, could you please cherry-pick it for 10? > thanks Yes, pushed to 10.x as 5b5a111c6794a0bb0385d04721ea854dd56da357. -- 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 45174] New: Flaky test failures on build bots
https://bugs.llvm.org/show_bug.cgi?id=45174 Bug ID: 45174 Summary: Flaky test failures on build bots Product: OpenMP Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P Component: Runtime Library Assignee: unassignedb...@nondot.org Reporter: jh7370.2...@my.bristol.ac.uk CC: llvm-bugs@lists.llvm.org I've had a couple of recent commits where one or more openmp tests failed for some reason. The changes I've made are completely unrelated, so it most likely means that either the tests themselves are flaky, or possibly the build bot has some kind of configuration issue. Here's the most recent example: http://lab.llvm.org:8011/builders/openmp-gcc-x86_64-linux-debian/builds/4942 The specific test I've seen fail most often is "libomp::bug_nested_proxy_task.c". -- 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 45175] New: [Machinepipeliner] Bug in creating AdjacencyStructure for multiple Output dependence chains
https://bugs.llvm.org/show_bug.cgi?id=45175
Bug ID: 45175
Summary: [Machinepipeliner] Bug in creating AdjacencyStructure
for multiple Output dependence chains
Product: clang
Version: trunk
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: P
Component: LLVM Codegen
Assignee: unassignedclangb...@nondot.org
Reporter: lama.s...@intel.com
CC: llvm-bugs@lists.llvm.org, neeil...@live.com,
richard-l...@metafoo.co.uk
The code creating a back-edge on the first and last nodes of a dependence chain
in createAdjacencyStructure:
// Add any successor to the adjacency matrix and exclude duplicates.
for (auto &SI : SUnits[i].Succs) {
// Only create a back-edge on the first and last nodes of a dependence
// chain. This records any chains and adds them later.
if (SI.getKind() == SDep::Output) {
int N = SI.getSUnit()->NodeNum;
int BackEdge = i;
auto Dep = OutputDeps.find(BackEdge);
if (Dep != OutputDeps.end()) {
BackEdge = Dep->second;
OutputDeps.erase(Dep);
}
OutputDeps[N] = BackEdge;
}
generates incorrect code for cases where there are more than one Output def in
the nodeset.
for example:
1) out1 = inst1..
2) out1 = inst2..
3) out1 = inst3..
4) out1 = inst4..
this will correctly add a back-edge from 4 to 1
but when there are 2 defs
1) out1,out2 = inst1..
2) out1,out2 = inst2..
3) out1,out2 = inst3..
4) out1,out2 = inst4..
it will add a backedge from 4 to 3, thus creating wrong recurrence node sets.
The code should generate a separate chain for each def.
unfortunately, I cou;dn't generate Hexagon/Power PC tests for this case.
--
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 40281] Remove some/all of the X86ISD double shift opcodes
https://bugs.llvm.org/show_bug.cgi?id=40281 Bug 40281 depends on bug 39467, which changed state. Bug 39467 Summary: [X86] Replace X86ISD SHLD\SHRD with ISD FSHL\FSHR https://bugs.llvm.org/show_bug.cgi?id=39467 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 39467] [X86] Replace X86ISD SHLD\SHRD with ISD FSHL\FSHR
https://bugs.llvm.org/show_bug.cgi?id=39467 Simon Pilgrim changed: What|Removed |Added Fixed By Commit(s)|348353 |rL348353,rGb3b4727a3e7e Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #4 from Simon Pilgrim --- (In reply to Simon Pilgrim from comment #3) > https://reviews.llvm.org/D75748 replaces (most) X86ISD::SHLD/SHRD usage with > ISD::FSHL/FSHR - the i16 case is the annoying one.. This landed in rGb3b4727a3e7e which converts i32/i64 types to ISD::FSHL/FSHR and the i16 types now use a X86ISD::FSHL/FSHR equivalent (to avoid the amt modulo 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 28598] Assigning a gsl::span to a gsl::span const causes segmentation fault during compilation.
https://bugs.llvm.org/show_bug.cgi?id=28598 Nico Weber changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED CC||nicolaswe...@gmx.de --- Comment #1 from Nico Weber --- No longer seems to repro at trunk: $ ~/src/llvm-project/out/gn/bin/clang -c main.cpp -std=c++14 main.cpp:15:7: error: cannot initialize a member subobject of type 'add_pointer_t' with an lvalue of type 'const add_pointer_t' data_(other.data_) ^ ~~~ main.cpp:30:26: note: in instantiation of function template specialization 'span::span' requested here span const span = getSpan(); ^ 1 error generated. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 45139] intermittent error of "#pragma omp requires unified_shared_memory' not used consistently!" when mixing Python and OpenMP target offload
https://bugs.llvm.org/show_bug.cgi?id=45139 Alexey Bataev changed: What|Removed |Added Resolution|--- |FIXED Fixed By Commit(s)||c422d69b1ad7ae3fdbe0d4ec795 ||a2931e08459f7 Status|NEW |RESOLVED --- Comment #6 from Alexey Bataev --- Fixed in c422d69b1ad7ae3fdbe0d4ec795a2931e08459f7 -- 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 45176] New: [ms] wrong calling convention for member functions returning simd types in 64-bit
https://bugs.llvm.org/show_bug.cgi?id=45176 Bug ID: 45176 Summary: [ms] wrong calling convention for member functions returning simd types in 64-bit Product: clang Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: LLVM Codegen Assignee: unassignedclangb...@nondot.org Reporter: nicolaswe...@gmx.de CC: llvm-bugs@lists.llvm.org, neeil...@live.com, richard-l...@metafoo.co.uk Callee side: https://godbolt.org/z/5uyPBD Looks like rdx contains the address of the return buffer before the call, and rax contains the address of where the data was written after the call. Calling side: https://godbolt.org/z/_FMkTv Both f and g tailcall in clang, but only g does in MSVC -- f copies off the stack first. (reported here: https://twitter.com/_xalri/status/1237690440050249733 ; I tweaked the flags a bit to pass an msvc --target) See also https://docs.microsoft.com/en-us/cpp/build/x64-calling-convention?view=vs-2019 (ctrl-f __m128) -- 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 45178] New: Crash in WebAssembly Instruction Selection
https://bugs.llvm.org/show_bug.cgi?id=45178 Bug ID: 45178 Summary: Crash in WebAssembly Instruction Selection Product: libraries Version: trunk Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: Backend: WebAssembly Assignee: unassignedb...@nondot.org Reporter: a...@pdx.edu CC: llvm-bugs@lists.llvm.org Created attachment 23223 --> https://bugs.llvm.org/attachment.cgi?id=23223&action=edit Observed backtrace This is a follow-on bug from https://bugs.llvm.org/show_bug.cgi?id=44954. That issue appears to be resolved by updating Emscripten (for me: `git pull && ./emsdk install tot && ./emsdk activate tot`). However, while attempting to compile libaom with SIMDe to WebAssembly, I observed the attached crash (with associated source and script). -- 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 21167 in oss-fuzz: llvm:llvm-isel-fuzzer--x86_64-O2: ASSERT: BitWidth == RHS.BitWidth && "Comparison requires equal bit widths"
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, d...@google.com, mit...@google.com, bigchees...@gmail.com, eney...@google.com, llvm-b...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2020-03-11 Type: Bug New issue 21167 by ClusterFuzz-External: llvm:llvm-isel-fuzzer--x86_64-O2: ASSERT: BitWidth == RHS.BitWidth && "Comparison requires equal bit widths" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=21167 Detailed Report: https://oss-fuzz.com/testcase?key=5637484299157504 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: llvm-isel-fuzzer--x86_64-O2 Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: BitWidth == RHS.BitWidth && "Comparison requires equal bit widths" DAGCombiner::visit DAGCombiner::combine Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201811191645:201811200233 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5637484299157504 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 45179] New: [LNT] submissions list for machine should be ordered by start date.
https://bugs.llvm.org/show_bug.cgi?id=45179
Bug ID: 45179
Summary: [LNT] submissions list for machine should be ordered
by start date.
Product: LNT
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: LNT
Assignee: unassignedb...@nondot.org
Reporter: yuanfang.c...@sony.com
CC: chris.matth...@apple.com, llvm-bugs@lists.llvm.org
Currently `@v4_route("/recent_activity")` submissions list is sorted by 'start
time'.
http://lnt.llvm.org/db_default/v4/nts/recent_activity
submissions list for machine should be the same.
http://lnt.llvm.org/db_default/v4/nts/machine/1364
--
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
