From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: nathan@codesourcery.com
Cc: gcc@gcc.gnu.org
Subject: Re: [RFC] ignoring type alias conflicts between structures and scalars
Date: Thu, 25 Nov 2004 18:03:00 -0000 [thread overview]
Message-ID: <10411251752.AA07194@vlsi1.ultra.nyu.edu> (raw)
your example is different, in that the int lvalue is not some arbitrary
pointer dereference, but a known variable.
Yes, I think that's the key. The alias_sets_conflict_p routine was meant
originally for an RTL environment where every MEM was potentially a pointer
dereference (yes, we knew some of those that weren't, but didn't do much with
that knowlege). If you want to distinguish between pointers to a type and
variables of that type, you don't have to do the symmetric test.
next reply other threads:[~2004-11-25 17:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-25 18:03 Richard Kenner [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-25 21:02 Richard Kenner
2004-11-25 21:17 ` Diego Novillo
2004-11-25 17:48 Richard Kenner
2004-11-25 16:28 Richard Kenner
2004-11-25 16:53 ` Diego Novillo
2004-11-25 17:39 ` Daniel Berlin
2004-11-25 16:11 Richard Kenner
2004-11-25 16:02 Richard Kenner
2004-11-25 16:12 ` Diego Novillo
2004-11-25 16:28 ` Andrew Pinski
2004-11-25 15:38 Diego Novillo
2004-11-25 16:18 ` Daniel Berlin
2004-11-25 17:48 ` Nathan Sidwell
2004-11-25 18:03 ` Joseph S. Myers
2004-11-25 20:55 ` Jeffrey A Law
2004-11-25 20: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=10411251752.AA07194@vlsi1.ultra.nyu.edu \
--to=kenner@vlsi1.ultra.nyu.edu \
--cc=gcc@gcc.gnu.org \
--cc=nathan@codesourcery.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).