From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 94428 invoked by alias); 6 Apr 2018 11:25:24 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 94352 invoked by uid 89); 6 Apr 2018 11:25:13 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=HContent-Transfer-Encoding:7Bit X-HELO: smtp.eu.adacore.com Received: from mel.act-europe.fr (HELO smtp.eu.adacore.com) (194.98.77.210) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 06 Apr 2018 11:25:11 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-smtp.eu.adacore.com (Postfix) with ESMTP id AC840812E5; Fri, 6 Apr 2018 13:25:05 +0200 (CEST) Received: from smtp.eu.adacore.com ([127.0.0.1]) by localhost (smtp.eu.adacore.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w_1w5xm-jLD0; Fri, 6 Apr 2018 13:25:05 +0200 (CEST) Received: from polaris.localnet (bon31-6-88-161-99-133.fbx.proxad.net [88.161.99.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.eu.adacore.com (Postfix) with ESMTPSA id D1A6281345; Fri, 6 Apr 2018 13:25:04 +0200 (CEST) From: Eric Botcazou To: Richard Biener Cc: gcc-patches@gcc.gnu.org, Alan Modra , Tamar Christina , 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 Message-ID: <2239339.DFribSM1H9@polaris> In-Reply-To: References: <20180405122903.GA509@arm.com> <20180405234558.GS3812@bubble.grove.modra.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-SW-Source: 2018-04/txt/msg00308.txt.bz2 > 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