<html>
<head>
<base href="https://bugs.llvm.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - llvm::DAGTypeLegalizer::SplitVecOp_MSTORE crash"
href="https://bugs.llvm.org/show_bug.cgi?id=45833">45833</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>llvm::DAGTypeLegalizer::SplitVecOp_MSTORE crash
</td>
</tr>
<tr>
<th>Product</th>
<td>new-bugs
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>PC
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>enhancement
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>new bugs
</td>
</tr>
<tr>
<th>Assignee</th>
<td>unassignedbugs@nondot.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>ajcbik@google.com
</td>
</tr>
<tr>
<th>CC</th>
<td>htmldeveloper@gmail.com, llvm-bugs@lists.llvm.org
</td>
</tr></table>
<p>
<div>
<pre>This bug is actually a continuation of the earlier bug
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - llvm::EVT::getHalfNumVectorElementsVT assert when running MLIR"
href="show_bug.cgi?id=45563">https://bugs.llvm.org/show_bug.cgi?id=45563</a>
that exposed a problem with loads on unusual vector lengths.
As I suspected, a similar issue arises for stores.
Take the following MLIR input
func @transfer_write13_1d(%A : memref<?xf32>, %base: index) {
%f = constant 13.0 : f32
%v = splat %f : vector<13xf32>
vector.transfer_write %v, %A[%base]
{permutation_map = affine_map<(d0) -> (d0)>}
: vector<13xf32>, memref<?xf32>
return
}
and run it through the lowering to LLVM-IR path for execution, and it crashes
LLVM as follows
F0507 12:50:26.508680 34021 logging.cc:106] assert.h assertion failed at
third_party/llvm/llvm-project/llvm/include/llvm/CodeGen/ValueTypes.h:371 in
llvm::EVT llvm::EVT::getHalfNumVectorElementsVT(llvm::LLVMContext &) const:
!(EltCnt.Min & 1) && "Splitting vector, but not in half!"
*** Check failure stack trace: ***
@ 0x557cd9079f40 absl::logging_internal::LogMessage::DieIfFatal()
@ 0x557cd9079813 absl::logging_internal::LogMessage::SendToLog()
@ 0x557cd9078ade absl::logging_internal::LogMessage::Flush()
@ 0x557cd907ad98
absl::logging_internal::LogMessageFatal::~LogMessageFatal()
@ 0x557cd9076a40 __assert_fail
@ 0x557cd72a6807 llvm::EVT::getHalfNumVectorElementsVT()
@ 0x557cd729c1cb llvm::SelectionDAG::GetSplitDestVTs()
@ 0x557cd739c534 llvm::DAGTypeLegalizer::SplitVecOp_MSTORE()
@ 0x557cd7398366 llvm::DAGTypeLegalizer::SplitVectorOperand()
@ 0x557cd735cb0d llvm::DAGTypeLegalizer::run()
The fix is probably very similar.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>