public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/38913] Fortran does not set TYPE_CANONICAL properly
Date: Thu, 04 Jun 2009 12:52:00 -0000 [thread overview]
Message-ID: <20090604125156.31362.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38913-10053@http.gcc.gnu.org/bugzilla/>
------- Comment #11 from burnus at gcc dot gnu dot org 2009-06-04 12:51 -------
(In reply to comment #10)
> That hack is already gone ... ;)
The truck hack yes, the question is whether one can also do something about the
following? Or is this a wider problem?
/* ??? Array types are not properly unified in all cases as we have
spurious changes in the index types for example. Removing this
causes all sorts of problems with the Fortran frontend. */
if (TREE_CODE (type1) == ARRAY_TYPE
&& TREE_CODE (type2) == ARRAY_TYPE)
return -1;
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38913
next prev parent reply other threads:[~2009-06-04 12:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-19 15:37 [Bug fortran/38913] New: " rguenth at gcc dot gnu dot org
2009-01-19 16:23 ` [Bug fortran/38913] " rguenth at gcc dot gnu dot org
2009-01-21 20:22 ` pault at gcc dot gnu dot org
2009-01-21 20:50 ` rguenth at gcc dot gnu dot org
2009-01-25 15:25 ` dfranke at gcc dot gnu dot org
2009-02-06 13:45 ` pault at gcc dot gnu dot org
2009-02-07 15:33 ` jv244 at cam dot ac dot uk
2009-02-07 18:50 ` rguenther at suse dot de
2009-06-04 10:55 ` rguenth at gcc dot gnu dot org
2009-06-04 11:47 ` burnus at gcc dot gnu dot org
2009-06-04 11:49 ` rguenther at suse dot de
2009-06-04 12:52 ` burnus at gcc dot gnu dot org [this message]
2009-06-04 13:39 ` rguenther at suse dot de
2009-06-28 16:56 ` rguenth at gcc dot gnu dot org
2009-06-28 20:44 ` rguenth at gcc dot gnu dot org
2009-08-03 10:11 ` jv244 at cam dot ac dot uk
2009-09-22 15:45 ` rguenth at gcc dot gnu dot org
2009-10-11 12:49 ` jv244 at cam dot ac dot uk
2009-12-09 11:50 ` jv244 at cam dot ac dot uk
2010-06-09 22:11 ` fxcoudert at gcc dot gnu dot org
2010-07-24 18:12 ` jv244 at cam dot ac dot uk
[not found] <bug-38913-4@http.gcc.gnu.org/bugzilla/>
2010-12-30 17:32 ` tkoenig at gcc dot gnu.org
2011-07-24 18:47 ` dfranke at gcc dot gnu.org
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=20090604125156.31362.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).