From: Mark Mitchell <mark@codesourcery.com>
To: Geoffrey Keating <geoffk@apple.com>
Cc: gcc List <gcc@gcc.gnu.org>
Subject: Re: attribute data structure rewrite
Date: Fri, 24 Sep 2004 22:29:00 -0000 [thread overview]
Message-ID: <41549410.6080701@codesourcery.com> (raw)
In-Reply-To: <FA388EC7-0DBB-11D9-8B78-000A95B1F520@apple.com>
Geoffrey Keating wrote:
> As a precondition for other compile speed improvements, I've been
> rewriting the way that GCC represents attributes. The result is a
> medium-size patch that touches every language and many targets (a
> surprising number of targets don't define any special attributes at all).
>
> 1. Do we think this would be acceptable for stage 3, or should I make
> a branch?
It might be acceptable for Stage 3 if the subsequent follow-on patches
demonstrated a noticable performance improvement. It should be a branch
until you can demonstrate that improvement. The final decision on
acceptability will probably hinge on how mechanical the patch is: even
if large, if it is quite mechanical (as I would anticipate), that will
make it less worrisome.
--
Mark Mitchell
CodeSourcery, LLC
(916) 791-8304
mark@codesourcery.com
prev parent reply other threads:[~2004-09-24 21:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-24 0:15 Geoffrey Keating
2004-09-24 0:34 ` Andrew Pinski
2004-09-24 1:30 ` Joseph S. Myers
2004-09-24 1:47 ` Zack Weinberg
2004-09-24 6:52 ` Geoffrey Keating
2004-09-24 1:40 ` Gabriel Dos Reis
2004-09-24 2:34 ` Giovanni Bajo
2004-09-24 2:59 ` Gabriel Dos Reis
2004-09-24 4:17 ` Giovanni Bajo
2004-09-24 4:18 ` Gabriel Dos Reis
2004-09-24 8:40 ` Andreas Schwab
2004-09-24 8:40 ` Andreas Schwab
2004-09-24 9:17 ` Joseph S. Myers
2004-09-24 14:45 ` Giovanni Bajo
2004-09-24 8:36 ` Geoffrey Keating
2004-09-24 14:03 ` Joseph S. Myers
2004-09-24 2:35 ` Giovanni Bajo
2004-09-24 8:33 ` Geoffrey Keating
2004-09-24 12:24 ` Nathan Sidwell
2004-09-24 22:29 ` Mark Mitchell [this message]
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=41549410.6080701@codesourcery.com \
--to=mark@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=geoffk@apple.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).