diff options
author | Tom Eccles <tom.eccles@arm.com> | 2023-05-23 11:38:17 +0000 |
---|---|---|
committer | Tom Eccles <tom.eccles@arm.com> | 2023-05-25 11:02:42 +0000 |
commit | 5b65dbd19756fc6522167d4c884d138907026254 (patch) | |
tree | d91d34599eb6f60128c2978e81a915e4c9a56125 /llvm/lib/CodeGen/MachineBasicBlock.cpp | |
parent | 0123deb3a6f0a83095287f51b07c77b7b43ab847 (diff) | |
download | llvm-5b65dbd19756fc6522167d4c884d138907026254.zip llvm-5b65dbd19756fc6522167d4c884d138907026254.tar.gz llvm-5b65dbd19756fc6522167d4c884d138907026254.tar.bz2 |
[flang][hlfir] fix regression in inline elementals
InlineElementals created a regression when inlining elemental
expressions where the type of the result of the hlfir.apply does not
match the hlfir.yield.
This patch ensures the pass doesn't match in these cases, fixing the
regression.
It isn't clear to me what the /right/ solution is:
- Is it actually valid for the hlfir.apply to have a different type
(even just different array bounds?). Should this be enforced in the
verifier?
- Inserting a convert if these types don't match doesn't work because
fir.convert doesn't know how to convert a hlfir.expr. Should this be
added?
Test case is from @vzakhari
Differential Revision: https://reviews.llvm.org/D151202
Diffstat (limited to 'llvm/lib/CodeGen/MachineBasicBlock.cpp')
0 files changed, 0 insertions, 0 deletions