public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vapier at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug sim/29957] New: or1k custom linker script used in testsuite always triggers LOAD segment with RWX permissions warning
Date: Tue, 03 Jan 2023 06:09:48 +0000 [thread overview]
Message-ID: <bug-29957-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29957
Bug ID: 29957
Summary: or1k custom linker script used in testsuite always
triggers LOAD segment with RWX permissions warning
Product: gdb
Version: unknown
Status: NEW
Severity: normal
Priority: P2
Component: sim
Assignee: unassigned at sourceware dot org
Reporter: vapier at gentoo dot org
CC: nickc at redhat dot com, shorne at gmail dot com, vapier at gentoo dot org
Target Milestone: ---
Target: or1k-elf
using the or1k-elf target, sim testsuite fails now due to linker warnings ever
since this change:
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=ba951afb99912da01a6e8434126b8fac7aa75107
Author: Nick Clifton <nickc@redhat.com>
Date: Tue May 3 11:42:24 2022 +0100
Add a linker warning when creating potentially dangerous executable segments.
Add tests, options to disabke and configure switches to choose defaults.
to reproduce:
$ or1k-elf-cc -Isim/testsuite/or1k -Wa,-Isim/testsuite/or1k -c -o load.S.o
sim/testsuite/or1k/load.S
$ ./ld/ld-new load.S.o -T sim/testsuite/or1k/or1k-test.ld -o load.S.x
./ld/ld-new: warning: load.S.x has a LOAD segment with RWX permissions
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-01-03 6:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 6:09 vapier at gentoo dot org [this message]
2023-07-30 16:52 ` [Bug sim/29957] " sam at gentoo dot org
2023-08-19 7:29 ` shorne at sourceware dot org
2023-08-19 10:03 ` shorne at sourceware dot org
2023-08-24 7:20 ` shorne at sourceware dot org
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=bug-29957-4717@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/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).