From: Indu Bhagat <indu.bhagat@oracle.com>
To: Steven Rostedt <rostedt@goodmis.org>, linux-toolchains@vger.kernel.org
Subject: SFrame version 2 in upcoming Binutils 2.41
Date: Fri, 7 Jul 2023 16:01:58 -0700 [thread overview]
Message-ID: <9deb1692-46e8-cd29-92d6-8865892d2a78@oracle.com> (raw)
Hi,
Binutils 2.41 release (planned to be released soon) will feature SFrame
version 2. One of main changes in SFrame version 2 is that the SFrame
Function Descriptor Entry (FDE) is now 20 bytes. This keeps all data
members of SFrame FDE naturally aligned.
All data structures continue to be packed in the on-disk representation.
SFrame FREs (Frame Row Entries) will continue to potentially have
members not aligned at their natural boundaries (Recall that SFrame FREs
are variable length entries).
Changes have been made to the GNU as, ld, objdump/readelf support: the
default version supported is SFrame version 2. The SFrame spec has also
been updated.
Relevant commits:
[sframe: bfd: gas: ld: format bump to SFrame version 2]
https://sourceware.org/pipermail/binutils/2023-June/128141.html
[doc: sframe: update specification for SFRAME_VERSION_2]
https://sourceware.org/pipermail/binutils/2023-June/128140.html
[binutils/NEWS: announce SFrame version 2 as the new default]
https://sourceware.org/pipermail/binutils/2023-June/128139.html
Please let me know if there are any questions or feedback,
Indu
next reply other threads:[~2023-07-07 23:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 23:01 Indu Bhagat [this message]
2023-07-07 23:43 ` SFrame version 2 in upcoming Binutils 2.41 Nick Desaulniers
2023-07-10 17:19 ` Indu Bhagat
2023-08-04 22:21 ` Indu Bhagat
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=9deb1692-46e8-cd29-92d6-8865892d2a78@oracle.com \
--to=indu.bhagat@oracle.com \
--cc=linux-toolchains@vger.kernel.org \
--cc=rostedt@goodmis.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 NNTP newsgroup(s).