From: Geoffrey Keating <geoffk@apple.com>
To: gcc list <gcc@gcc.gnu.org>
Cc: Zem Laski <zlaski@apple.com>
Subject: objc data structure design
Date: Tue, 23 Nov 2004 19:34:00 -0000 [thread overview]
Message-ID: <117D8646-3D82-11D9-827E-000A95B1F520@apple.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1957 bytes --]
Following discussion with Zem, we've agreed that the objc data
structure design will proceed as follows:
Zem will take this patch:
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(())
(with comments and possibly field names improved), and determine what
impact it has on C and C++ compile time, and C and C++ PCH size. For
C++, he'll use our Finder_FE benchmark for both time and PCH size, for
C I suggest that the PCH be one that just contains
#include <Carbon/Carbon.h>
on Darwin, and use some reasonable and convenient benchmark for time.
If these results show that there's not significant degradation, that is
less than 1% for compile speed and increase in PCH size, then this
should solve his problem and let him proceed with the objc data
structure changes. If there is significant degradation, we'll look at
making these fields be inserted only when they're actually needed.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 2408 bytes --]
next reply other threads:[~2004-11-23 19:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 19:34 Geoffrey Keating [this message]
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
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=117D8646-3D82-11D9-827E-000A95B1F520@apple.com \
--to=geoffk@apple.com \
--cc=gcc@gcc.gnu.org \
--cc=zlaski@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).