From: Jan Beulich <jbeulich@suse.com>
To: Binutils <binutils@sourceware.org>
Cc: "H.J. Lu" <hjl.tools@gmail.com>
Subject: [PATCH 0/3] x86: further disassembler tweaks
Date: Mon, 24 Apr 2023 09:33:29 +0200 [thread overview]
Message-ID: <61597ebf-cc5e-2029-6520-31f7adfeea68@suse.com> (raw)
The first patch is an attempt to deal with recently uncovered (but
latently present for longer) dangling pointer warnings issued by gcc.
I'll commit this patch right away, in the hope that it helps. The
latter two patches address observations made while checking whether
the approach taken in patch 1 is actually safe. I'll keep these pending
for a few days, in case there are comments (or even objections).
1: work around compiler diagnosing dangling pointer
2: limit data passed to prefix_name()
3: limit data passed to i386_dis_printf()
Jan
next reply other threads:[~2023-04-24 7:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 7:33 Jan Beulich [this message]
2023-04-24 7:34 ` [PATCH 1/3] x86: work around compiler diagnosing dangling pointer Jan Beulich
2023-04-24 10:24 ` Alan Modra
2023-04-24 10:35 ` Jan Beulich
2023-04-24 7:35 ` [PATCH 2/3] x86: limit data passed to prefix_name() Jan Beulich
2023-04-24 7:35 ` [PATCH 3/3] x86: limit data passed to i386_dis_printf() Jan Beulich
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=61597ebf-cc5e-2029-6520-31f7adfeea68@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.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).