[llvm-dev] [GlobalISel] Narrowing uneven/non-pow-2 types
Dominik Montada via llvm-dev
llvm-dev at lists.llvm.org
Wed Mar 25 00:53:26 PDT 2020
thanks for responding. I left a couple of comments down below.
Am 24.03.20 um 18:26 schrieb Matt Arsenault:
>> On Mar 24, 2020, at 12:24, Dominik Montada via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>> Hi all,
>> recently when working with GlobalISel we have often encountered cases in the legalizer where instructions could not be narrowed because the narrowing code relies on G_UNMERGE_VALUES and therefore requires the source type to be a multiple of the narrow type. Often times these instructions can be widened without any problem to a fitting type.
>> This has us writing legalization rules like `.widenScalarToNextPow2(0, /*MinSize*/ 32).maxScalar(0, s32)` instead of the much simpler `.clampScalar(0, s32 ,s32)`.
>> Although this works and has the desired effect, we feel like that such a rule requires internal knowledge of the legalizer, which can change at any point in the future. Ideally we would only want to say `clampScalar` and let the legalizer handle the rest, even if it requires extending the type before it can be narrowed.
> Being able to specify the order of specific legalization steps is pretty useful, and one area I found frustrating in SelectionDAG. For example, we do use custom lowering in some places to hack around the order that operation expansion and legalization is done. In this particular case, another helper may be useful, since forcing a power of 2 and bounding the size are two distinct constraints.
Hm, I see. That makes a lot of sense. What could such a helper look
like? I was thinking about something along the lines of
clampScalarWithWiden or narrowScalarWithWiden (if you have better
suggestions, I would highly appreciate it) which would be a short-hand
for a widen to the next multiple of the narrow type and narrowScalar.
My main concern here is that if at one point in the future narrowing for
an uneven type suddenly gets supported, I would rather have the
legalizer skip the widen, which would not work with such a helper, as
far as I'm aware.
I guess what I would actually prefer is a helper which first tries to
narrow and if it doesn't work uses widen before trying again.
>> We were now wondering if such a behavior in the legalizer is even desired? I.e. that an instruction is extended to an easier-to-handle type even though narrowing was requested (as long as the narrowing is done in the end)?
> I would need more context on this question, and what specifically you are hitting. The current set of implemented legalization rules is fairly incomplete, and not all operations use a consistent strategy
Basically we have an architecture which only works on 32-bit types and
we are starting to hit many of the edge cases. For example this
particular question arose because we are seeing the following LLVM-IR,
which we cannot legalize with our current legalization rules:
%6 = zext i32 %5 to i33
%7 = zext i32 %0 to i33
%8 = mul i33 %6, %7
%9 = lshr i33 %8, 1
%10 = trunc i33 %9 to i32
.clampScalar(0, s32, s32);
.clampScalar(1, s32, s32)
.clampScalar(0, s32, s32);
We would be able to legalize the above code if we just add a
widenScalarToNextPow2 before the clampScalar in both cases. However we
only know that this will work because we looked at the narrowing code
and we are now having an internal discussion if our legalization rules
should rely on such implementation details. Furthermore, this then
raises the question if other instructions also need this
widen-before-narrow pattern because a straight narrow action would not
work, even though we're not seeing any actual failures due to them so far.
I hope that clarifies the context of this problem.
Dominik Montada Email: dominik.montada at hightec-rt.com
HighTec EDV-Systeme GmbH Phone: +49 681 92613 19
Europaallee 19 Fax: +49-681-92613-26
D-66113 Saarbrücken WWW: http://www.hightec-rt.com
Managing Director: Vera Strothmann
Register Court: Saarbrücken, HRB 10445, VAT ID: DE 138344222
This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient please notify the sender immediately
and destroy this e-mail. Any unauthorised copying, disclosure or
distribution of the material in this e-mail is strictly forbidden.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 5409 bytes
Desc: not available
More information about the llvm-dev