public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kito Cheng <kito.cheng@gmail.com>
To: "Maciej W. Rozycki" <macro@embecosm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	Andrew Waterman <andrew@sifive.com>
Subject: Re: [PATCH] RISC-V: Reset the length to the default of 4 for FP comparisons
Date: Thu, 9 Jun 2022 22:55:27 +0800	[thread overview]
Message-ID: <CA+yXCZDatm--Pa9PcAMSvatpxs1qMx2-PnB02n+jUOJ5U8CZfA@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.2206082325030.10833@tpp.orcam.me.uk>

LGTM, *f<quiet_pattern>_quiet<ANYF:mode><X:mode>4_default and
*f<quiet_pattern>_quiet<ANYF:mode><X:mode>4_snan has set their own
length and the only user of this setting is
*cstore<ANYF:mode><X:mode>4, but apparently the length if 4 for that
not 8.

Thanks!

On Thu, Jun 9, 2022 at 9:36 PM Maciej W. Rozycki <macro@embecosm.com> wrote:
>
> The default length for floating-point compare operations is overridden
> to 8, however the FEQ.fmt, FLT.fmt, FLE.fmt machine instructions and
> FGE.fmt, FGT.fmt assembly idioms the relevant RTL insns produce are all
> 4 bytes long each.  And all the floating-point compare RTL insns that
> produce multiple machine instructions explicitly set their lengths.
>
> Remove the override then, letting the default of 4 apply for the single
> instruction case.
>
>         gcc/
>         * config/riscv/riscv.md (length): Remove the explicit setting
>         for "fcmp".
> ---
> Hi,
>
>  So for:
>
> int
> feq (float x, float y)
> {
>   return x == y;
> }
>
> we get:
>
>         .globl  feq
>         .type   feq, @function
> feq:
>         feq.s   a0,fa0,fa1      # 15    [c=4 l=8]  *cstoresfdi4
>         ret             # 24    [c=0 l=4]  simple_return
>         .size   feq, .-feq
>
> which is obviously wrong given:
>
> Disassembly of section .text:
>
> 0000000000000000 <feq>:
>    0:   a0b52553                feq.s   a0,fa0,fa1
>    4:   8082                    ret
>
> (hmm tabs are odd here too, but that's a binutils issue).  I note that the
> override has always been there since the RISC-V port landed, so I take it
> it's a missed leftover from an earlier situation.
>
>  With the change in place we instead get:
>
>         .globl  feq
>         .type   feq, @function
> feq:
>         feq.s   a0,fa0,fa1      # 15    [c=4 l=4]  *cstoresfdi4
>         ret             # 24    [c=0 l=4]  simple_return
>         .size   feq, .-feq
>
> which I find so relieving.
>
>  No regressions in the testsuite (and I haven't checked how it affects
> instruction scheduling, especially with `-Os', but I think it's obviously
> correct really).  OK to apply?
>
>   Maciej
> ---
>  gcc/config/riscv/riscv.md |    2 --
>  1 file changed, 2 deletions(-)
>
> gcc-riscv-fcmp-length.diff
> Index: gcc/gcc/config/riscv/riscv.md
> ===================================================================
> --- gcc.orig/gcc/config/riscv/riscv.md
> +++ gcc/gcc/config/riscv/riscv.md
> @@ -231,8 +231,6 @@
>
>           (eq_attr "got" "load") (const_int 8)
>
> -         (eq_attr "type" "fcmp") (const_int 8)
> -
>           ;; SHIFT_SHIFTs are decomposed into two separate instructions.
>           (eq_attr "move_type" "shift_shift")
>                 (const_int 8)

  reply	other threads:[~2022-06-09 14:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-09 13:36 Maciej W. Rozycki
2022-06-09 14:55 ` Kito Cheng [this message]
2022-06-13 21:31   ` Maciej W. Rozycki

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=CA+yXCZDatm--Pa9PcAMSvatpxs1qMx2-PnB02n+jUOJ5U8CZfA@mail.gmail.com \
    --to=kito.cheng@gmail.com \
    --cc=andrew@sifive.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=macro@embecosm.com \
    /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).