From: Jonas Maebe <jonas.maebe@elis.ugent.be>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Fix dyngen failure on PPC.
Date: Sun, 1 May 2005 22:29:21 +0200 [thread overview]
Message-ID: <5a8682dc45aca2e20b6d7926a147fa65@elis.ugent.be> (raw)
In-Reply-To: <200505011804.43687.paul@codesourcery.com>
On 01 May 2005, at 19:04, Paul Brook wrote:
> This is not correct.
> If the blr is not at the end of the function, things will break.
> dyngen assumes the last instruction is the only return instruction in
> the
> function. This allows it to remove the blr insn and concatenate
> multiple
> functions together.
Can't we on PPC just replace all blr's with plain branches to the
instruction after end of the function? (since all instructions are 32
bit long)
Jonas
next prev parent reply other threads:[~2005-05-01 20:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-30 11:10 [Qemu-devel] [PATCH] Fix dyngen failure on PPC David Woodhouse
2005-05-01 17:04 ` Paul Brook
2005-05-01 20:15 ` Flavio Visentin
2005-05-01 20:35 ` Paul Brook
2005-05-01 20:29 ` Jonas Maebe [this message]
2005-05-01 20:49 ` Paul Brook
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=5a8682dc45aca2e20b6d7926a147fa65@elis.ugent.be \
--to=jonas.maebe@elis.ugent.be \
--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).