public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-2728] LoongArch: Prepare static PIE support
Date: Tue, 20 Sep 2022 06:00:09 +0000 (GMT)	[thread overview]
Message-ID: <20220920060009.953703858D28@sourceware.org> (raw)

https://gcc.gnu.org/g:90d3e27f3a6add0cd6892bdf07c6a2538bb709e4

commit r13-2728-g90d3e27f3a6add0cd6892bdf07c6a2538bb709e4
Author: Xi Ruoyao <xry111@xry111.site>
Date:   Tue Sep 13 23:21:39 2022 +0800

    LoongArch: Prepare static PIE support
    
    Static PIE allows us to extend the ASLR to cover static executables and
    it's not too difficult to support it.  On GCC side, we just pass a group
    of options to the linker, like other ports with static PIE support.
    
    The real implementation of static PIE (rcrt1.o) will be added into Glibc
    later.
    
    gcc/ChangeLog:
    
            * config/loongarch/gnu-user.h (GNU_USER_TARGET_LINK_SPEC): For
            -static-pie, pass -static -pie --no-dynamic-linker -z text to
            the linker, and do not pass --dynamic-linker.

Diff:
---
 gcc/config/loongarch/gnu-user.h | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/gcc/config/loongarch/gnu-user.h b/gcc/config/loongarch/gnu-user.h
index 664dc9206ad..c5b1afe530d 100644
--- a/gcc/config/loongarch/gnu-user.h
+++ b/gcc/config/loongarch/gnu-user.h
@@ -40,8 +40,10 @@ along with GCC; see the file COPYING3.  If not see
 #undef GNU_USER_TARGET_LINK_SPEC
 #define GNU_USER_TARGET_LINK_SPEC \
   "%{G*} %{shared} -m " GNU_USER_LINK_EMULATION \
-  "%{!shared: %{static} %{!static: %{rdynamic:-export-dynamic} " \
-  "-dynamic-linker " GNU_USER_DYNAMIC_LINKER "}}"
+  "%{!shared: %{static} " \
+  "%{!static: %{!static-pie: %{rdynamic:-export-dynamic} " \
+  "-dynamic-linker " GNU_USER_DYNAMIC_LINKER "}} " \
+  "%{static-pie: -static -pie --no-dynamic-linker -z text}}"
 
 
 /* Similar to standard Linux, but adding -ffast-math support.  */

                 reply	other threads:[~2022-09-20  6:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-all 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=20220920060009.953703858D28@sourceware.org \
    --to=xry111@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).