From: Diego Novillo <dnovillo@redhat.com>
To: Geoff Keating <geoffk@geoffk.org>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: [RFC] Tightening up the type system
Date: Thu, 30 Sep 2004 22:38:00 -0000 [thread overview]
Message-ID: <1096574542.16899.80.camel@localhost.localdomain> (raw)
In-Reply-To: <m2oejnpm0m.fsf@greed.local>
On Thu, 2004-09-30 at 15:58, Geoffrey Keating wrote:
> Diego Novillo <dnovillo@redhat.com> writes:
>
> > In fact, I would like to get to the point where we can simply call
> > 'gcc_assert (lang_hook.compatible_types_p (dest, orig))' when doing
> > propagation. Ideally, all the necessary type conversions should be
> > exposed in the IL.
>
> Should the validity of GIMPLE really depend on a language hook like
> this? Surely it would make more sense to have a
> gimple_compatible_types_p that reflects what code that parses GIMPLE
> can actually handle (presumably a superset of what each language can
> generate).
>
Perhaps. Today I was thinking something along the lines of using
alias_sets_conflict_p() as our type compatibility test, instead. That
would loosen the restrictions and allow mixing things like const type *
and type *.
Right now, we have a hybrid model where we try to remove "useless" type
conversions, but then validate propagation opportunities using
compatible_types_p.
Diego.
next prev parent reply other threads:[~2004-09-30 20:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 17:08 Diego Novillo
2004-09-28 17:59 ` Andrew Haley
2004-09-28 18:07 ` Diego Novillo
2004-09-28 18:37 ` Andrew Haley
2004-09-28 22:46 ` Tom Tromey
2004-09-30 18:43 ` Diego Novillo
2004-09-28 19:30 ` Jan Hubicka
2004-09-28 20:30 ` Nathan Sidwell
2004-09-30 21:02 ` Geoffrey Keating
2004-09-30 21:23 ` Geoffrey Keating
2004-09-30 22:38 ` Diego Novillo [this message]
2004-09-28 17:16 Richard Kenner
2004-09-28 20:59 Richard Kenner
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=1096574542.16899.80.camel@localhost.localdomain \
--to=dnovillo@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=geoffk@geoffk.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).