From: Luca Boccassi <luca.boccassi@gmail.com>
To: binutils@sourceware.org
Subject: Re: Re: Output section type (READONLY)
Date: Sat, 29 Jan 2022 16:46:34 +0000 [thread overview]
Message-ID: <aadb8657d7cf32627893b1e8b61b5f11367e25fe.camel@gmail.com> (raw)
In-Reply-To: <20220129074545.csaig4kn5bk4si5k@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 814 bytes --]
> [PATCH v2] ld: add READONLY attribute for SECTIONS
> (https://sourceware.org/pipermail/binutils/2021-July/117492.html)
> added
> READONLY. There was no justification as to why it was added.
It was already explained - READONLY is necessary for notes, otherwise
they are marked as writable:
[ 3] .note.package NOTE 00000000000002e8 000002e8
0000000000000030 0000000000000000 WA 0 0 4
> What went lucky is that
> https://sourceware.org/binutils/docs/ld/Output-Section-Type.html does
> not have
> the feature listed yet, so hopefully very few people will be lured to
> use this.
The documentation update is already committed in the repository, I
imagine it will be published on the website after the new release is
out.
--
Kind regards,
Luca Boccassi
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-01-29 16:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 7:45 Fangrui Song
2022-01-29 16:46 ` Luca Boccassi [this message]
2022-01-29 18:51 ` Fangrui Song
2022-01-31 13:33 ` Nick Clifton
2022-02-01 3:39 ` Fangrui Song
2022-02-01 11:07 ` Nick Clifton
2022-02-01 11:59 ` Luca Boccassi
2022-02-02 7:29 ` Fangrui Song
2022-02-02 16:54 ` Michael Matz
2022-02-02 18:12 ` Luca Boccassi
2022-02-16 17:38 ` Nick Clifton
2022-02-16 19:03 ` Luca Boccassi
2022-02-17 2:12 ` Fangrui Song
2022-02-21 23:04 ` Alan Modra
2022-02-21 23:30 ` Fangrui Song
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=aadb8657d7cf32627893b1e8b61b5f11367e25fe.camel@gmail.com \
--to=luca.boccassi@gmail.com \
--cc=binutils@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).