From: Mike Frysinger <vapier@gentoo.org>
To: "Guillermo E. Martinez" <guillermo.e.martinez@oracle.com>
Cc: binutils@sourceware.org, jose.marchesi@oracle.com
Subject: Re: [PATCH] Fix sim/testsuite/bpf due to linker warnings
Date: Wed, 4 Jan 2023 02:02:26 -0500 [thread overview]
Message-ID: <Y7UkgjaeXAlFEWXl@vapier> (raw)
In-Reply-To: <20230104041219.794237-1-guillermo.e.martinez@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 803 bytes --]
On 03 Jan 2023 22:12, Guillermo E. Martinez via Binutils wrote:
> Hello,
>
> This patch is meant to fix bug:
> https://sourceware.org/bugzilla/show_bug.cgi?id=29954
>
> Please let know your thoughts. I'll really appreciate them!,
> guillermo
>
> --
>
> On a bpf-*-* testsuite fails:
> ./ld/ld-new: warning: test has a LOAD segment with RWX permissions
>
> Adding `--no-warn-rwx-segments' option to linker and set `--memory-size=10Mb'
> to the simulator bpf testsuite passes.
>
> Tested on bpf-*-*:
>
> Bug 29954: https://sourceware.org/bugzilla/show_bug.cgi?id=29954
i thought increasing the memory was sufficient to not need the -Ttext=0x0,
and the -Ttext=0x0 was the only reason we were triggering RWX warnings. so
do we still need --no-warn-rwx-segments ?
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-01-04 7:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 4:12 Guillermo E. Martinez
2023-01-04 7:02 ` Mike Frysinger [this message]
2023-01-04 17:24 ` Guillermo E. Martinez
2023-01-04 21:41 ` [PATCHv2] " Guillermo E. Martinez
2023-01-05 1:54 ` Mike Frysinger
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=Y7UkgjaeXAlFEWXl@vapier \
--to=vapier@gentoo.org \
--cc=binutils@sourceware.org \
--cc=guillermo.e.martinez@oracle.com \
--cc=jose.marchesi@oracle.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).