[llvm-dev] Saturating float-to-int casts

Bevin Hansson via llvm-dev llvm-dev at lists.llvm.org
Mon Sep 7 07:39:20 PDT 2020

I'm the one who has been working on this patch.

I have noticed the test failures, but I cannot reproduce those when I build and test locally, so I haven't actively tried to do anything about them. I don't put much stock in the pre-land tests, they tend to fail in odd ways.
From: llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of David Lloyd via llvm-dev <llvm-dev at lists.llvm.org>
Sent: Friday, September 4, 2020 4:42 PM
To: llvm-dev at lists.llvm.org <llvm-dev at lists.llvm.org>
Subject: Re: [llvm-dev] Saturating float-to-int casts

On Fri, Aug 7, 2020 at 9:19 AM David Lloyd <david.lloyd at redhat.com> wrote:
> I have encountered a need for float-to-int casts that saturate to
> min/max when the value is out of the range of the target type.  It
> seems that there is no intrinsic to do this, currently, but on IRC it
> was pointed out that a patch [1] has been proposed to implement this
> functionality in exactly the way that I was looking for.
> It looks like the discussion has died out but I was hoping maybe to
> kick it off again.
> [1] https://protect2.fireeye.com/v1/url?k=0f2670d1-5186b297-0f26304a-86fc6812c361-8897797f7301e1e5&q=1&e=215b56a1-2b93-4622-a733-7123494b2246&u=https%3A%2F%2Freviews.llvm.org%2FD54749

Looks like a little more activity has happened, and the patch was
rebased, but some unit tests are currently failing (I have no idea how
normal that is but I'm assuming it's a problem - at least the failures
seem related, on the surface anyway).  Seems like the failures are
related to applying these operations to vectors.

- DML • he/him

LLVM Developers mailing list
llvm-dev at lists.llvm.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200907/e335b3e7/attachment.html>

More information about the llvm-dev mailing list