public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Yinyu Cai <caiyinyu@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] LoongArch: Use __builtin_{fmax, fmaxf, fmin, fminf} with GCC >= 13
Date: Tue, 30 Aug 2022 06:12:13 +0000 (GMT)	[thread overview]
Message-ID: <20220830061213.3D90238425B3@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=241603123c2a1beb7e599bd012c542479e216473

commit 241603123c2a1beb7e599bd012c542479e216473
Author: Xi Ruoyao <xry111@xry111.site>
Date:   Sat Aug 20 16:43:44 2022 +0800

    LoongArch: Use __builtin_{fmax,fmaxf,fmin,fminf} with GCC >= 13
    
    GCC 13 compiles these built-ins to {fmax,fmin}.{s/d} instruction, use
    them instead of the generic implementation.
    
    Link: https://gcc.gnu.org/r13-2085
    Signed-off-by: Xi Ruoyao <xry111@xry111.site>

Diff:
---
 sysdeps/loongarch/fpu/math-use-builtins-fmax.h | 10 ++++++++++
 sysdeps/loongarch/fpu/math-use-builtins-fmin.h | 10 ++++++++++
 2 files changed, 20 insertions(+)

diff --git a/sysdeps/loongarch/fpu/math-use-builtins-fmax.h b/sysdeps/loongarch/fpu/math-use-builtins-fmax.h
new file mode 100644
index 0000000000..5d22567bd3
--- /dev/null
+++ b/sysdeps/loongarch/fpu/math-use-builtins-fmax.h
@@ -0,0 +1,10 @@
+#if __GNUC_PREREQ (13, 0)
+# define USE_FMAX_BUILTIN 1
+# define USE_FMAXF_BUILTIN 1
+#else
+# define USE_FMAX_BUILTIN 0
+# define USE_FMAXF_BUILTIN 0
+#endif
+
+#define USE_FMAXL_BUILTIN 0
+#define USE_FMAXF128_BUILTIN 0
diff --git a/sysdeps/loongarch/fpu/math-use-builtins-fmin.h b/sysdeps/loongarch/fpu/math-use-builtins-fmin.h
new file mode 100644
index 0000000000..4d28b41c0d
--- /dev/null
+++ b/sysdeps/loongarch/fpu/math-use-builtins-fmin.h
@@ -0,0 +1,10 @@
+#if __GNUC_PREREQ (13, 0)
+# define USE_FMIN_BUILTIN 1
+# define USE_FMINF_BUILTIN 1
+#else
+# define USE_FMIN_BUILTIN 0
+# define USE_FMINF_BUILTIN 0
+#endif
+
+#define USE_FMINL_BUILTIN 0
+#define USE_FMINF128_BUILTIN 0

                 reply	other threads:[~2022-08-30  6:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220830061213.3D90238425B3@sourceware.org \
    --to=caiyinyu@sourceware.org \
    --cc=glibc-cvs@sourceware.org \
    /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).