From: FX <fxcoudert@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc@gcc.gnu.org, "Joseph S. Myers" <joseph@codesourcery.com>,
FX via Fortran <fortran@gcc.gnu.org>
Subject: Re: Floating-point comparisons in the middle-end
Date: Thu, 1 Sep 2022 11:04:03 +0200 [thread overview]
Message-ID: <3BD50DD7-5C9E-42CB-992C-A66584411A4F@gmail.com> (raw)
In-Reply-To: <YxBrLzoOag91YQ27@tucnak>
Hi Jakub,
>> 2. All the functions are available as GCC type-generic built-ins (yeah!),
>> except there is no __builtin_ iseqsig
>> (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77928). Is there a
>> fundamental problem with creating one, and could someone help there?
>
> IMHO until that one is implemented you can just use
> tx = x, ty = y, tx>=ty && tx<=ty
> (in GENERIC just SAVE_EXPR<x> >= SAVE_EXPR<y> && SAVE_EXPR<x> <= SAVE_EXPR<y>
If it’s just that (optimization aside), I probably can create a C built-in. It would need to be:
1. defined in builtins.def
2. lowered in builtins.cc
3. type-checked in c-family/c-common.cc
4. documented in doc/extend.texi
5. tested in fp-test.cc
6. covered in the testsuite
Is that right?
Thanks,
FX
PS: I see that reclassify is not covered in fp-test.cc, is that file obsolete?
next prev parent reply other threads:[~2022-09-01 9:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 8:04 FX
2022-09-01 8:19 ` Jakub Jelinek
2022-09-01 9:04 ` FX [this message]
2022-09-01 9:23 ` Jakub Jelinek
2022-09-01 10:06 ` FX
2022-09-01 15:21 ` Joseph Myers
2022-09-01 15:57 ` Marc Glisse
2022-09-01 16:22 ` Joseph Myers
2022-09-01 16:24 ` FX
2022-09-01 16:44 ` Joseph Myers
2022-09-01 18:15 ` FX
2022-09-01 14:32 ` Segher Boessenkool
2022-09-01 15:19 ` Joseph Myers
2022-09-01 18:38 ` FX
2022-09-01 19:13 ` Joseph Myers
2022-09-01 18:47 ` FX
2022-09-01 19:16 ` Joseph Myers
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=3BD50DD7-5C9E-42CB-992C-A66584411A4F@gmail.com \
--to=fxcoudert@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.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).