public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: chenglulu <chenglulu@loongson.cn>
To: Xi Ruoyao <xry111@xry111.site>, gcc-patches@gcc.gnu.org
Cc: i@xen0n.name, xuchenghua@loongson.cn
Subject: Re: [PATCH v3 1/5] LoongArch: Fix usage of LSX and LASX frint/ftint instructions [PR112578]
Date: Thu, 23 Nov 2023 14:35:19 +0800	[thread overview]
Message-ID: <cec4e36d-6da4-ac1c-506f-c808a30ec969@loongson.cn> (raw)
In-Reply-To: <20231120004728.205167-2-xry111@xry111.site>


在 2023/11/20 上午8:47, Xi Ruoyao 写道:
> The usage LSX and LASX frint/ftint instructions had some problems:
>
> 1. These instructions raises FE_INEXACT, which is not allowed with
>     -fno-fp-int-builtin-inexact for most C2x section F.10.6 functions
>     (the only exceptions are rint, lrint, and llrint).
> 2. The "frint" instruction without explicit rounding mode is used for
>     roundM2, this is incorrect because roundM2 is defined "rounding
>     operand 1 to the *nearest* integer, rounding away from zero in the
>     event of a tie".  We actually don't have such an instruction.  Our
>     frintrne instruction is roundevenM2 (unfortunately, this is not
>     documented).
> 3. These define_insn's are written in a way not so easy to hack.
>
> So I removed these instructions and created a "simd.md" file, then added
> them and the corresponding expanders there.  The advantage of the
> simd.md file is we don't need to duplicate the RTL template twice (in
> lsx.md and lasx.md).
/* snip */
> +;; fix_trunc is allowed to raise inexact exception even if
> +;; -fno-fp-int-builtin-inexact.  Because the middle end trys to match
> +;; (FIX x) and it does not know (FIX (UNSPEC_SIMD_FRINTRZ x)), we need
> +;; to use define_insn_and_split instead of define_expand (expanders are
> +;; not considered during matching).

Hi,

  I don’t quite understand this part. Is it because define_insn would be 
duplicated with the above implementation,

so define_insn_and_split is used?


Thanks.

> +(define_insn_and_split "fix_trunc<mode><vimode>2"
> +  [(set (match_operand:<VIMODE> 0 "register_operand" "=f")
> +	(fix:<VIMODE> (match_operand:FVEC 1 "register_operand" "f")))]
> +  ""
> +  "#"
> +  ""
> +  [(const_int 0)]
> +  {
> +    emit_insn (gen_<simd_isa>_<x>vftintrz_<simdifmt_for_f>_<simdfmt> (
> +      operands[0], operands[1]));
> +    DONE;
> +  }
> +  [(set_attr "type" "simd_fcvt")
> +   (set_attr "mode" "<MODE>")])




  reply	other threads:[~2023-11-23  6:35 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-20  0:47 [PATCH v3 0/5] LoongArch: SIMD fixes and optimizations Xi Ruoyao
2023-11-20  0:47 ` [PATCH v3 1/5] LoongArch: Fix usage of LSX and LASX frint/ftint instructions [PR112578] Xi Ruoyao
2023-11-23  6:35   ` chenglulu [this message]
2023-11-23  7:11     ` Xi Ruoyao
2023-11-23  7:31       ` chenglulu
2023-11-23  8:13         ` chenglulu
2023-11-23  9:02           ` Xi Ruoyao
2023-11-23  9:12             ` chenglulu
2023-11-23 10:12               ` Xi Ruoyao
2023-11-23 12:06                 ` Xi Ruoyao
2023-11-23 18:03                 ` Joseph Myers
2023-11-24  2:39                   ` Xi Ruoyao
2023-11-24  8:01                     ` chenglulu
2023-11-24  8:26                       ` Xi Ruoyao
2023-11-24  8:36                         ` chenglulu
2023-11-24  8:42                           ` Xi Ruoyao
2023-11-24  9:46                             ` chenglulu
2023-11-24 10:30                               ` Xi Ruoyao
2023-11-24 14:59                                 ` chenglulu
2023-11-23  8:54         ` Xi Ruoyao
2023-11-20  0:47 ` [PATCH v3 2/5] LoongArch: Use standard pattern name and RTX code for LSX/LASX muh instructions Xi Ruoyao
2023-11-23 12:08   ` chenglulu
2023-11-20  0:47 ` [PATCH v3 3/5] LoongArch: Use standard pattern name and RTX code for LSX/LASX rotate shift Xi Ruoyao
2023-11-23  8:42   ` chenglulu
2023-11-20  0:47 ` [PATCH v3 4/5] LoongArch: Remove lrint_allow_inexact Xi Ruoyao
2023-11-23  8:23   ` chenglulu
2023-11-23  8:58     ` Xi Ruoyao
2023-11-23  9:14       ` chenglulu
2023-11-23 12:24         ` Xi Ruoyao
2023-11-23 14:39           ` chenglulu
2023-11-20  0:47 ` [PATCH v3 5/5] LoongArch: Use LSX for scalar FP rounding with explicit rounding mode Xi Ruoyao
2023-11-29  7:12 ` Pushed: [PATCH v3 0/5] LoongArch: SIMD fixes and optimizations Xi Ruoyao
2023-11-29  7:45   ` chenglulu

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=cec4e36d-6da4-ac1c-506f-c808a30ec969@loongson.cn \
    --to=chenglulu@loongson.cn \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=i@xen0n.name \
    --cc=xry111@xry111.site \
    --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).