public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bill Schmidt <wschmidt@linux.vnet.ibm.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Richard Biener <richard.guenther@gmail.com>,
	       GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix PR71815 (SLSR misses PHI opportunities)
Date: Mon, 26 Jun 2017 20:59:00 -0000	[thread overview]
Message-ID: <5B27D9D9-E9D8-4ABB-875F-891CB2B4B3E2@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAMe9rOr4u6+=OgWK1TEs+sBN9dNC8gT=WCTE0=47GXCVdsUy3A@mail.gmail.com>


> On Jun 26, 2017, at 2:22 PM, H.J. Lu <hjl.tools@gmail.com> wrote:
> 
> This may have caused:
> 
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81216
> 
> -- 
> H.J.
> 

Nope.  Reverting my patch does not solve the problem, which appears to begin with r249643.

Bill

      reply	other threads:[~2017-06-26 20:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-16 16:10 Bill Schmidt
2017-06-20 11:23 ` Richard Biener
2017-06-20 14:06   ` Bill Schmidt
2017-06-23 16:06   ` Bill Schmidt
2017-06-26 10:04     ` Richard Biener
2017-06-26 19:22     ` H.J. Lu
2017-06-26 20:59       ` Bill Schmidt [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=5B27D9D9-E9D8-4ABB-875F-891CB2B4B3E2@linux.vnet.ibm.com \
    --to=wschmidt@linux.vnet.ibm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --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).