public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "JamesMikeDuPont at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/67155] New: Linking of complex constexpr static class member failing across files
Date: Sat, 08 Aug 2015 03:06:00 -0000	[thread overview]
Message-ID: <bug-67155-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 67155
           Summary: Linking of complex constexpr static class member
                    failing across files
           Product: gcc
           Version: 5.2.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: JamesMikeDuPont at googlemail dot com
  Target Milestone: ---

Created attachment 36148
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36148&action=edit
test case

I encountered a strange behavior when creating a class that wraps a constexpr
string.

It seems that the static constant string field wrapped in a class is only
accessible in the same header file and not available in a separate compilation
unit. 

The workaround is to move the usage of the static fields into the header.

If you prefer git you can find the test case here as well :
https://github.com/h4ck3rm1k3/gcc-plugin-cpp-template/tree/constexpr/testcase


             reply	other threads:[~2015-08-08  3:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-08  3:06 JamesMikeDuPont at googlemail dot com [this message]
2015-08-08  3:08 ` [Bug c++/67155] " JamesMikeDuPont at googlemail dot com
2015-08-08  4:00 ` JamesMikeDuPont at googlemail dot com
2015-08-08  4:10 ` JamesMikeDuPont at googlemail dot com
2015-08-08  6:07 ` trippels at gcc dot gnu.org
2015-08-08  8:06 ` redi 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-67155-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).