From: Giuliano Procida <gprocida@google.com>
To: libabigail@sourceware.org
Cc: dodji@seketeli.org, kernel-team@android.com, gprocida@google.com,
maennich@google.com, mark@klomp.org
Subject: [PATCH 0/1] Fix interpretation of ARM32 CFI
Date: Tue, 11 Jan 2022 16:34:11 +0000 [thread overview]
Message-ID: <20220111163412.3012602-1-gprocida@google.com> (raw)
Hi.
This patch ensures correct symbol address for ARM32 shared libraries
that have been complied with CFI.
I have no idea what the implications are for PPC64. It's also possible
the fix-up code would better belong in some kind of helper.
Feedback welcome as always!
Regards,
Giuliano.
Giuliano Procida (1):
symtab reader: fix up alternative addresses
src/abg-symtab-reader.cc | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
--
2.34.1.575.g55b058a8bb-goog
next reply other threads:[~2022-01-11 16:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 16:34 Giuliano Procida [this message]
2022-01-11 16:34 ` [PATCH 1/1] symtab reader: fix up alternative addresses Giuliano Procida
2022-01-11 17:46 ` [PATCH 0/1] Fix interpretation of ARM32 CFI Mark Wielaard
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=20220111163412.3012602-1-gprocida@google.com \
--to=gprocida@google.com \
--cc=dodji@seketeli.org \
--cc=kernel-team@android.com \
--cc=libabigail@sourceware.org \
--cc=maennich@google.com \
--cc=mark@klomp.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).