public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "daniel.kruegler at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/48771] New: [C++0x] is_literal_type incorrect for references to non-literal types
Date: Tue, 26 Apr 2011 13:50:00 -0000	[thread overview]
Message-ID: <bug-48771-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48771

           Summary: [C++0x] is_literal_type incorrect for references to
                    non-literal types
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: daniel.kruegler@googlemail.com


gcc 4.7.0 20110423 (experimental) in C++0x mode rejects the following code:

//-----------
#include <type_traits>

struct NonLiteral {
  NonLiteral();
  ~NonLiteral();
};

static_assert(std::is_literal_type<NonLiteral&>::value, "Error"); // #1
static_assert(std::is_literal_type<NonLiteral&&>::value, "Error"); // #2
//-----------

because both assertions fire. This code should be accepted, because as of the
FDIS all reference types are literal types (similar to pointers).


             reply	other threads:[~2011-04-26 13:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-26 13:50 daniel.kruegler at googlemail dot com [this message]
2011-04-26 14:10 ` [Bug c++/48771] " paolo.carlini at oracle dot com
2011-04-26 14:40 ` paolo.carlini at oracle dot com
2011-04-27  3:58 ` jason at gcc dot gnu.org
2011-04-27  9:01 ` paolo.carlini at oracle dot com
2011-04-28  9:23 ` paolo at gcc dot gnu.org
2011-04-28  9:25 ` paolo.carlini at oracle dot com
2011-04-28 15:57 ` rguenth at gcc dot gnu.org
2011-06-06 15:43 ` paolo.carlini at oracle dot com

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=bug-48771-4@http.gcc.gnu.org/bugzilla/ \
    --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).