qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org, daimon55@free.fr
Subject: Re: [Qemu-devel] Re: MacOSX CVS build broken
Date: Fri, 21 Jan 2005 23:08:37 +0000	[thread overview]
Message-ID: <200501212308.37792.paul@codesourcery.com> (raw)
In-Reply-To: <pan.2005.01.21.22.38.42.149661@reply.to>

>     d9d8:       4d 81 00 20     bgtlr
>     d9dc:       4b ff ff cc     b       d9a8 <op_pmaddwd_mmx+0x24>
>
> this really don't end with blr, but if I have understood correctly
> what I have found about bgtlr, it should do what blr do with some
> condition on r0.
> May be dyngen should verify on 4bffffcc too and not only 4e800020.

No, this is not correct.

The reason qemu expects the code sequence to end with blr is because it 
assumes the routine only has a single return statement at the end of the 
function. It then removes that return instructions to chain multiple ops 
together into a single block.

You'll notice that the preceding instruction is bgtlr, so simply accepting the 
"b" would break this assumtion.

The correct solution is to add FORCE_RET() to the end of the end of op_pmaddwd 
in ops_sse.h.

The same probably applies to many of the other routines in that file.

Paul

  reply	other threads:[~2005-01-21 23:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BE0DEDA1.15F79%johnt@jdtangney.com>
2005-01-16  4:28 ` [Qemu-devel] Re: MacOSX CVS build broken Tim Douglas
2005-01-16  6:08   ` Phil Krylov
2005-01-21 22:38   ` Ronald
2005-01-21 23:08     ` Paul Brook [this message]
2005-01-21 23:09     ` Johannes Schindelin
2005-01-21 23:14     ` Daniel Egger
2005-01-23 21:11       ` Fabrice Bellard

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=200501212308.37792.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=daimon55@free.fr \
    --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).