From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: aph@redhat.com
Cc: gcc@gcc.gnu.org
Subject: Re: [RFC] Tightening up the type system
Date: Tue, 28 Sep 2004 20:59:00 -0000 [thread overview]
Message-ID: <10409281811.AA26707@vlsi1.ultra.nyu.edu> (raw)
It's an interesting view. I'm pretty sure that we violate this is the
Java FE in a few places, but perhaps we shouldn't. The trouble is
that the GENERIC type system has never been so well-defined.
That's true, however, I've always treated GENERIC's type system as
being very strict: the types must *exactly* agree. Certainly the Ada
front end goes to a lot of trouble to make that happen in the trees it
generates. I think there has been some code that assumes
type-correctness, but not much.
In GIMPLE, we relax this to allow any types that are type_compatible_p.
I'm sure that enforcing this would break things and it would take some
time to find and fix them all.
On the other hand, *not* enforcing this looks like it's causing problems
for the optimizers. Those problems are going to be harder to find and
fix than typing violations in the front end.
next reply other threads:[~2004-09-28 18:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 20:59 Richard Kenner [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-28 17:16 Richard Kenner
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
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=10409281811.AA26707@vlsi1.ultra.nyu.edu \
--to=kenner@vlsi1.ultra.nyu.edu \
--cc=aph@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).