From: Richard Henderson <rth@redhat.com>
To: Jan Hubicka <hubicka@ucw.cz>
Cc: gcc@gcc.gnu.org, law@redhat.com
Subject: Re: tree-SSA and indirect references.
Date: Tue, 20 Jan 2004 00:59:00 -0000 [thread overview]
Message-ID: <20040120005924.GA3079@redhat.com> (raw)
In-Reply-To: <20040120003156.GE8495@atrey.karlin.mff.cuni.cz>
On Tue, Jan 20, 2004 at 01:31:56AM +0100, Jan Hubicka wrote:
> vara=(type *)&varb;
> varc=*vara;
>
> this is common for small aggregate casts that can stay in registers
> after compiling. What is our strategy to deal with this?
I don't know. I think it depends what the set of all these types are.
r~
next prev parent reply other threads:[~2004-01-20 0:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 0:31 Jan Hubicka
2004-01-20 0:59 ` Richard Henderson [this message]
2004-01-20 9:50 ` Jan Hubicka
2004-01-20 10:21 ` Richard Henderson
2004-01-20 14:25 ` Jan Hubicka
2004-01-20 16:57 ` Andrew Pinski
2004-01-20 18:15 ` Richard Henderson
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=20040120005924.GA3079@redhat.com \
--to=rth@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=law@redhat.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).