public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Aldy Hernandez <aldyh@redhat.com>
Cc: Andrew MacLeod <amacleod@redhat.com>,
	GCC patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] range-ops: Handle undefined ranges in frange op[12]_range [PR108647]
Date: Fri, 3 Feb 2023 19:28:42 +0100	[thread overview]
Message-ID: <Y91SWTVfwPwYt5Cr@tucnak> (raw)
In-Reply-To: <20230203180918.6417-1-aldyh@redhat.com>

On Fri, Feb 03, 2023 at 07:09:18PM +0100, Aldy Hernandez wrote:
> This patch gracefully handles undefined operand ranges for the floating
> point op[12]_range operators.  This is very low risk, as we would have
> ICEd otherwise.
> 
> We don't have a testcase that ICEs for floating point ranges, but it's
> only a matter of time.  Besides, this dovetails nicely with the integer
> versions Jakub is testing.

LGTM (even bootstrapped/regtested this successfully on i686-linux).

	Jakub


      reply	other threads:[~2023-02-03 20:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-03 18:09 Aldy Hernandez
2023-02-03 18:28 ` Jakub Jelinek [this message]

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=Y91SWTVfwPwYt5Cr@tucnak \
    --to=jakub@redhat.com \
    --cc=aldyh@redhat.com \
    --cc=amacleod@redhat.com \
    --cc=gcc-patches@gcc.gnu.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).