public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: "Martin Liška" <mliska@suse.cz>,
	gcc@gcc.gnu.org, binutils@sourceware.org
Subject: Re: [committed] exec-stack warning for test which wants executable stacks
Date: Tue, 26 Apr 2022 07:54:12 -0600	[thread overview]
Message-ID: <c14e585b-3ac0-c742-2667-c0c4c0bbd57b@gmail.com> (raw)
In-Reply-To: <fd30ffae-e186-f407-c4dd-ec97ecf22db5@gmail.com>



On 4/25/2022 8:37 AM, Jeff Law wrote:
>
>
> On 4/25/2022 6:56 AM, Martin Liška wrote:
>>
>>> I used -z execstack rather than --no-warn-execstack as the former is 
>>> recognized by older versions of ld, but the latter is a new option.
>> Thanks for it.
> Unfortunately, I should have looked at the other failures that have 
> popped up over the last week.  Essentially all the nested function 
> tests are failing on some targets due to the same linker warning.
>
> Either pruning or adding  the option to all those tests is going to be 
> necessary ;(
And -z execstack is not universally accepted either.  In fact, we even 
have some elf targets that don't support it due to oversights (?) in 
their linker configurations.  But the key thing AFAICT is that -z 
execstack is an ELF specific flag (I didn't know that until just now).  
So we can't really depend on it across the board.  In fact, I wouldn't 
be surprised if AIX has regressed on the one file I adjusted earlier.

So I think that means we're stuck with the less desirable option of 
pruning the output.  I'll take care of it and reverting the change that 
added -z execstack to the one test.

jeff

      parent reply	other threads:[~2022-04-26 13:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-24 17:42 Jeff Law
2022-04-25 12:56 ` Martin Liška
2022-04-25 14:37   ` Jeff Law
2022-04-25 14:42     ` Nick Clifton
2022-04-25 14:59       ` Jeff Law
2022-04-25 15:26         ` Nick Clifton
2022-04-25 15:30           ` Jeff Law
2022-05-26  1:17             ` Hans-Peter Nilsson
2022-05-26 23:17               ` Hans-Peter Nilsson
2022-04-26 13:54     ` Jeff Law [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=c14e585b-3ac0-c742-2667-c0c4c0bbd57b@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=gcc@gcc.gnu.org \
    --cc=mliska@suse.cz \
    /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).