qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: malc <av1474@comtv.ru>
To: Stuart Brady <sdbrady@ntlworld.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] tcg, tci: Add TCG and interpreter for bytecode (virtual machine)
Date: Mon, 12 Oct 2009 16:33:10 +0400 (MSD)	[thread overview]
Message-ID: <Pine.LNX.4.64.0910121624010.2142@linmac.oyster.ru> (raw)
In-Reply-To: <20091012064652.GA10789@miranda.arrow>

On Mon, 12 Oct 2009, Stuart Brady wrote:

> On Mon, Oct 12, 2009 at 03:50:31AM +0400, malc wrote:
> > yOn Mon, 12 Oct 2009, Stuart Brady wrote:
> > 
> > No it's not, given that there are ABIs with argument alignment and
> > the fact that information about the types doesn't exist at the point
> > of op_call things just aren't that simple.
> 
> Huh?  If you're using a function pointer with the *correct* type,
> I hardly see how that's not sufficient.

Let me give you an example:

tcg$ cat << eof | gcc-4.4.1 -O -o - -S -x c -
> unsigned long long moo1 (int dummy, unsigned long long a)
> {
>     return ((unsigned long) (a >> 32)) | (a << 32);
> }
> 
> unsigned long long moo2 (int dummy1, int dummy2, unsigned long long a)
> {
>     return ((unsigned long) (a >> 32)) | (a << 32);
> }
> eof
        .file   ""
        .gnu_attribute 4, 1
        .gnu_attribute 8, 1
        .gnu_attribute 12, 2
        .section        ".text"
        .align 2
        .globl moo1
        .type   moo1, @function
moo1:
        mr 3,6
        mr 4,5
        blr
        .size   moo1, .-moo1
        .align 2
        .globl moo2
        .type   moo2, @function
moo2:
        mr 3,6
        mr 4,5
        blr
        .size   moo2, .-moo2
        .ident  "GCC: (GNU) 4.4.1"
        .section        .note.GNU-stack,"",@progbits

tcg$ uname -mo
ppc GNU/Linux

I hope it's self explanatory.

> 
> Yes, I did notice that the information doesn't exist at that point,
> (in fact I did so before the previous time that you pointed this out).
> 
> Cheers,
> 

-- 
mailto:av1474@comtv.ru

  reply	other threads:[~2009-10-12 12:33 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-28 16:50 [Qemu-devel] [RFC] tcg/interpreter: Add TCG + interpreter for bytecode (virtual machine) Stefan Weil
2009-09-28 16:50 ` [Qemu-devel] [PATCH] tcg, tci: Add TCG and " Stefan Weil
2009-09-28 18:42   ` Blue Swirl
2009-09-28 21:33     ` Stefan Weil
2009-10-04 18:27   ` Stuart Brady
2009-10-11 16:33     ` Stefan Weil
2009-10-11 16:55       ` malc
2009-10-11 21:04       ` malc
2009-10-26 15:26         ` Stefan Weil
2009-10-26 15:52           ` malc
2009-10-11 23:17       ` Stuart Brady
2009-10-11 23:50         ` malc
2009-10-12  6:46           ` Stuart Brady
2009-10-12 12:33             ` malc [this message]
2009-10-12 12:55               ` malc
2009-10-12 17:39               ` Stuart Brady
2009-10-12 20:07                 ` malc
2009-10-12 20:30                   ` Stuart Brady
2010-05-12 19:06 ` [Qemu-devel] [RFC] tcg/interpreter: Add TCG + " Stefan Weil
2010-05-13  2:01 ` Jun Koi

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=Pine.LNX.4.64.0910121624010.2142@linmac.oyster.ru \
    --to=av1474@comtv.ru \
    --cc=qemu-devel@nongnu.org \
    --cc=sdbrady@ntlworld.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 NNTP newsgroup(s).