public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: dnovillo@redhat.com
Cc: gcc@gcc.gnu.org
Subject: Re:  [RFC] ignoring type alias conflicts between structures and scalars
Date: Thu, 25 Nov 2004 17:48:00 -0000	[thread overview]
Message-ID: <10411251745.AA06923@vlsi1.ultra.nyu.edu> (raw)

    So, what I want to teach the alias analyzer is that given a pointer to
    an aggregate type A and a regular variable of a scalar type S, such that
    A and S are not type-compatible, then a pointer to 'A' cannot possibly
    point to a variable of type 'S'.

    So, it boils down to alias_sets_conflict_p being symmetric.  We want to
    consider 'int * -> struct int_float_s' to alias, but we want to reject
    'struct int_float_s * -> int'.

Right.  I think it's just a matter of writing a version of
alias_sets_conflict_p with the second block of code that checks children
removed, leaving just the checks for set 0, the same alias set, and the first
being a subset of the second.  Then call that routine.

It might be worth checking if other places should be using that new routine.
It looks like the usage in gimplify.c and perhaps tree-data-ref.c should as
well.

             reply	other threads:[~2004-11-25 17:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-25 17:48 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 18:03 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=10411251745.AA06923@vlsi1.ultra.nyu.edu \
    --to=kenner@vlsi1.ultra.nyu.edu \
    --cc=dnovillo@redhat.com \
    --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).