public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/64989] New: constant-initialization of self-referencing array
Date: Mon, 09 Feb 2015 20:24:00 -0000	[thread overview]
Message-ID: <bug-64989-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64989

            Bug ID: 64989
           Summary: constant-initialization of self-referencing array
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Keywords: wrong-code
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jason at gcc dot gnu.org
                CC: jakub at gcc dot gnu.org, jason at gcc dot gnu.org,
                    wolfgang.roehrl@gi-de.com
        Depends on: 64899

+++ This bug was initially created as a clone of Bug #64899 +++

The testcase in bug 64899 works now, but this one still doesn't.

struct S
{
  void *p;
  constexpr S (): p(this) {}
};

constexpr S sa[2];
#define SA(X) static_assert((X),#X)
SA(sa[1].p == &sa[1]);


             reply	other threads:[~2015-02-09 20:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-09 20:24 jason at gcc dot gnu.org [this message]
2015-02-09 20:25 ` [Bug c++/64989] " jason at gcc dot gnu.org
2015-03-18 20:07 ` paolo.carlini at oracle dot com
2015-07-25  6:55 ` jason at gcc dot gnu.org
2015-07-25  7:13 ` jason at gcc dot gnu.org
2021-12-07 12:27 ` pinskia at gcc dot gnu.org
2021-12-09  3:06 ` pinskia at gcc dot gnu.org
2021-12-14 16:25 ` pinskia at gcc dot gnu.org
2021-12-14 16:27 ` pinskia at gcc dot gnu.org
2022-10-27  2:40 ` pinskia 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=bug-64989-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).