From: Jason Merrill <jason@redhat.com>
To: Marc Glisse <marc.glisse@inria.fr>, gcc-patches@gcc.gnu.org
Subject: Re: PR54442 build_qualified_type produces a non-canonical type
Date: Mon, 09 Jun 2014 14:24:00 -0000 [thread overview]
Message-ID: <5395C387.1010506@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1406091604020.13093@stedding.saclay.inria.fr>
On 06/09/2014 10:18 AM, Marc Glisse wrote:
> I doubt the patch can be wrong, but it may be that this is a situation
> that is not supposed to happen and should be fixed elsewhere?
Seems likely. What is the difference between the type returned from
build_qualified_type (TYPE_CANONICAL and it's TYPE_CANONICAL? I would
expect them to be the same.
Jason
next prev parent reply other threads:[~2014-06-09 14:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 14:18 Marc Glisse
2014-06-09 14:24 ` Jason Merrill [this message]
2014-06-09 14:32 ` Marc Glisse
2014-06-09 14:46 ` Jason Merrill
2015-01-13 19:01 ` Paolo Carlini
2015-01-13 21:25 ` Jason Merrill
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=5395C387.1010506@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=marc.glisse@inria.fr \
/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).