From: Gerald Pfeifer <gp@suse.de>
To: Karel Gardas <kgardas@objectsecurity.com>
Cc: Eric Christopher <echristo@redhat.com>,
GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: GCC 3.4.0 20040114 + GCC 3.3.2 compile-time performance comparison on MICO project sources.
Date: Mon, 19 Jan 2004 20:01:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.58.0401192100110.1599@D209.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.43.0401192053150.8443-100000@thinkpad.wg-ro-gar1.inext.cz>
On Mon, 19 Jan 2004, Karel Gardas wrote:
> OK, I have thought that the -O0 -g (perhaps) build is the most important
> from compile-time performance view, as it is probably used for
> development...
Just as an example, in DLV (origin of PR8361) I switched to -O1 years
ago because that was _faster_ than -O0 at that time, debugging was still
okay, and test runs with the generated binary were much faster.
-O0 really is not too useful in some contexts.
Gerald
--
Gerald Pfeifer <gp@suse.de> Technical Project Manager, SUSE Linux AG
next prev parent reply other threads:[~2004-01-19 20:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 19:43 Karel Gardas
2004-01-19 19:49 ` Eric Christopher
2004-01-19 19:53 ` Karel Gardas
2004-01-19 19:57 ` Eric Christopher
2004-01-19 20:01 ` Gerald Pfeifer [this message]
2004-01-19 20:06 ` Karel Gardas
2004-01-20 9:20 ` [UPDATED] " Karel Gardas
2004-01-20 9:48 ` Steven Bosscher
2004-01-20 9:52 ` Karel Gardas
2004-01-20 11:31 ` Giovanni Bajo
2004-01-20 11:52 ` Giovanni Bajo
2004-01-20 18:47 ` Bugreports from MICO compile-time testing submited [was: Re: [UPDATED] GCC 3.4.0 20040114 + GCC 3.3.2 compile-time performance comparison on MICO project sources.] Karel Gardas
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=Pine.LNX.4.58.0401192100110.1599@D209.suse.de \
--to=gp@suse.de \
--cc=echristo@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=kgardas@objectsecurity.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).