qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Flavio Visentin <THe_ZiPMaN@zipman.it>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Fix dyngen failure on PPC.
Date: Sun, 01 May 2005 22:15:48 +0200	[thread overview]
Message-ID: <427538F4.8070502@zipman.it> (raw)
In-Reply-To: <200505011804.43687.paul@codesourcery.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> 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?

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.

Maybe I asked 2 dumb questions, but I'm courious and I'd like to learn
something new :-)

TNX

P.S. I apologize for my bad English :-)

- --
Flavio Visentin

|                     \|||/
|                    @/0.0\@
|                     \ - /
+------------------oOOo---oOOo------------------

There are only 10 types of people in this world:
those who understand binary, and those who don't.

GPG Key: http://www.zipman.it/gpgkey.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFCdTj0usUmHkh1cnoRAs3hAJ48/9uEbjEqNTsa24mKm6Ol62774ACdGpnF
N+EC/lngLa6oytEfDVUO3eA=
=lVHN
-----END PGP SIGNATURE-----

  reply	other threads:[~2005-05-01 20:22 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 [this message]
2005-05-01 20:35     ` Paul Brook
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=427538F4.8070502@zipman.it \
    --to=the_zipman@zipman.it \
    --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).