public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Lulu Cheng <chenglulu@loongson.cn>
To: Xi Ruoyao <xry111@xry111.site>, gcc-patches@gcc.gnu.org
Cc: Wang Xuerui <i@xen0n.name>, Chenghua Xu <xuchenghua@loongson.cn>,
	liuzhensong <liuzhensong@loongson.cn>
Subject: Re: [PATCH] LoongArch: Prepare static PIE support
Date: Thu, 15 Sep 2022 11:44:29 +0800	[thread overview]
Message-ID: <fd8d0b9b-53d0-6476-b051-e9676e51ab34@loongson.cn> (raw)
In-Reply-To: <20220913153237.305471-1-xry111@xry111.site>

LGTM!

Thanks.

在 2022/9/13 下午11:32, Xi Ruoyao 写道:
> 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.
> ---
>   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-15  3:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-13 15:32 Xi Ruoyao
2022-09-15  3:44 ` Lulu Cheng [this message]

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=fd8d0b9b-53d0-6476-b051-e9676e51ab34@loongson.cn \
    --to=chenglulu@loongson.cn \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=i@xen0n.name \
    --cc=liuzhensong@loongson.cn \
    --cc=xry111@xry111.site \
    --cc=xuchenghua@loongson.cn \
    /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).