From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: mszick@goquest.com
Cc: gcc@gcc.gnu.org
Subject: Re: [tree-ssa] Out of SSA status and issues
Date: Tue, 13 May 2003 15:23:00 -0000 [thread overview]
Message-ID: <10305131528.AA14941@vlsi1.ultra.nyu.edu> (raw)
Consider instead that '*p' is just the name given a register's
contents. Neither 'i' nor '9' are processor internal. Both are
external to the cpu. The memory reference for 'i' is source code
implicit, the memory reference for '*p' is source code explicit.
True, but given caching effects, it's hard to see how *p could be less
expensive than 'i'.
next reply other threads:[~2003-05-13 15:23 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 15:23 Richard Kenner [this message]
2003-05-13 18:50 ` Geoff Keating
2003-05-13 23:28 ` Michael S. Zick
2003-05-17 17:19 ` Michael S. Zick
-- strict thread matches above, loose matches on Subject: below --
2003-05-13 13:42 Richard Kenner
2003-05-13 13:17 Richard Kenner
2003-05-13 13:27 ` Diego Novillo
2003-05-13 13:40 ` Michael Matz
2003-05-13 15:08 ` Michael S. Zick
2003-05-12 14:42 Andrew MacLeod
2003-05-12 15:38 ` Diego Novillo
2003-05-12 15:57 ` Andrew MacLeod
2003-05-12 16:05 ` Michael Matz
2003-05-12 16:10 ` Andrew MacLeod
2003-05-12 16:16 ` law
2003-05-12 17:08 ` law
2003-05-12 17:12 ` Andrew MacLeod
2003-05-12 17:26 ` law
2003-05-12 18:57 ` Andrew MacLeod
2003-05-13 9:07 ` Michael Matz
2003-05-13 12:42 ` Diego Novillo
2003-05-13 12:50 ` Andrew MacLeod
2003-05-13 13:05 ` Diego Novillo
2003-05-13 13:29 ` Andrew MacLeod
2003-05-13 13:57 ` Diego Novillo
2003-05-13 12:57 ` Michael Matz
2003-05-13 13:11 ` Diego Novillo
2003-05-13 13:18 ` Andrew MacLeod
2003-05-14 17:19 ` Jan Vroonhof
2003-05-14 18:05 ` Andrew MacLeod
2003-05-14 18:33 ` Diego Novillo
2003-05-14 19:11 ` Daniel Berlin
2003-05-13 15:01 ` Daniel Berlin
2003-05-13 12:33 ` Diego Novillo
2003-05-13 12:49 ` Andrew MacLeod
2003-05-13 12:58 ` Diego Novillo
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=10305131528.AA14941@vlsi1.ultra.nyu.edu \
--to=kenner@vlsi1.ultra.nyu.edu \
--cc=gcc@gcc.gnu.org \
--cc=mszick@goquest.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).