From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13417 invoked by alias); 27 Oct 2015 14:50:21 -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 13388 invoked by uid 89); 27 Oct 2015 14:50:20 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.5 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-ob0-f180.google.com Received: from mail-ob0-f180.google.com (HELO mail-ob0-f180.google.com) (209.85.214.180) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Tue, 27 Oct 2015 14:50:19 +0000 Received: by obbza9 with SMTP id za9so54535652obb.1 for ; Tue, 27 Oct 2015 07:50:17 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.182.60.37 with SMTP id e5mr28338683obr.22.1445957417336; Tue, 27 Oct 2015 07:50:17 -0700 (PDT) Received: by 10.76.72.3 with HTTP; Tue, 27 Oct 2015 07:50:17 -0700 (PDT) In-Reply-To: <562F8B6F.7060605@foss.arm.com> References: <562F5E11.1090503@redhat.com> <562F739F.2090000@foss.arm.com> <562F818A.90003@foss.arm.com> <562F8B6F.7060605@foss.arm.com> Date: Tue, 27 Oct 2015 15:20:00 -0000 Message-ID: Subject: Re: PING: [PATCH] PR target/67215: -fno-plt needs improvements for x86 From: "H.J. Lu" To: Ramana Radhakrishnan Cc: Jiong Wang , Bernd Schmidt , GCC Patches Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2015-10/txt/msg02914.txt.bz2 On Tue, Oct 27, 2015 at 7:34 AM, Ramana Radhakrishnan wrote: > >> >> OK, then it's fairly x86-64 specific optimization, because we can't do "= call *mem" in >> aarch64 and some other targets. > > It is a fairly x86_64 specific optimization and doesn't apply to AArch64. > > The question really is what impact does removing the generic code handlin= g have on aarch64 - is it a no-op or not for the existing -fno-plt implemen= tation in the AArch64 backend ? The only case that is of interest is the bi= t below in calls.c and it looks like that may well be redundant with the lo= gic in the backend already, but I have not done the full analysis to convin= ce myself that the code in the backend is sufficient. > > - && (!flag_plt > - || lookup_attribute ("noplt", DECL_ATTRIBUTES (fndecl_or_t= ype))) > - && !targetm.binds_local_p (fndecl_or_type)) > -fno-plt is a backend specific optimization and should be handled in backend. --=20 H.J.