qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "developer@isl-gbr.de" <developer@isl-gbr.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] X86_64 (AMD64) build segfaults
Date: Fri, 22 Apr 2005 18:30:19 +0200	[thread overview]
Message-ID: <20050422183019.228a8cfd@smirftschs.home.tld> (raw)
In-Reply-To: <8737c432399be6c4c8b349c300916cd8@elis.ugent.be>

I don't think it'll be possible for me to fix this, i don't have any knowledge about these functions at all...


On Fri, 22 Apr 2005 18:12:10 +0200
Jonas Maebe <jonas.maebe@elis.ugent.be> wrote:

> 
> On 22 apr 2005, at 17:41, developer@isl-gbr.de wrote:
> 
> > Hello Jonas, here is the output of the command you gave me for this 
> > function, does this help ?
> 
> It helps in the sense that it confirms my suspicion, although I don't 
> know why it creates such convoluted code. Maybe in order to have as 
> small code as possible with at the same time as many aligned jump 
> targets as possible. It's definitely not trivial to parse this, and 
> even less trivial to rewrite it so it is usable for qemu's purposes (in 
> this particular case, the retq could be replaced by a jmp, but you 
> can't count on there being 4 padding bytes after each ret).
> 
> You (or someone else) will have to find a way to force gcc 4.0 to put 
> one ret (or jump) at the very end of the code it generates. If that's 
> not possible, it will be quite hard to support gcc 4.0 in qemu...
> 
> 
> Jonas
> 
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel

  reply	other threads:[~2005-04-22 16:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-21 14:34 [Qemu-devel] X86_64 (AMD64) build segfaults developer
2005-04-21 14:42 ` Paul Brook
2005-04-21 14:59   ` developer
2005-04-21 15:01     ` Paul Brook
2005-04-21 16:02       ` developer
2005-04-22 14:50       ` developer
2005-04-22 15:01         ` Jonas Maebe
2005-04-22 15:41           ` developer
2005-04-22 16:12             ` Jonas Maebe
2005-04-22 16:30               ` developer [this message]
2005-04-22 16:33               ` Paul Brook
2005-04-23  9:05                 ` developer
2005-04-23 11:33                   ` Paul Brook
2006-03-15  8:15                     ` [Qemu-devel] Dynamic compiler future (was Re: X86_64 (AMD64) build segfaults) Antti P Miettinen
2005-04-22 22:12               ` [Qemu-devel] X86_64 (AMD64) build segfaults Joshua Root
2005-04-21 15:11     ` Paul Brook
  -- strict thread matches above, loose matches on Subject: below --
2005-04-22 16:35 Jung-uk Kim
2005-04-22 16:49 Jung-uk Kim
2005-04-23  9:06 ` developer
2005-05-02 17:40   ` Jung-uk Kim

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=20050422183019.228a8cfd@smirftschs.home.tld \
    --to=developer@isl-gbr.de \
    --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).