From: Eric Botcazou <ebotcazou@adacore.com>
To: Richard Biener <rguenther@suse.de>
Cc: gcc-patches@gcc.gnu.org, Alan Modra <amodra@gmail.com>,
Tamar Christina <tamar.christina@arm.com>,
nd@arm.com, law@redhat.com, ian@airs.com, bergner@vnet.ibm.com
Subject: Re: [PATCH][GCC][mid-end] Fix PR85123 incorrect copies
Date: Fri, 06 Apr 2018 11:25:00 -0000 [thread overview]
Message-ID: <2239339.DFribSM1H9@polaris> (raw)
In-Reply-To: <alpine.LSU.2.20.1804061223170.18265@zhemvz.fhfr.qr>
> I wonder if it's best to revert the original regression causing patch
> and look for a proper solution in the GCC 9 timeframe?
Probably the best course of action indeed, as changes in this area need to be
thoroughly tested on various targets to cover all the cases.
--
Eric Botcazou
next prev parent reply other threads:[~2018-04-06 11:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 12:29 Tamar Christina
2018-04-05 23:46 ` Alan Modra
2018-04-06 10:24 ` Richard Biener
2018-04-06 11:25 ` Eric Botcazou [this message]
2018-04-06 11:35 ` Richard Biener
2018-04-06 12:55 ` Tamar Christina
2018-04-06 13:18 ` Tamar Christina
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=2239339.DFribSM1H9@polaris \
--to=ebotcazou@adacore.com \
--cc=amodra@gmail.com \
--cc=bergner@vnet.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ian@airs.com \
--cc=law@redhat.com \
--cc=nd@arm.com \
--cc=rguenther@suse.de \
--cc=tamar.christina@arm.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).