qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Fix dyngen failure on PPC.
Date: Sun, 1 May 2005 21:35:43 +0100	[thread overview]
Message-ID: <200505012135.44060.paul@codesourcery.com> (raw)
In-Reply-To: <427538F4.8070502@zipman.it>

On Sunday 01 May 2005 21:15, Flavio Visentin wrote:
> > This is not correct.
> > If the blr is not at the end of the function, things will break.
>
> [SNIP]
>
> > This basically only ever worked because gcc could be coerced into
> > generating relatively simple code. GCC4 contains much more aggressive
> > high level optimizers, so this is no longer possible.
>
> I don't know almost anything about gcc, so I'm asking two questions:
>
> 1) Isn't there any kind of compiler directive to force no optimization
> only for a portion of the code?

Optimiziation is controlled on a per-file bases.

> 2) If there aren't such directives is it possible to link together
> optimized obj with not optimized obj? In this case you could group
> functions that require no optimization and link them with the other
> optimized code.

Linking together objects compiled with and without optimization isn't a 
problem, however...

Disabling optimization isn't really an option because (a) it causes other 
problems, and (b) the code generate is awfully slow.
The real solution is to teach qemu how to generate native code from and remove 
dyngen altogether, but that's a lot of work. Look in the list archives for 
more details.

Paul

  reply	other threads:[~2005-05-01 21:04 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 [this message]
2005-05-01 20:29   ` Jonas Maebe
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=200505012135.44060.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --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).