public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mike Stump <mrs@apple.com>
To: Steven Bosscher <stevenb@suse.de>
Cc: Paolo Bonzini <bonzini@gnu.org>,
	Karel Gardas <kgardas@objectsecurity.com>,
	GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: Compilation performance comparison of gcc3.4.1 and gcc3.5.0 2004-08-30 on MICO sources
Date: Tue, 31 Aug 2004 19:30:00 -0000	[thread overview]
Message-ID: <8100F39E-FB82-11D8-8516-000393941EE6@apple.com> (raw)
In-Reply-To: <200408311249.32872.stevenb@suse.de>

On Aug 31, 2004, at 3:49 AM, Steven Bosscher wrote:
> This may also just be noise.  Some passes run so fast that the
> time vars are not accurate enough to record it.

We at apple use ~10ns clocks to record times...  works better...  Only 
problem, getting user/sys time out of the kernel into user space, so 
that merely grabbing time isn't costly.  :-(  Not really a problem, as 
wall is the only thing you can trust, and what matters the most anyway.

  reply	other threads:[~2004-08-31 19:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-31  9:58 Karel Gardas
2004-08-31 10:12 ` Steven Bosscher
2004-08-31 10:28   ` Karel Gardas
2004-08-31 10:44     ` Paolo Bonzini
2004-08-31 10:46       ` Karel Gardas
2004-08-31 10:49         ` Steven Bosscher
2004-08-31 11:00           ` Paolo Bonzini
2004-08-31 11:24             ` Steven Bosscher
2004-08-31 19:30               ` Mike Stump [this message]
2004-08-31 12:48             ` Karel Gardas
2004-09-01  7:18               ` Paolo Bonzini
2004-08-31 10:55         ` Steven Bosscher
2004-08-31 13:57           ` Karel Gardas
2004-09-01 11:18 ` Giovanni Bajo
2004-09-02  9:41   ` Karel Gardas
2004-09-02 20:32     ` Compilation performance comparison of gcc3.4.1 and gcc3.5.02004-08-30 " Giovanni Bajo
2004-09-04  7:35       ` Karel Gardas
2004-09-02  9:44   ` Compilation performance comparison of gcc3.4.1 and gcc3.5.0 2004-08-30 " 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=8100F39E-FB82-11D8-8516-000393941EE6@apple.com \
    --to=mrs@apple.com \
    --cc=bonzini@gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=kgardas@objectsecurity.com \
    --cc=stevenb@suse.de \
    /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).