From: Joseph Myers <joseph@codesourcery.com>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: Zong Li <zong@andestech.com>, <libc-alpha@sourceware.org>,
<zongbox@gmail.com>, arcml <linux-snps-arc@lists.infradead.org>
Subject: Re: [PATCH] Fix the ld flags not be applied to tst-execstack-mod.so
Date: Wed, 25 Jul 2018 20:22:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1807252021030.4746@digraph.polyomino.org.uk> (raw)
In-Reply-To: <469dcf75-d652-62ee-8310-ea59ec878a0a@synopsys.com>
On Wed, 25 Jul 2018, Vineet Gupta wrote:
> Chiming in as I'm looking into these things myself in context of testing
> for ARC port submission. Do we really need to fix this part - in this
> way. I'd vote to not force the execstack through linker and rely on gcc
> generating this itself when it knows it doing something for trampolines.
> And only if target gcc doesn't support it (detected via configure test)
> should this be done.
The whole point of this test is to verify executable stack changes on
dlopen of a module requiring an executable stack. Thus, for this test to
work correctly, this module must be forced to have a marking as needing an
executable stack.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-07-25 20:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 10:15 Zong Li
2018-07-25 18:54 ` Vineet Gupta
2018-07-25 20:22 ` Joseph Myers [this message]
2018-07-25 20:54 ` Vineet Gupta
2018-07-25 20:56 ` Joseph Myers
2018-07-26 1:19 ` Zong Li
2018-07-26 15:01 ` Joseph Myers
2018-10-15 12:43 ` Zong Li
2018-10-15 13:53 ` Joseph Myers
2018-10-15 17:01 ` Zong Li
2018-10-24 11:01 ` Florian Weimer
2018-10-24 15:59 ` Zong Li
2018-10-25 12:22 ` Florian Weimer
-- strict thread matches above, loose matches on Subject: below --
2018-07-12 8:19 Zong Li
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=alpine.DEB.2.20.1807252021030.4746@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=zong@andestech.com \
--cc=zongbox@gmail.com \
/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).