public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gao, Liming" <liming.gao@intel.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	"Shi, Steven" <steven.shi@intel.com>,
	"Zhu, Yonghong" <yonghong.zhu@intel.com>,
	"Justen, Jordan L" <jordan.l.justen@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [PATCH] MdePkg: move to 'hidden' visibility for all symbols under GCC/X64
Date: Tue, 2 Aug 2016 02:49:40 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A1155E3E3A@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1470034640-3912-1-git-send-email-ard.biesheuvel@linaro.org>

Reviewed-by: Liming Gao <liming.gao@intel.com>

> -----Original Message-----
> From: Ard Biesheuvel [mailto:ard.biesheuvel@linaro.org]
> Sent: Monday, August 01, 2016 2:57 PM
> To: Shi, Steven <steven.shi@intel.com>; Zhu, Yonghong
> <yonghong.zhu@intel.com>; Gao, Liming <liming.gao@intel.com>; Justen,
> Jordan L <jordan.l.justen@intel.com>; edk2-devel@lists.01.org
> Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> Subject: [PATCH] MdePkg: move to 'hidden' visibility for all symbols under
> GCC/X64
> 
> When using GCC to build for X64, we switched to the position independent
> small code model, which is much more efficient in terms of code generation
> and runtime relocation footprint, and produces binaries that can execute
> correctly from any offset.
> 
> However, the PIC routines are by default geared towards hosted binaries
> containing symbol references that may resolve to definitions in other
> dynamic objects, and for this reason, external symbol references are
> indirected via a GOT entry by default (which also results in a .reloc fixup
> entry) unless we annotate them.
> 
> For this reason, we introduced the 'protected' visibility annotation for
> all symbol definitions and references, by setting the GCC visibility
> pragma. However, as it turns out, this is not sufficient for all versions
> of GCC, and in some cases (GCC 5.x using the GCC49 toolchain tag), may
> still result in GOT based relocations.
> 
> So switch to 'hidden' visibility instead, which is slightly stronger, and
> fixes this issue for the versions of GCC that exhibit the problem.
> 
> Contributed-under: TianoCore Contribution Agreement 1.0
> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> ---
>  MdePkg/Include/X64/ProcessorBind.h | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/MdePkg/Include/X64/ProcessorBind.h
> b/MdePkg/Include/X64/ProcessorBind.h
> index a4aad3e524e8..666cc8e8bd16 100644
> --- a/MdePkg/Include/X64/ProcessorBind.h
> +++ b/MdePkg/Include/X64/ProcessorBind.h
> @@ -29,12 +29,12 @@
> 
>  #if defined(__GNUC__) && defined(__pic__)
>  //
> -// Mark all symbol declarations and references as protected, meaning they
> will
> +// Mark all symbol declarations and references as hidden, meaning they will
>  // not be subject to symbol preemption. This allows the compiler to refer to
>  // symbols directly using relative references rather than via the GOT, which
>  // contains absolute symbol addresses that are subject to runtime relocation.
>  //
> -#pragma GCC visibility push (protected)
> +#pragma GCC visibility push (hidden)
>  #endif
> 
>  #if defined(__INTEL_COMPILER)
> --
> 2.7.4



  reply	other threads:[~2016-08-02  2:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-01  6:57 [PATCH] MdePkg: move to 'hidden' visibility for all symbols under GCC/X64 Ard Biesheuvel
2016-08-02  2:49 ` Gao, Liming [this message]
2016-08-02  6:21   ` Ard Biesheuvel

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-list 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=4A89E2EF3DFEDB4C8BFDE51014F606A1155E3E3A@shsmsx102.ccr.corp.intel.com \
    --to=devel@edk2.groups.io \
    /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