From: Ziemowit Laski <zlaski@apple.com>
To: gcc list <gcc@gcc.gnu.org>
Subject: Re: objc data structure design
Date: Tue, 07 Dec 2004 01:45:00 -0000 [thread overview]
Message-ID: <6578A4A7-47F1-11D9-9362-000D9330C50E@apple.com> (raw)
In-Reply-To: <E290E272-45B4-11D9-BEA3-00039390FFE2@apple.com>
And here are the C numbers:
Without patch:
20041206 usr SimpleText_COMPILATION 34.52(0.05)
20041206 usr SimpleText_SIZE 150972
-rw-rw-r-- 1 zlaski admin 18494852 Dec 6 17:21 c
With patch:
20041206 usr SimpleText_COMPILATION 34.68(0.35)
20041206 usr SimpleText_SIZE 150972
-rw-rw-r-- 1 zlaski admin 18494852 Dec 6 17:35 c
(The PCH was constructed separately from a header containing just
'#include <Carbon/Carbon.h>'.)
So, we have a 0.5% compile-time regression, with no increase in PCH.
Since all these numbers are below the 1% threshhold, I shall offer the
patch below on gcc-patches shortly.
--Zem
On 3 Dec 2004, at 21.25, Ziemowit Laski wrote:
> OK, I finally managed to get the C++ numbers Geoff requested; sorry it
> took so long.
>
> Without patch:
> 20041203 usr FinderFE_COMPILATION 895.07(1.63)
> 20041203 usr FinderFE_SIZE 73695552
> PCH: -rw-rw-r-- 1 zlaski admin 46080420 Dec 3 15:25 c++
>
> With patch:
> 20041203 usr FinderFE_COMPILATION 897.43(9.76)
> 20041203 usr FinderFE_SIZE 73695552
> PCH: -rw-rw-r-- 1 zlaski admin 46080420 Dec 3 18:01 c++
>
> So, compile time regressed by 0.3%, with no increase in PCH size.
> This was done
> on a 500 MHz G4 Power Mac, should anyone care.
>
> I shall now do the C measurements. Stay tuned.
>
> --Zem
>
>> Index: c-tree.h
>> ===================================================================
>> RCS file: /cvs/gcc/gcc/gcc/c-tree.h,v
>> retrieving revision 1.187
>> diff -u -p -u -p -r1.187 c-tree.h
>> --- c-tree.h 11 Nov 2004 23:13:10 -0000 1.187
>> +++ c-tree.h 23 Nov 2004 18:54:26 -0000
>> @@ -73,6 +73,8 @@ struct lang_type GTY(())
>> /* In an ENUMERAL_TYPE, the min and max values. */
>> tree enum_min;
>> tree enum_max;
>> + /* In a RECORD_TYPE, <insert proper comment here>. */
>> + tree objc_protocol;
>> };
>>
>> /* Record whether a type or decl was written with nonconstant size.
>> Index: cp/cp-tree.h
>> ===================================================================
>> RCS file: /cvs/gcc/gcc/gcc/cp/cp-tree.h,v
>> retrieving revision 1.1070
>> diff -u -p -u -p -r1.1070 cp-tree.h
>> --- cp/cp-tree.h 10 Nov 2004 17:34:47 -0000 1.1070
>> +++ cp/cp-tree.h 23 Nov 2004 18:54:28 -0000
>> @@ -1060,6 +1060,9 @@ struct lang_type_class GTY(())
>> tree decl_list;
>> tree template_info;
>> tree befriending_classes;
>> +
>> + /* <insert proper comment here>. */
>> + tree objc_protocol;
>> };
>>
>> struct lang_type_ptrmem GTY(())
>
prev parent reply other threads:[~2004-12-07 1:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 19:34 Geoffrey Keating
2004-11-23 23:00 ` Ziemowit Laski
2004-11-24 16:12 ` Nathan Sidwell
2004-12-04 5:25 ` Ziemowit Laski
2004-12-07 1:45 ` Ziemowit Laski [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=6578A4A7-47F1-11D9-9362-000D9330C50E@apple.com \
--to=zlaski@apple.com \
--cc=gcc@gcc.gnu.org \
/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).