From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 81272 invoked by alias); 28 Nov 2015 16:29:03 -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 81254 invoked by uid 89); 28 Nov 2015 16:29:02 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: relay1.mentorg.com Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 28 Nov 2015 16:29:01 +0000 Received: from nat-ies.mentorg.com ([192.94.31.2] helo=SVR-IES-FEM-01.mgc.mentorg.com) by relay1.mentorg.com with esmtp id 1a2iMr-0003q9-DU from Tom_deVries@mentor.com ; Sat, 28 Nov 2015 08:28:57 -0800 Received: from [127.0.0.1] (137.202.0.76) by SVR-IES-FEM-01.mgc.mentorg.com (137.202.0.104) with Microsoft SMTP Server id 14.3.224.2; Sat, 28 Nov 2015 16:28:55 +0000 Subject: Re: [RFC] Getting LTO incremental linking work To: Ilya Verbin References: <20151125085912.GD58491@kam.mff.cuni.cz> <20151125191740.GB5371@kam.mff.cuni.cz> <20151125230758.GF20593@kam.mff.cuni.cz> <5659757A.2080700@mentor.com> <56598994.2010703@mentor.com> CC: Jan Hubicka , "H.J. Lu" , Richard Biener , GCC Patches , Andi Kleen , Cary Coutant , Ian Lance Taylor , Kirill Yukhin From: Tom de Vries Message-ID: <5659D60E.3080406@mentor.com> Date: Sat, 28 Nov 2015 17:41:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/mixed; boundary="------------040109070906020600050402" X-SW-Source: 2015-11/txt/msg03415.txt.bz2 --------------040109070906020600050402 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Content-length: 405 On 28/11/15 13:02, Ilya Verbin wrote: > 2015-11-28 14:01 GMT+03:00 Tom de Vries : >> This patch fixes the failures. I'm not sure if this is the right or complete >> fix though. > > I think it's ok, at least until we decide how to rework the offloading > stuff in lto-wrapper (see PR68463). > Bootstrapped and reg-tested on x86_64. Committed to trunk as attached. Thanks, - Tom --------------040109070906020600050402 Content-Type: text/x-patch; name="0001-Handle-flinker-output-in-lto-wrapper.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="0001-Handle-flinker-output-in-lto-wrapper.patch" Content-length: 806 Handle flinker-output in lto-wrapper 2015-11-28 Tom de Vries * lto-wrapper.c (run_gcc): Handle -flinker-output argument. --- gcc/lto-wrapper.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/gcc/lto-wrapper.c b/gcc/lto-wrapper.c index b9ac535..e4772d1 100644 --- a/gcc/lto-wrapper.c +++ b/gcc/lto-wrapper.c @@ -1096,7 +1096,10 @@ run_gcc (unsigned argc, char *argv[]) if (have_offload && !have_lto) { for (i = 1; i < argc; ++i) - if (strncmp (argv[i], "-fresolution=", sizeof ("-fresolution=") - 1)) + if (strncmp (argv[i], "-fresolution=", + sizeof ("-fresolution=") - 1) != 0 + && strncmp (argv[i], "-flinker-output=", + sizeof ("-flinker-output=") - 1) != 0) { char *out_file; /* Can be ".o" or ".so". */ --------------040109070906020600050402--