From: Jason Merrill <jason@redhat.com>
To: Paolo Carlini <paolo.carlini@oracle.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [C++ Patch] PR 52487
Date: Tue, 20 Mar 2012 19:22:00 -0000 [thread overview]
Message-ID: <4F68D900.2000604@redhat.com> (raw)
In-Reply-To: <4F689E3A.20805@oracle.com>
That assert is there to make sure that we don't try to test for
literality of an incomplete type. We should check for completeness
before trying to check for literality.
Jason
next prev parent reply other threads:[~2012-03-20 19:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 15:15 Paolo Carlini
2012-03-20 19:22 ` Jason Merrill [this message]
2012-03-20 20:17 ` Paolo Carlini
2012-03-20 20:38 ` Paolo Carlini
2012-03-22 14:49 ` Jason Merrill
2012-03-22 17:01 ` Paolo Carlini
2012-03-22 17:16 ` Gabriel Dos Reis
2012-03-22 18:29 ` Jason Merrill
2012-03-23 1:02 ` Paolo Carlini
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=4F68D900.2000604@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=paolo.carlini@oracle.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).