public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Aldy Hernandez <aldyh@redhat.com>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: Paul Koning <ni1d@arrl.net>,
	Richard Biener <richard.guenther@gmail.com>,
	 Jakub Jelinek <jakub@redhat.com>,
	GCC patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Implement known/maybe fpclassify like API for frange.
Date: Mon, 12 Sep 2022 15:12:46 +0200	[thread overview]
Message-ID: <CAGm3qMW9dJ2jNnNquNnt6YTy4te9uSz5nMXFzbMRCAiQO9SSTw@mail.gmail.com> (raw)
In-Reply-To: <20220912084147.v54scz6dbnlxsijv@lug-owl.de>

On Mon, Sep 12, 2022 at 10:48 AM Jan-Benedict Glaw <jbglaw@lug-owl.de> wrote:
>
> Hi Aldy!
>
> On Thu, 2022-09-08 12:56:24 +0200, Aldy Hernandez via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
>
> > From 795baa0b044953e9f198f49e379374d633f43b47 Mon Sep 17 00:00:00 2001
> > From: Aldy Hernandez <aldyh@redhat.com>
> > Date: Thu, 8 Sep 2022 08:11:43 +0200
> > Subject: [PATCH] Implement known/maybe fpclassify like API for frange.
> >
> > gcc/ChangeLog:
> >
> >       * gimple-range-fold.cc
> >       (fold_using_range::range_of_builtin_int_call): Use fpclassify like API.
> >       * range-op-float.cc (finite_operand_p): Same.
> >       (finite_operands_p): Same.
> >       (foperator_lt::fold_range): Same.
> >       (foperator_le::fold_range): Same.
> >       (foperator_gt::fold_range): Same.
> >       (foperator_ge::fold_range): Same.
> >       (foperator_unordered::fold_range): Same.
> >       (foperator_unordered::op1_range): Same.
> >       (foperator_ordered::fold_range): Same.
> >       * value-range.cc (frange::set_nan): Same.
> >       (frange::set_signbit): Same.
> >       (frange::union_): Same.
> >       (frange::intersect): Same.
> >       (frange::operator==): Same.
> >       (frange::singleton_p): Same.
> >       (frange::verify_range): Same.
> >       (range_tests_nan): Same.
> >       (range_tests_floats): Same.
> >       * value-range.h(frange::known_finite): New.
> >       (frange::maybe_inf): New.
> >       (frange::known_inf): New.
> >       (frange::maybe_nan): New.
> >       (frange::known_nan): New.
> >       (frange::known_signbit): New.
> > ---
> >  gcc/gimple-range-fold.cc |  19 +++---
> >  gcc/range-op-float.cc    |  26 ++++----
> >  gcc/value-range.cc       | 126 +++++++++++++++++++++++----------------
> >  gcc/value-range.h        |  78 +++++++++++++++++++++++-
> >  4 files changed, 170 insertions(+), 79 deletions(-)
>
> This triggers a selftest failure for pdp11:
>
> .../gcc/configure --prefix=... --enable-werror-always --enable-languages=all --disable-gcov --disable-shared --disable-threads --target=pdp11-aout --without-headers

I have just pushed a patch to fix this.

I have also added -ffinite-math-only selftests to my list of testing
requirements for all future frange work.

Thanks for reporting this.
Aldy


  reply	other threads:[~2022-09-12 13:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08  6:27 Aldy Hernandez
2022-09-08  7:27 ` Richard Biener
2022-09-08 10:56   ` Aldy Hernandez
2022-09-12  8:41     ` Jan-Benedict Glaw
2022-09-12 13:12       ` Aldy Hernandez [this message]
2022-09-12 18:38         ` Jan-Benedict Glaw

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=CAGm3qMW9dJ2jNnNquNnt6YTy4te9uSz5nMXFzbMRCAiQO9SSTw@mail.gmail.com \
    --to=aldyh@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=jbglaw@lug-owl.de \
    --cc=ni1d@arrl.net \
    --cc=richard.guenther@gmail.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).