All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Add gcc 4.0 support
Date: Wed, 29 Mar 2006 20:33:52 +0100	[thread overview]
Message-ID: <200603292033.53117.paul@codesourcery.com> (raw)
In-Reply-To: <E5E88543-C778-4819-B014-7E5D78127AED@mac.com>

On Wednesday 29 March 2006 18:03, John Davidorff Pell wrote:
> I was just thinking that by enabling the required feature
> individually, someone else could choose -O0 and not have to
> investigate why it fails. Its not like its a big deal, though. :-)

Like most things dyngen relies on this isn't a feature as such. There's no gcc 
option that says "make sure this function doesn't have a stack frame".
It just happens that at with optimisation turned on this is generally true.

Also, the gcc -O2 option is more than the sum of the other options it enables.

Paul

  parent reply	other threads:[~2006-03-29 19:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-15 12:25 [Qemu-devel] [PATCH] Add gcc 4.0 support Thiemo Seufer
2006-02-15 16:20 ` Johannes Schindelin
2006-02-15 19:10   ` Thiemo Seufer
2006-02-15 22:04     ` Johannes Schindelin
2006-03-28 14:09 ` Thiemo Seufer
2006-03-29  4:26   ` John Davidorff Pell
2006-03-29  9:59     ` Thiemo Seufer
2006-03-29 17:03       ` John Davidorff Pell
2006-03-29 19:24         ` Pascal Terjan
2006-03-29 19:37           ` sofar
2006-03-29 21:21             ` [Off Topic again] " Jim C. Brown
2006-03-29 21:03           ` [Off Topic] " Jim C. Brown
2006-03-29 19:33         ` Paul Brook [this message]
2006-03-31 23:18           ` John Davidorff Pell
2006-04-03 15:42   ` Dirk Behme
2006-04-03 15:50     ` Jim C. Brown

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=200603292033.53117.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.