From: Steven Bosscher <stevenb@suse.de>
To: Matt Austern <austern@apple.com>, Mark Mitchell <mark@codesourcery.com>
Cc: gcc@gcc.gnu.org, Per Bothner <per@bothner.com>, java@gcc.gnu.org
Subject: Re: GCC Status Report (2004-09-13) [--enable-mapped-location]
Date: Thu, 16 Sep 2004 22:50:00 -0000 [thread overview]
Message-ID: <200409162355.59878.stevenb@suse.de> (raw)
In-Reply-To: <29BB7B2C-0812-11D9-B168-000A95AA5E5E@apple.com>
On Thursday 16 September 2004 20:56, Matt Austern wrote:
> Even if this patch doesn't show an immediate performance win, isn't
> simplicity and the possibility of future improvements an argument in
> its favor?
Not to mention the improved maintainability? Having two mechanisms
side by side is one thing GCC does too often already.
If --enable-mapped-location works and does not cause regressions of
any kind, I would think making it the default and removing the old
stuff very compelling.
Gr.
Steven
next prev parent reply other threads:[~2004-09-16 21:58 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 [this message]
2004-09-16 19:28 ` Per Bothner
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=200409162355.59878.stevenb@suse.de \
--to=stevenb@suse.de \
--cc=austern@apple.com \
--cc=gcc@gcc.gnu.org \
--cc=java@gcc.gnu.org \
--cc=mark@codesourcery.com \
--cc=per@bothner.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).