From: Sebastian Kaliszewski <sk@z.pl>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Stupid (probably) idea wrt dyngen & gcc 3.4 & 4.0
Date: Mon, 9 May 2005 03:55:24 +0200 [thread overview]
Message-ID: <200505090355.24247.sk@z.pl> (raw)
In-Reply-To: <200505090140.57249.paul@nowt.org>
So the idea was indeed stupid :)
On Monday 09 May 2005 02:40, Paul Brook wrote:
> No. The main problem with gcc3.4 was that we weren't using FORCE_RET
> everywhere that we should. This has mostly been fixed now.
I see...
[snip]
>
> I've got a solution for x86/x86-64 that's 95% complete, using the method
> I suggested in a previous email.
So, since ret is too small to be replaced with jump, you relocate the block
following ret few bytes further, and retarget all relevant jumps?
> I hope to be submitting a patch shortly.
> I expect most other hosts (particularly the RISC based ones) to be much
> simpler to fix.
Nice.
rgds
Sebastian Kaliszewski
next prev parent reply other threads:[~2005-05-09 2:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-09 0:02 [Qemu-devel] Stupid (probably) idea wrt dyngen & gcc 3.4 & 4.0 Sebastian Kaliszewski
2005-05-09 0:25 ` André Braga
2005-05-09 0:40 ` Paul Brook
2005-05-09 1:55 ` Sebastian Kaliszewski [this message]
2005-05-09 2:33 ` 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=200505090355.24247.sk@z.pl \
--to=sk@z.pl \
--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).