From: Richard Henderson <rth@twiddle.net>
To: Stefan Weil <sw@weilnetz.de>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [RFC] TCI for ARM and other hosts with aligned args
Date: Tue, 10 Sep 2013 14:52:50 -0700 [thread overview]
Message-ID: <522F94B2.5030300@twiddle.net> (raw)
In-Reply-To: <522F907F.4090600@weilnetz.de>
On 09/10/2013 02:34 PM, Stefan Weil wrote:
> For native compilations, TCG_TARGET_CALL_ALIGN_ARGS can be set from
> configure. Cross compilations cannot set that macro automatically
> (or is there some way to do this?)
I can't think of a way that would be reasonable from configure.
> Should we use this mechanism for all hosts (and move the definitions in
> tcg-target.h to a conditional definition in tcg.h), or should we use it only for TCI?
I'd prefer a common solution, but it's something easy to get wrong
if there are multiple ABIs in play, e.g. PPC32.
Perhaps let's start with just TCI.
> The alpha disassembler does not work on 32 bit hosts,
> therefore debugging is difficult.
It works on i386. What's your "not working" test case?
r~
next prev parent reply other threads:[~2013-09-10 21:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 19:47 [Qemu-devel] [RFC] TCG unit testing Richard Henderson
2013-08-23 20:42 ` Stefan Weil
2013-08-23 21:18 ` Richard Henderson
2013-08-25 17:13 ` Peter Maydell
2013-08-25 19:45 ` Stefan Weil
2013-09-10 21:34 ` [Qemu-devel] [RFC] TCI for ARM and other hosts with aligned args (was: Re: [RFC] TCG unit testing) Stefan Weil
2013-09-10 21:52 ` Richard Henderson [this message]
2013-09-10 22:04 ` [Qemu-devel] [RFC] TCI for ARM and other hosts with aligned args Stefan Weil
2013-09-10 22:22 ` Peter Maydell
2013-09-11 5:05 ` Stefan Weil
2013-09-10 21:57 ` [Qemu-devel] [RFC] TCI for ARM and other hosts with aligned args (was: Re: [RFC] TCG unit testing) Peter Maydell
2013-08-27 3:18 ` [Qemu-devel] [RFC] TCG unit testing Lei Li
2013-09-02 16:07 ` Aurelien Jarno
2013-09-07 2:38 ` Rob Landley
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=522F94B2.5030300@twiddle.net \
--to=rth@twiddle.net \
--cc=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.