From: Steven Bosscher <stevenb.gcc@gmail.com>
To: Jeff Law <law@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: Improve uncprop and coalescing
Date: Fri, 07 Jun 2013 08:30:00 -0000 [thread overview]
Message-ID: <CABu31nOz-SwoGF1oJNe=5pXUpyCAUe8j10YmTCXvCRtKM1WvVA@mail.gmail.com> (raw)
In-Reply-To: <51B178BA.1000802@redhat.com>
On Fri, Jun 7, 2013 at 8:07 AM, Jeff Law wrote:
> Rather than using strict pointer equality, we can do better by looking at
> TYPE_CANONICAL when it's available. Thus objects of the following two types
> (T1 & T2) become candidates for coalescing if they are tied together by a
> copy or PHI node.
>
> typedef int t1;
> typedef int t2;
>
>
> This typically eliminates necessary copies and constant initializations,
> which is good.
Hmm... Can't you use types_compatible_p?
Ciao!
Steven
next prev parent reply other threads:[~2013-06-07 8:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 6:08 Jeff Law
2013-06-07 8:30 ` Steven Bosscher [this message]
2013-06-07 12:50 ` Jeff Law
2013-06-07 9:14 ` Richard Biener
2013-06-12 4:44 ` Jeff Law
2013-06-12 16:04 ` Jeff Law
2013-08-30 10:06 ` Richard Biener
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='CABu31nOz-SwoGF1oJNe=5pXUpyCAUe8j10YmTCXvCRtKM1WvVA@mail.gmail.com' \
--to=stevenb.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--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).