public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andreas Jaeger <aj@suse.de>
To: larsbj@gullik.net (Lars Gullik Bjønnes)
Cc: gcc@gcc.gnu.org
Subject: Re: Speed issues taken seriously?
Date: Fri, 10 Oct 2003 15:42:00 -0000	[thread overview]
Message-ID: <u8r81l8742.fsf@gromit.moeb> (raw)
In-Reply-To: <m3oewpno6b.fsf@tyfon.gullik.net> (Lars Gullik Bjønnes's message of "Fri, 10 Oct 2003 16:49:00 +0200")

[-- Attachment #1: Type: text/plain, Size: 627 bytes --]

larsbj@gullik.net (Lars Gullik Bjønnes) writes:

> I just thought that I'd see how gcc 3.3.2 (CVS) and 3.4(CVS) compared,
> I was hoping (expecting) the recent months long threads on compile
> performance to have had an effect... the result was a bit
> disappointing...

How did you configure GCC exactly?  Please use --disable-checking so
that the checking code is disabled, it causes some run-time overhead.

Andreas
-- 
 Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj
  SuSE Linux AG, Deutschherrnstr. 15-19, 90429 Nürnberg, Germany
   GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2003-10-10 15:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-10 15:21 Lars Gullik Bjønnes
2003-10-10 15:21 ` Steven Bosscher
2003-10-10 15:57   ` Lars Gullik Bjønnes
2003-10-10 17:03     ` Andreas Jaeger
2003-10-10 15:42 ` Andreas Jaeger [this message]
2003-10-10 16:33   ` Lars Gullik Bjønnes
2003-10-10 17:04     ` Lars Gullik Bjønnes
2003-10-10 17:49       ` Jan Hubicka
2003-10-10 17:49       ` Andreas Jaeger
2003-10-15 18:06       ` Lars Gullik Bjønnes
2003-10-18 12:44         ` Gerald Pfeifer
2003-10-18 14:26           ` Jan Hubicka
2003-10-18 17:51             ` Joel Sherrill
2003-10-18 18:30               ` Jan Hubicka
2003-10-10 19:37 ` Daniel Berlin

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=u8r81l8742.fsf@gromit.moeb \
    --to=aj@suse.de \
    --cc=gcc@gcc.gnu.org \
    --cc=larsbj@gullik.net \
    /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).