From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Richard Biener <rguenther@suse.de>
Cc: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>,
Christophe Lyon <christophe.lyon@linaro.org>,
Jeff Law <law@redhat.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH][RFC] Fix P1 PR77498
Date: Fri, 31 Mar 2017 10:37:00 -0000 [thread overview]
Message-ID: <20170331102225.GA7002@x4> (raw)
In-Reply-To: <alpine.LSU.2.20.1703311116450.30715@zhemvz.fhfr.qr>
On 2017.03.31 at 11:16 +0200, Richard Biener wrote:
> On Fri, 31 Mar 2017, Richard Biener wrote:
>
> > On Fri, 31 Mar 2017, Rainer Orth wrote:
> >
> > > Hi Christophe,
> > >
> > > > With this patch, the following testcase now fails on arm* targets:
> > > > gcc.dg/tree-ssa/pr71347.c scan-tree-dump-not optimized ".* = MEM.*;"
> > >
> > > same on Solaris/SPARC.
> >
> > I've reverted r241968 with (patch reverted). It doesn't include
> > sparc, so please amend as you see fit.
>
> Ah, r241441. I'll fixup myself then.
It also fails on some X86 configurations:
https://gcc.gnu.org/ml/gcc-regression/2017-03/msg00237.html
https://gcc.gnu.org/ml/gcc-regression/2017-03/msg00238.html
--
Markus
next prev parent reply other threads:[~2017-03-31 10:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 10:17 Richard Biener
2017-03-29 16:38 ` Bin.Cheng
2017-03-29 19:28 ` Jeff Law
2017-03-30 8:16 ` Richard Biener
2017-03-31 9:05 ` Christophe Lyon
2017-03-31 9:13 ` Rainer Orth
2017-03-31 9:17 ` Richard Biener
2017-03-31 9:25 ` Richard Biener
2017-03-31 10:37 ` Markus Trippelsdorf [this message]
2017-03-31 11:13 ` Richard Biener
2017-03-31 14:09 ` Bin.Cheng
2017-03-31 14:15 ` Bin.Cheng
2017-03-31 14:35 ` Rainer Orth
2017-04-03 8:45 ` Richard Biener
2017-03-31 9:16 ` Richard Biener
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=20170331102225.GA7002@x4 \
--to=markus@trippelsdorf.de \
--cc=christophe.lyon@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=rguenther@suse.de \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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).