From: Geoffrey Keating <geoffk@apple.com>
To: Giovanni Bajo <giovannibajo@libero.it>
Cc: gcc@gcc.gnu.org
Subject: Re: attribute data structure rewrite
Date: Fri, 24 Sep 2004 08:33:00 -0000 [thread overview]
Message-ID: <6832D6AE-0DF5-11D9-B012-000A95B1F520@apple.com> (raw)
In-Reply-To: <007a01c4a1de$78b66ed0$dc4e2a97@bagio>
[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]
On 23/09/2004, at 7:30 PM, Giovanni Bajo wrote:
> Geoffrey Keating wrote:
>
>> /* A structure representing 'attributes' on a DECL or TYPE node.
>> Each attribute has a NAME (an IDENTIFIER_NODE) and possibly a
>> VALUE. */
>> struct one_attribute GTY(())
>> {
>> tree name;
>> tree value;
>> };
>>
>> /* A counted list of attributes. */
>> struct attribute_list_s GTY(())
>> {
>> attribute_count n_attributes;
>> /* There are 16 bits free here. */
>> struct one_attribute GTY((length ("%h.n_attributes"))) attribs[1];
>> };
>
> Why not simply VEC(one_attribute) ?
VECs are much too much for what's needed here. They're expandable,
they can be used as a stack, all kinds of stuff (and all kinds of data)
that aren't necessary.
> Do you have some numbers on the speedup we get with this?
This is infrastructure for speedup patches, not a speedup patch itself.
In the compilations I time, only a very small proportion of functions
and types have any attributes, and most of those are builtin functions.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 2408 bytes --]
next prev parent reply other threads:[~2004-09-24 6:46 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 [this message]
2004-09-24 12:24 ` Nathan Sidwell
2004-09-24 22:29 ` 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=6832D6AE-0DF5-11D9-B012-000A95B1F520@apple.com \
--to=geoffk@apple.com \
--cc=gcc@gcc.gnu.org \
--cc=giovannibajo@libero.it \
/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).