public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kito Cheng <kito.cheng@gmail.com>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] RISC-V: Support -fexcess-precision=16
Date: Fri, 9 Sep 2022 17:56:26 +0800	[thread overview]
Message-ID: <CA+yXCZCeULa9pUpP73UwjG0dGZDvbkFTDE8KHqVb8JiT-vpEiQ@mail.gmail.com> (raw)
In-Reply-To: <20220909094326.22995-1-palmer@rivosinc.com>

LGTM, seems like you have landed now, see you soon :)

On Fri, Sep 9, 2022 at 5:44 PM Palmer Dabbelt <palmer@rivosinc.com> wrote:
>
> This fixes f19a327077e ("Support -fexcess-precision=16 which will enable
> FLT_EVAL_METHOD_PROMOTE_TO_FLOAT16 when backend supports _Float16.") on
> RISC-V targets.
>
> gcc/ChangeLog
>
>         PR target/106815
>         * config/riscv/riscv.cc (riscv_excess_precision): Add support
>         for EXCESS_PRECISION_TYPE_FLOAT16.
> ---
>  gcc/config/riscv/riscv.cc | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/gcc/config/riscv/riscv.cc b/gcc/config/riscv/riscv.cc
> index 675d92c0961..9b6d3e95b1b 100644
> --- a/gcc/config/riscv/riscv.cc
> +++ b/gcc/config/riscv/riscv.cc
> @@ -5962,6 +5962,7 @@ riscv_excess_precision (enum excess_precision_type type)
>        return (TARGET_ZFH ? FLT_EVAL_METHOD_PROMOTE_TO_FLOAT16
>                          : FLT_EVAL_METHOD_PROMOTE_TO_FLOAT);
>      case EXCESS_PRECISION_TYPE_IMPLICIT:
> +    case EXCESS_PRECISION_TYPE_FLOAT16:
>        return FLT_EVAL_METHOD_PROMOTE_TO_FLOAT16;
>      default:
>        gcc_unreachable ();
> --
> 2.34.1
>

  reply	other threads:[~2022-09-09  9:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-09  9:43 Palmer Dabbelt
2022-09-09  9:56 ` Kito Cheng [this message]
2022-09-30 22:23   ` Palmer Dabbelt

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+yXCZCeULa9pUpP73UwjG0dGZDvbkFTDE8KHqVb8JiT-vpEiQ@mail.gmail.com \
    --to=kito.cheng@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=palmer@rivosinc.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).