From: Jeff Law <jeffreyalaw@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>,
"Joseph S. Myers" <joseph@codesourcery.com>,
Richard Biener <rguenther@suse.de>
Cc: gcc-patches@gcc.gnu.org, Jonathan Wakely <jwakely@redhat.com>
Subject: Re: [PATCH] builtins: Add various complex builtins for _Float{16,32,64,128,32x,64x,128x}
Date: Mon, 24 Oct 2022 10:28:34 -0600 [thread overview]
Message-ID: <52520523-e623-3367-99a7-b07a64f76866@gmail.com> (raw)
In-Reply-To: <Y1K9+NDQQlJp87YK@tucnak>
On 10/21/22 09:42, Jakub Jelinek wrote:
> Hi!
>
> On top of the pending
> https://gcc.gnu.org/pipermail/gcc-patches/2022-October/603665.html
> https://gcc.gnu.org/pipermail/gcc-patches/2022-October/604080.html
> the following patch adds some complex builtins which have libm
> implementation in glibc 2.26 and later on various arches.
> It is needed for libstdc++ _Float128 support when long double is not
> IEEE quad.
>
> Tested on x86_64-linux, ok for trunk?
>
> 2022-10-21 Jakub Jelinek <jakub@redhat.com>
>
> * builtin-types.def (BT_COMPLEX_FLOAT16, BT_COMPLEX_FLOAT32,
> BT_COMPLEX_FLOAT64, BT_COMPLEX_FLOAT128, BT_COMPLEX_FLOAT32X,
> BT_COMPLEX_FLOAT64X, BT_COMPLEX_FLOAT128X,
> BT_FN_COMPLEX_FLOAT16_COMPLEX_FLOAT16,
> BT_FN_COMPLEX_FLOAT32_COMPLEX_FLOAT32,
> BT_FN_COMPLEX_FLOAT64_COMPLEX_FLOAT64,
> BT_FN_COMPLEX_FLOAT128_COMPLEX_FLOAT128,
> BT_FN_COMPLEX_FLOAT32X_COMPLEX_FLOAT32X,
> BT_FN_COMPLEX_FLOAT64X_COMPLEX_FLOAT64X,
> BT_FN_COMPLEX_FLOAT128X_COMPLEX_FLOAT128X,
> BT_FN_FLOAT16_COMPLEX_FLOAT16, BT_FN_FLOAT32_COMPLEX_FLOAT32,
> BT_FN_FLOAT64_COMPLEX_FLOAT64, BT_FN_FLOAT128_COMPLEX_FLOAT128,
> BT_FN_FLOAT32X_COMPLEX_FLOAT32X, BT_FN_FLOAT64X_COMPLEX_FLOAT64X,
> BT_FN_FLOAT128X_COMPLEX_FLOAT128X,
> BT_FN_COMPLEX_FLOAT16_COMPLEX_FLOAT16_COMPLEX_FLOAT16,
> BT_FN_COMPLEX_FLOAT32_COMPLEX_FLOAT32_COMPLEX_FLOAT32,
> BT_FN_COMPLEX_FLOAT64_COMPLEX_FLOAT64_COMPLEX_FLOAT64,
> BT_FN_COMPLEX_FLOAT128_COMPLEX_FLOAT128_COMPLEX_FLOAT128,
> BT_FN_COMPLEX_FLOAT32X_COMPLEX_FLOAT32X_COMPLEX_FLOAT32X,
> BT_FN_COMPLEX_FLOAT64X_COMPLEX_FLOAT64X_COMPLEX_FLOAT64X,
> BT_FN_COMPLEX_FLOAT128X_COMPLEX_FLOAT128X_COMPLEX_FLOAT128X): New.
> * builtins.def (CABS_TYPE, CACOSH_TYPE, CARG_TYPE, CASINH_TYPE,
> CPOW_TYPE, CPROJ_TYPE): Define and undefine later.
> (BUILT_IN_CABS, BUILT_IN_CACOSH, BUILT_IN_CACOS, BUILT_IN_CARG,
> BUILT_IN_CASINH, BUILT_IN_CASIN, BUILT_IN_CATANH, BUILT_IN_CATAN,
> BUILT_IN_CCOSH, BUILT_IN_CCOS, BUILT_IN_CEXP, BUILT_IN_CLOG,
> BUILT_IN_CPOW, BUILT_IN_CPROJ, BUILT_IN_CSINH, BUILT_IN_CSIN,
> BUILT_IN_CSQRT, BUILT_IN_CTANH, BUILT_IN_CTAN): Add
> DEF_EXT_LIB_FLOATN_NX_BUILTINS.
> * fold-const-call.cc (fold_const_call_sc, fold_const_call_cc,
> fold_const_call_ccc): Add various CASE_CFN_*_FN: cases when
> CASE_CFN_* is present.
> * gimple-ssa-backprop.cc (backprop::process_builtin_call_use):
> Likewise.
> * builtins.cc (expand_builtin, fold_builtin_1): Likewise.
> * fold-const.cc (negate_mathfn_p, tree_expr_finite_p,
> tree_expr_maybe_signaling_nan_p, tree_expr_maybe_nan_p,
> tree_expr_maybe_real_minus_zero_p, tree_call_nonnegative_warnv_p):
> Likewise.
OK
jeff
next prev parent reply other threads:[~2022-10-24 16:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 7:23 [PATCH] builtins: Add __builtin_nextafterf16b builtin Jakub Jelinek
2022-10-21 15:42 ` [PATCH] builtins: Add various complex builtins for _Float{16,32,64,128,32x,64x,128x} Jakub Jelinek
2022-10-24 16:28 ` Jeff Law [this message]
2022-10-25 9:03 ` Patch ping Jakub Jelinek
2022-10-24 15:24 ` [PATCH] builtins: Add __builtin_nextafterf16b builtin Jeff Law
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=52520523-e623-3367-99a7-b07a64f76866@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=jwakely@redhat.com \
--cc=rguenther@suse.de \
/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).