From: Jan Beulich <jbeulich@suse.com>
To: Binutils <binutils@sourceware.org>
Cc: "H.J. Lu" <hjl.tools@gmail.com>, Alan Modra <amodra@gmail.com>
Subject: [PATCH 0/8] x86: do away with (ab)using setjmp/longjmp for error handling
Date: Tue, 4 Apr 2023 08:56:45 +0200 [thread overview]
Message-ID: <5dac45a8-cd5f-ee4d-52fc-7d283fc29ec4@suse.com> (raw)
As per https://sourceware.org/pipermail/binutils/2023-March/126687.html
doing so is problematic.
1: move fetch error handling into a helper function
2: change fetch error handling in top-level function
3: change fetch error handling in ckprefix()
4: change fetch error handling in get_valid_dis386()
5: change fetch error handling when processing operands
6: change fetch error handling for get<N>()
7: drop use of setjmp() from disassembler
8: drop (explicit) BFD64 dependency from assembler
Jan
next reply other threads:[~2023-04-04 6:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 6:56 Jan Beulich [this message]
2023-04-04 6:58 ` [PATCH 1/8] x86: move fetch error handling into a helper function Jan Beulich
2023-04-04 6:58 ` [PATCH 2/8] x86: change fetch error handling in top-level function Jan Beulich
2023-04-04 6:59 ` [PATCH 3/8] x86: change fetch error handling in ckprefix() Jan Beulich
2023-04-04 6:59 ` [PATCH 4/8] x86: change fetch error handling in get_valid_dis386() Jan Beulich
2023-04-04 7:00 ` [PATCH 5/8] x86: change fetch error handling when processing operands Jan Beulich
2023-04-04 7:00 ` [PATCH 6/8] x86: change fetch error handling for get<N>() Jan Beulich
2023-04-04 7:01 ` [PATCH 7/8] x86: drop use of setjmp() from disassembler Jan Beulich
2023-04-04 7:01 ` [PATCH 8/8] x86: drop (explicit) BFD64 dependency " 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=5dac45a8-cd5f-ee4d-52fc-7d283fc29ec4@suse.com \
--to=jbeulich@suse.com \
--cc=amodra@gmail.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).