public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jeff Law <law@redhat.com>
Cc: gcc-patches@gcc.gnu.org, jakub@redhat.com
Subject: Re: [PATCH] combine: Fix PR80233
Date: Wed, 29 Mar 2017 20:56:00 -0000	[thread overview]
Message-ID: <20170329204919.GY4402@gate.crashing.org> (raw)
In-Reply-To: <a8f32295-e5dd-3706-590e-873292092911@redhat.com>

On Wed, Mar 29, 2017 at 02:35:32PM -0600, Jeff Law wrote:
> ps.  Never in a million years would I have expected isolation of 
> division by zero to have exposed as many latent issues as it has.  Sigh.

The trap insns weren't handled very well before, but we didn't generate
many either.  They still aren't handled very well, but hopefully we don't
ICE so much on them anymore ;-)


Segher

      parent reply	other threads:[~2017-03-29 20:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-29 18:47 Segher Boessenkool
2017-03-29 20:44 ` Jeff Law
2017-03-29 20:48   ` Jakub Jelinek
2017-03-29 20:49     ` Jeff Law
2017-03-29 20:56   ` Segher Boessenkool [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=20170329204919.GY4402@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=law@redhat.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).