public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bkoz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/46203] New: constexpr weirdness w/ default ctors
Date: Wed, 27 Oct 2010 21:30:00 -0000 [thread overview]
Message-ID: <bug-46203-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46203
Summary: constexpr weirdness w/ default ctors
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: bkoz@gcc.gnu.org
From trunk, get these additional fails.
FAIL: 23_containers/vector/ext_pointer/citerators.cc (test for excess errors)
FAIL: 29_atomics/atomic_address/cons/assign_neg.cc (test for excess errors)
FAIL: 29_atomics/atomic_address/cons/copy_neg.cc (test for excess errors)
FAIL: 29_atomics/atomic_address/cons/default.cc (test for excess errors)
FAIL: 29_atomics/atomic_flag/cons/assign_neg.cc (test for excess errors)
FAIL: 29_atomics/atomic_flag/cons/copy_neg.cc (test for excess errors)
FAIL: 29_atomics/atomic_flag/cons/default.cc (test for excess errors)
=== libstdc++ Summary ===
# of expected passes 7977
# of unexpected failures 7
# of expected failures 84
# of unsupported tests 100
Looking at
FAIL: 29_atomics/atomic_address/cons/default.cc,
I see:
In file included from
/mnt/share/bld/gcc.git-trunk/x86_64-unknown-linux-gnu/libstdc++-v3/include/atomic:42:0,
from
/mnt/share/src/gcc.git-trunk/libstdc++-v3/testsuite/29_atomics/atomic_flag/cons/default.cc:20:
/mnt/share/bld/gcc.git-trunk/x86_64-unknown-linux-gnu/libstdc++-v3/include/bits/atomic_base.h:
In constructor ‘constexpr std::__atomic_flag_base::__atomic_flag_base()’:
/mnt/share/bld/gcc.git-trunk/x86_64-unknown-linux-gnu/libstdc++-v3/include/bits/atomic_base.h:58:18:
error: uninitialized member ‘std::__atomic_flag_base::_M_i’ in ‘constexpr’
constructor
In file included from
/mnt/share/bld/gcc.git-trunk/x86_64-unknown-linux-gnu/libstdc++-v3/include/atomic:81:0,
from
/mnt/share/src/gcc.git-trunk/libstdc++-v3/testsuite/29_atomics/atomic_flag/cons/default.cc:20:
/mnt/share/bld/gcc.git-trunk/x86_64-unknown-linux-gnu/libstdc++-v3/include/bits/atomic_2.h:
In constructor ‘constexpr std::__atomic2::atomic_flag::atomic_flag()’:
/mnt/share/bld/gcc.git-trunk/x86_64-unknown-linux-gnu/libstdc++-v3/include/bits/atomic_2.h:49:5:
note: synthesized method ‘std::__atomic_flag_base::__atomic_flag_base()’ first
required here
/mnt/share/src/gcc.git-trunk/libstdc++-v3/testsuite/29_atomics/atomic_flag/cons/default.cc:
In function ‘int main()’:
/mnt/share/src/gcc.git-trunk/libstdc++-v3/testsuite/29_atomics/atomic_flag/cons/default.cc:25:44:
note: synthesized method ‘constexpr std::__atomic2::atomic_flag::atomic_flag()’
first required here
These default ctors are not constexpr.
next reply other threads:[~2010-10-27 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 21:30 bkoz at gcc dot gnu.org [this message]
2010-10-27 21:30 ` [Bug c++/46203] " bkoz at gcc dot gnu.org
2010-10-28 17:46 ` bkoz at gcc dot gnu.org
2010-11-01 16:45 ` jason 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-46203-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).