From: Jan Kiszka <jan.kiszka@web.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: dyngen-exec.h cleanup
Date: Sun, 08 Mar 2009 17:39:24 +0100 [thread overview]
Message-ID: <49B3F4BC.4090807@web.de> (raw)
In-Reply-To: <761ea48b0903080912y49fdecd1g124f01a475c6243d@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1448 bytes --]
Laurent Desnogues wrote:
> On Sun, Mar 8, 2009 at 5:00 PM, Jan Kiszka <jan.kiszka@web.de> wrote:
>> Laurent Desnogues wrote:
> [...]
>>> Yes, and I did the work for ARM. However when considering the
>>> removal of AREG0, and after looking at generated code, I came
>>> to the perhaps premature conclusion that removing it would not
>>> bring me any speedup (at least for a not so register starved
>>> target as x86_64).
>> I don't think we are looking for speedup here, just for cleanup. Status
>> quo regarding performance after a conversion would be more than fine IMHO.
>
> I was ambiguous, I meant I expect slowdowns... But given how many
> times I was wrong in the past when I thought some tricks would
> speedup things, I should probably not trust my a priori.
>
>>> Well dyngen-exec.h is long gone in my sources even though
>>> AREG0 is still used. I would have to backtrack my changes to
>>> see how I arrived to that, but for sure the first thing to do is to
>>> remove cpu_T from ARM target.
>> Yes, please share your wisdom!
>
> Sorry if I sounded arrogant, I just wanted to highlight the fact one
> can achieve your aim. As far as sharing goes, that's another
> story.
No, no, you didn't sound arrogant. I just forgot your boundary conditions.
But it's good to know that there might be a way to overcome
dyngen-exec.h without dropping AREGs altogether in case performance
requires this.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2009-03-08 16:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-08 13:25 [Qemu-devel] dyngen-exec.h cleanup Blue Swirl
2009-03-08 14:41 ` [Qemu-devel] " Jan Kiszka
2009-03-08 15:03 ` Laurent Desnogues
2009-03-08 15:36 ` Jan Kiszka
2009-03-08 15:46 ` Laurent Desnogues
2009-03-08 16:00 ` Jan Kiszka
2009-03-08 16:12 ` Laurent Desnogues
2009-03-08 16:39 ` Jan Kiszka [this message]
2009-03-08 15:16 ` [Qemu-devel] " Hasso Tepper
2009-03-08 16:28 ` Anthony Liguori
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=49B3F4BC.4090807@web.de \
--to=jan.kiszka@web.de \
--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).