From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 53587 invoked by alias); 12 Nov 2015 11:30:48 -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 53564 invoked by uid 89); 12 Nov 2015 11:30:48 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.2 X-HELO: eu-smtp-delivery-143.mimecast.com Received: from eu-smtp-delivery-143.mimecast.com (HELO eu-smtp-delivery-143.mimecast.com) (146.101.78.143) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 12 Nov 2015 11:30:47 +0000 Received: from cam-owa2.Emea.Arm.com (fw-tnat.cambridge.arm.com [217.140.96.140]) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-29-8OlyvkBeT1OgNr0aoU322A-1; Thu, 12 Nov 2015 11:30:41 +0000 Received: from [10.2.206.40] ([10.1.2.79]) by cam-owa2.Emea.Arm.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 12 Nov 2015 11:30:41 +0000 Message-ID: <56447860.6080702@arm.com> Date: Thu, 12 Nov 2015 11:30:00 -0000 From: Szabolcs Nagy User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.8.0 MIME-Version: 1.0 To: "gcc-patches@gcc.gnu.org" CC: Marcus Shawcroft Subject: [PATCH][AArch64] Documentation fix for -fpic X-MC-Unique: 8OlyvkBeT1OgNr0aoU322A-1 Content-Type: multipart/mixed; boundary="------------070501050302020709020902" X-IsSubscribed: yes X-SW-Source: 2015-11/txt/msg01489.txt.bz2 This is a multi-part message in MIME format. --------------070501050302020709020902 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Content-length: 450 The documentation for -fpic and -fPIC explicitly mentions some targets where the difference matters, but not AArch64. Specifying the GOT size limit is not entirely correct as it can depend on the -mcmodel setting, but probably better than leaving the impression that -fpic vs -fPIC does not matter on AArch64. ChangeLog: 2015-11-12 Szabolcs Nagy * doc/invoke.texi (-fpic): Add the AArch64 limit. (-fPIC): Add AArch64. --------------070501050302020709020902 Content-Type: text/x-patch; name=fpic.diff Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="fpic.diff" Content-length: 1143 diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi index 0121832..f925fe0 100644 --- a/gcc/doc/invoke.texi +++ b/gcc/doc/invoke.texi @@ -23951,7 +23951,7 @@ loader is not part of GCC; it is part of the operat= ing system). If the GOT size for the linked executable exceeds a machine-specific maximum size, you get an error message from the linker indicating that @option{-fpic} does not work; in that case, recompile with @option{-fPIC} -instead. (These maximums are 8k on the SPARC and 32k +instead. (These maximums are 8k on the SPARC, 28k on AArch64 and 32k on the m68k and RS/6000. The x86 has no such limit.) =20 Position-independent code requires special support, and therefore works @@ -23966,7 +23966,7 @@ are defined to 1. @opindex fPIC If supported for the target machine, emit position-independent code, suitable for dynamic linking and avoiding any limit on the size of the -global offset table. This option makes a difference on the m68k, +global offset table. This option makes a difference on the AArch64, m68k, PowerPC and SPARC@. =20 Position-independent code requires special support, and therefore works --------------070501050302020709020902--