From: Richard Henderson <richard.henderson@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: peter.maydell@linaro.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 2/2] tcg/optimize: Flush data at labels not TCG_OPF_BB_END
Date: Wed, 21 Oct 2020 08:51:01 -0700 [thread overview]
Message-ID: <46f2f32b-28bd-5164-edce-00c18d93b692@linaro.org> (raw)
In-Reply-To: <878sbzwrrg.fsf@linaro.org>
On 10/21/20 7:57 AM, Alex Bennée wrote:
> The optimize function has a lot of goto's in it and I find generally
> hard to follow. Anyway:
Yes. We'll call it inherited code that could use a re-factor.
r~
next prev parent reply other threads:[~2020-10-21 15:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-13 22:23 [PATCH 0/2] tcg: optimize across branches Richard Henderson
2020-10-13 22:23 ` [PATCH 1/2] tcg: Do not kill globals at conditional branches Richard Henderson
2020-10-21 13:29 ` Alex Bennée
2020-10-13 22:23 ` [PATCH 2/2] tcg/optimize: Flush data at labels not TCG_OPF_BB_END Richard Henderson
2020-10-21 14:57 ` Alex Bennée
2020-10-21 15:51 ` Richard Henderson [this message]
2020-10-19 23:04 ` [PATCH 0/2] tcg: optimize across branches 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=46f2f32b-28bd-5164-edce-00c18d93b692@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).