From: WANG Xuerui <i.swmail@xen0n.name>
To: Huang Pei <huangpei@loongson.cn>,
Zhensong Liu <liuzhensong@loongson.cn>,
binutils <binutils@sourceware.org>,
Chenghua Xu <xuchenghua@loongson.cn>
Subject: Re: [PATCH 2/2] partial revert 5a91f93b983184c64b3a9332f5f4339d17941d76
Date: Fri, 13 May 2022 09:55:23 +0800 [thread overview]
Message-ID: <d2da9e95-4955-0f0e-ea44-58589daf02f6@xen0n.name> (raw)
In-Reply-To: <20220513013523.85151-2-huangpei@loongson.cn>
Hi,
On 5/13/22 09:35, Huang Pei wrote:
> set elf_backend_default_execstack=0 on loongarch
Please provide reasons for the change; while I and other people familiar
with those lower-level details can somehow guess it's because
contemporary architectures really prefer non-executable stacks by
default, for enhancing security, it's better to be explicit.
Plus, please format the subject lines of both your patches, so they
conform to the repo's conventions. I think they should look like
"LoongArch: Do foo" or "bfd: LoongArch: Do foo", looking at a few recent
commits on various components.
> ---
> bfd/elfnn-loongarch.c | 1 +
> ld/testsuite/ld-elf/elf.exp | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/bfd/elfnn-loongarch.c b/bfd/elfnn-loongarch.c
> index e4cd9fa107e..94c8e8269d3 100644
> --- a/bfd/elfnn-loongarch.c
> +++ b/bfd/elfnn-loongarch.c
> @@ -130,6 +130,7 @@ struct loongarch_elf_link_hash_table
> #define elf_backend_got_header_size (GOT_ENTRY_SIZE * 1)
>
> #define elf_backend_want_dynrelro 1
> +#define elf_backend_default_execstack 0
>
> /* Generate a PLT header. */
>
> diff --git a/ld/testsuite/ld-elf/elf.exp b/ld/testsuite/ld-elf/elf.exp
> index ebb5ba090bf..e33a0d08831 100644
> --- a/ld/testsuite/ld-elf/elf.exp
> +++ b/ld/testsuite/ld-elf/elf.exp
> @@ -186,6 +186,7 @@ proc target_defaults_to_execstack {} {
> || [istarget "*-*-nacl"]
> || [istarget "arc*-*-*"]
> || [istarget "ia64*-*-*"]
> + || [istarget "loongarch*-*-*"]
> || [istarget "nios2*-*-*"]
> || [istarget "powerpc64*-*-*"]
> || [istarget "riscv*-*-*"]
next prev parent reply other threads:[~2022-05-13 1:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 1:35 [PATCH 1/2] remove R_LARCH_{SUB,ADD}24, since LA does not need them Huang Pei
2022-05-13 1:35 ` [PATCH 2/2] partial revert 5a91f93b983184c64b3a9332f5f4339d17941d76 Huang Pei
2022-05-13 1:55 ` WANG Xuerui [this message]
2022-05-13 8:58 ` Huang Pei
2022-05-13 1:50 ` [PATCH 1/2] remove R_LARCH_{SUB,ADD}24, since LA does not need them WANG Xuerui
-- strict thread matches above, loose matches on Subject: below --
2022-05-12 12:56 Huang Pei
2022-05-12 12:56 ` [PATCH 2/2] partial revert 5a91f93b983184c64b3a9332f5f4339d17941d76 Huang Pei
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=d2da9e95-4955-0f0e-ea44-58589daf02f6@xen0n.name \
--to=i.swmail@xen0n.name \
--cc=binutils@sourceware.org \
--cc=huangpei@loongson.cn \
--cc=liuzhensong@loongson.cn \
--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).