From: "Doug Gregor" <doug.gregor@gmail.com>
To: "Richard Guenther" <richard.guenther@gmail.com>
Cc: "Jakub Jelinek" <jakub@redhat.com>,
"H.J. Lu" <hjl.tools@gmail.com>,
"Paolo Bonzini" <bonzini@gnu.org>,
"GCC Patches" <gcc-patches@gcc.gnu.org>
Subject: Re: [C/C++/ObjC/ObjC++ PATCH] Battle of the comptypes (PR c++/35049)
Date: Thu, 07 Feb 2008 15:57:00 -0000 [thread overview]
Message-ID: <24b520d20802070747s2680361l38bf6e256a81452c@mail.gmail.com> (raw)
In-Reply-To: <84fc9c000802070711g1717654m63694c4110d5641@mail.gmail.com>
On Feb 7, 2008 10:11 AM, Richard Guenther <richard.guenther@gmail.com> wrote:
> But now it ICEs for me again...
>
> /space/rguenther/src/svn/trunk/gcc/testsuite/g++.dg/ext/vector13.C:6:
> internal compiler error: canonical types differ for identical types
> const int __vector__ [] and const int __vector__ []^M
> Please submit a full bug report,^M
> with preprocessed source if appropriate.^M
> See <http://gcc.gnu.org/bugs.html> for instructions.^M
>
> FAIL: g++.dg/ext/vector13.C (internal compiler error)
> FAIL: g++.dg/ext/vector13.C (test for excess errors)
I'm seeing this on i686-pc-linux-gnu, but not i386-apple-darwin9. This
looks like a typical canonical-types failure, where we have two
equivalent ARRAY_TYPE nodes whose canonical types are different. I'm
looking into it.
The issue is independent of the issue with comptypes, and I happen to
like Paolo's patch better than my own. Despite its size, it's a far
cleaner approach.
- Doug
next prev parent reply other threads:[~2008-02-07 15:47 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 17:53 [C++ " Doug Gregor
2008-02-06 15:51 ` H.J. Lu
2008-02-06 15:59 ` Doug Gregor
2008-02-06 16:48 ` H.J. Lu
2008-02-06 22:51 ` Andreas Tobler
2008-02-06 22:55 ` Manuel López-Ibáñez
2008-02-06 23:16 ` Andrew Pinski
2008-02-07 8:59 ` Paolo Bonzini
2008-02-07 13:46 ` [C/C++/ObjC/ObjC++ " Paolo Bonzini
2008-02-07 13:52 ` H.J. Lu
2008-02-07 14:59 ` Paolo Bonzini
2008-02-07 15:05 ` H.J. Lu
2008-02-07 15:07 ` Jakub Jelinek
2008-02-07 15:47 ` Richard Guenther
2008-02-07 15:57 ` Doug Gregor [this message]
2008-02-07 16:22 ` Paolo Bonzini
2008-02-07 15:07 ` Doug Gregor
2008-02-11 4:58 ` Mark Mitchell
2008-02-11 12:23 ` Joseph S. Myers
2008-02-11 13:33 ` Paolo Bonzini
2008-02-07 20:49 ` [C++ " Joseph S. Myers
2008-02-08 10:42 ` Paolo Bonzini
2008-02-08 15:49 ` Joseph S. Myers
2008-02-08 15:59 ` Doug Gregor
2008-02-08 16:37 ` Paolo Bonzini
2008-02-08 20:02 ` Joseph S. Myers
2008-02-07 18:54 ` Andreas Krebbel
2008-02-07 19:06 ` Doug Gregor
2008-02-11 13:40 [C/C++/ObjC/ObjC++ " Uros Bizjak
2008-02-11 13:58 ` Paolo Bonzini
2008-02-11 20:02 ` Doug Gregor
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=24b520d20802070747s2680361l38bf6e256a81452c@mail.gmail.com \
--to=doug.gregor@gmail.com \
--cc=bonzini@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=jakub@redhat.com \
--cc=richard.guenther@gmail.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).