From: Devang Patel <dpatel@apple.com>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: gcc@gcc.gnu.org
Subject: Re: TREE_CODE mania
Date: Wed, 04 Sep 2002 19:51:00 -0000 [thread overview]
Message-ID: <6A24C554-C07A-11D6-9975-00039362EF82@apple.com> (raw)
In-Reply-To: <A26C8A14-C05A-11D6-AF92-000393575BCC@dberlin.org>
[-- Attachment #1: Type: text/plain, Size: 716 bytes --]
On Wednesday, September 4, 2002, at 04:04 PM, Daniel Berlin wrote:
>>
>> Sure, we can try using different allocation schemes to achieve better
>> compile
>> time performance. But this approach is like -- earn more money and
>> allocate
>> funds in better way to meet the budget. I am thinking in terms, can
>> we reduce
>> expenditure ?
>
> By the by, did you mark the TREE_CODE_read function as const/pure (i'm
> not sure tree_code's aren't modified in place, if they are, it's both,
> if they aren't, it's at least one of them), so that it accurately
> simulates the macro in terms of actual accesses?
>
Well, TREE_CODE_read() name is misleading. It is recording read as well
as write accesses.
-Devang
[-- Attachment #2: Type: text/enriched, Size: 726 bytes --]
On Wednesday, September 4, 2002, at 04:04 PM, Daniel Berlin wrote:
<excerpt><excerpt>
Sure, we can try using different allocation schemes to achieve better
compile
time performance. But this approach is like -- earn more money and
allocate
funds in better way to meet the budget. I am thinking in terms, can we
reduce
expenditure ?
</excerpt>
By the by, did you mark the TREE_CODE_read function as const/pure (i'm
not sure tree_code's aren't modified in place, if they are, it's both,
if they aren't, it's at least one of them), so that it accurately
simulates the macro in terms of actual accesses?
</excerpt>
Well, TREE_CODE_read() name is misleading. It is recording read as
well as write accesses.
-Devang
next prev parent reply other threads:[~2002-09-05 2:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-03 20:18 Devang Patel
2002-09-03 20:50 ` Daniel Berlin
2002-09-04 10:19 ` Devang Patel
2002-09-04 16:04 ` Daniel Berlin
2002-09-04 19:51 ` Devang Patel [this message]
2002-09-04 10:23 ` Devang Patel
2002-09-04 1:51 ` Neil Booth
2002-09-04 10:15 ` Devang Patel
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=6A24C554-C07A-11D6-9975-00039362EF82@apple.com \
--to=dpatel@apple.com \
--cc=dberlin@dberlin.org \
--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).