From: Peter Maydell <peter.maydell@linaro.org>
To: Samuel Tardieu <sam@rfc1149.net>
Cc: qemu-devel@nongnu.org, Richard Henderson <richard.henderson@linaro.org>
Subject: Re: [PATCH v2 0/2] tcg: Jump after always false condition
Date: Mon, 15 Jan 2024 17:11:26 +0000 [thread overview]
Message-ID: <CAFEAcA__cuJaphqWJKSRJ2Zn+2t0xaxOGgzSLE9OCE24jNxSfQ@mail.gmail.com> (raw)
In-Reply-To: <20231219182212.455952-1-sam@rfc1149.net>
On Tue, 19 Dec 2023 at 18:23, Samuel Tardieu <sam@rfc1149.net> wrote:
>
> Unreachable code in an error handling block is listed in issue
> https://gitlab.com/qemu-project/qemu/-/issues/2030.
>
> After removing this code, the `fail` label is now immediately followed
> by a test whose condition can never be true when coming explicitly
> via this label. Moving the label down preserves the fall-through
> case while avoiding testing an always false condition.
>
> Changes from v1:
> - Add a comment explaining that `buf_rx` does not require cleanup
> - Use a unique cleanup path for the function by setting `errno` before
> jumping to the cleanup block.
>
> Samuel Tardieu (2):
> tcg: Remove unreachable code
> tcg: Make the cleanup-on-error path unique
>
> tcg/region.c | 10 ++++------
> 1 file changed, 4 insertions(+), 6 deletions(-)
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
RTH: I'm assuming you'll take this via your tcg tree.
thanks
-- PMM
next prev parent reply other threads:[~2024-01-15 17:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 18:22 [PATCH v2 0/2] tcg: Jump after always false condition Samuel Tardieu
2023-12-19 18:22 ` [PATCH v2 1/2] tcg: Remove unreachable code Samuel Tardieu
2023-12-19 18:22 ` [PATCH v2 2/2] tcg: Make the cleanup-on-error path unique Samuel Tardieu
2024-01-15 17:11 ` Peter Maydell [this message]
2024-01-15 22:01 ` [PATCH v2 0/2] tcg: Jump after always false condition Richard Henderson
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=CAFEAcA__cuJaphqWJKSRJ2Zn+2t0xaxOGgzSLE9OCE24jNxSfQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=sam@rfc1149.net \
/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).