All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thiemo Seufer <ths@networkno.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Add gcc 4.0 support
Date: Wed, 29 Mar 2006 10:59:47 +0100	[thread overview]
Message-ID: <20060329095947.GE31939@networkno.de> (raw)
In-Reply-To: <F4CBCED7-5B22-4C5F-AC94-7FBCAACC1220@mac.com>

On Tue, Mar 28, 2006 at 08:26:27PM -0800, John Davidorff Pell wrote:
> Out of curiosity, wouldn't it be better to specifically request that  
> feature of gcc, with one of its myriad options, rather than forcing a  
> rather large optimization sweep? I'm sure that -O2 is good generally,  
> but using it as a kludge to get at one of the many things that it  
> enables seems like a not-so-great-idea. Its like buying a restaurant  
> so that you can get a chef's stove.

Well, I went through the ppc disassembly and found no reason to
disable -O2. Note that it was the default before, I only noticed
the breakage when I lowered the global optimisation to -O0 for better
debugging.


Thiemo

  reply	other threads:[~2006-03-29 10:00 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 [this message]
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
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=20060329095947.GE31939@networkno.de \
    --to=ths@networkno.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 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.