From: Xi Ruoyao <xry111@xry111.site>
To: gcc-patches@gcc.gnu.org
Cc: chenglulu <chenglulu@loongson.cn>, i@xen0n.name, xuchenghua@loongson.cn
Subject: Re: [PATCH v2 1/3] LoongArch: Fix usage of LSX and LASX frint/ftint instructions [PR112578]
Date: Mon, 20 Nov 2023 03:26:20 +0800 [thread overview]
Message-ID: <46927f2b040a7229e6d5f7c79681e104188e8774.camel@xry111.site> (raw)
In-Reply-To: <20231119143037.16443-2-xry111@xry111.site>
On Sun, 2023-11-19 at 22:30 +0800, Xi Ruoyao wrote:
> +;; All these are controlled by -ffp-int-builtin-inexact.
> +(define_int_attr simd_frint_pattern
> + [(UNSPEC_SIMD_FRINTRP "ceil")
> + (UNSPEC_SIMD_FRINTRZ "btrunc")
> + (UNSPEC_SIMD_FRINT "nearbyint")
> + (UNSPEC_SIMD_FRINTRNE "roundeven")
> + (UNSPEC_SIMD_FRINTRM "floor")])
This is wrong. nearbyint is not allowed to raise FE_INEXACT even if -
ffp-int-builtin-inexact. Please abandon this series and I'll send V3.
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2023-11-19 19:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-19 14:30 [PATCH v2 0/3] LoongArch: SIMD fixes and optimizations Xi Ruoyao
2023-11-19 14:30 ` [PATCH v2 1/3] LoongArch: Fix usage of LSX and LASX frint/ftint instructions [PR112578] Xi Ruoyao
2023-11-19 19:26 ` Xi Ruoyao [this message]
2023-11-19 14:30 ` [PATCH v2 2/3] LoongArch: Use standard pattern name and RTX code for LSX/LASX muh instructions Xi Ruoyao
2023-11-19 14:30 ` [PATCH v2 3/3] LoongArch: Use standard pattern name and RTX code for LSX/LASX rotate shift Xi Ruoyao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46927f2b040a7229e6d5f7c79681e104188e8774.camel@xry111.site \
--to=xry111@xry111.site \
--cc=chenglulu@loongson.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=i@xen0n.name \
--cc=xuchenghua@loongson.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).