From: Per Bothner <per@bothner.com>
To: Mark Mitchell <mark@codesourcery.com>
Cc: gcc@gcc.gnu.org, java@gcc.gnu.org
Subject: Re: GCC Status Report (2004-09-13) [--enable-mapped-location]
Date: Thu, 16 Sep 2004 19:28:00 -0000 [thread overview]
Message-ID: <4149E1F7.5070009@bothner.com> (raw)
In-Reply-To: <4149DF81.70105@codesourcery.com>
Mark Mitchell wrote:
> I think you should at least try for initial numbers on whatever machine
> you're using. Try compiling libstdc++, say, at least. If your patches
> aren't a performance win, they're not going to be terribly compelling;
> if they are a win, as expected, then that will make them much more
> compelling.
It will take a couple of days, at best, as I'll be travelling.
Any earlier C-only test didn't show a clear difference either way.
The patches are "winning" even if the immediate performance difference
is a wash because they'll allow us to track column numbers at little
or no extra cost.
--
--Per Bothner
per@bothner.com http://per.bothner.com/
next prev parent reply other threads:[~2004-09-16 18:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-14 0:30 GCC Status Report (2004-09-13) Mark Mitchell
2004-09-14 1:14 ` Andrew Pinski
2004-09-14 1:28 ` Jan Hubicka
2004-09-14 5:02 ` Jeffrey A Law
2004-09-14 5:58 ` Mark Mitchell
2004-09-14 6:29 ` Jeffrey A Law
2004-09-14 15:54 ` Jan Hubicka
2004-09-14 17:07 ` Mark Mitchell
2004-09-14 6:28 ` Mark Mitchell
2004-09-15 21:25 ` Scott Robert Ladd
2004-09-16 21:58 ` Mark Mitchell
2004-09-16 15:58 ` GCC Status Report (2004-09-13) [--enable-mapped-location] Per Bothner
2004-09-16 18:45 ` Mark Mitchell
2004-09-16 18:56 ` Per Bothner
2004-09-16 19:02 ` Mark Mitchell
2004-09-16 19:03 ` Matt Austern
2004-09-16 19:31 ` Mark Mitchell
2004-09-16 22:50 ` Steven Bosscher
2004-09-16 19:28 ` Per Bothner [this message]
2004-09-16 19:46 ` Mark Mitchell
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=4149E1F7.5070009@bothner.com \
--to=per@bothner.com \
--cc=gcc@gcc.gnu.org \
--cc=java@gcc.gnu.org \
--cc=mark@codesourcery.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).