public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "morpheby at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/54126] New: ICE on constexpr move ctor with const ref type instead of error
Date: Mon, 30 Jul 2012 14:17:00 -0000 [thread overview]
Message-ID: <bug-54126-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54126
Bug #: 54126
Summary: ICE on constexpr move ctor with const ref type instead
of error
Classification: Unclassified
Product: gcc
Version: 4.7.2
Status: UNCONFIRMED
Severity: minor
Priority: P3
Component: c++
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: morpheby@gmail.com
Compiling attached source fails with ICE:
$ gcc -std=c++11 gcc-bug.cpp --save-temps
gcc-bug.cpp: In instantiation of 'constexpr ClassA<T1>::ClassA(U1&&) [with U1 =
int; T1 = const ClassB&]':
gcc-bug.cpp:34:3: required from here
gcc-bug.cpp:22:12: internal compiler error: in
build_data_member_initialization,
at cp/semantics.c:5790
GCC version dump: $ gcc -v
Using built-in specs.
COLLECT_GCC=C:\MinGW\bin\gcc.exe
COLLECT_LTO_WRAPPER=c:/mingw/bin/../libexec/gcc/i686-w64-mingw32/4.7.2/lto-wrapp
er.exe
Target: i686-w64-mingw32
Configured with: ../..//mingw-src/gcc-4_7-branch/configure
--host=i686-w64-mingw
32 --build=i686-w64-mingw32 --target=i686-w64-mingw32
--prefix=/mingw-gcc-4_7-br
anch-x32 --with-sysroot=/mingw-gcc-4_7-branch-x32 --enable-shared
--enable-stati
c --enable-targets=all --enable-multilib --enable-languages=c,c++,fortran,lto
--
enable-libstdcxx-time=yes --enable-threads=posix --enable-libgomp --enable-lto
-
-enable-graphite --enable-cloog-backend=isl --enable-checking=release
--enable-f
ully-dynamic-string --enable-version-specific-runtime-libs
--enable-sjlj-excepti
ons --disable-ppl-version-check --disable-cloog-version-check
--disable-libstdcx
x-pch --disable-libstdcxx-debug --disable-bootstrap --disable-rpath
--disable-wi
n32-registry --disable-nls --disable-werror --disable-symvers --with-gnu-ld
--wi
th-tune=generic --with-host-libstdcxx='-static -lstdc++' --with-libiconv
--with-
gmp=/mingw-gcc-4_7-branch-libs-x32 --with-mpfr=/mingw-gcc-4_7-branch-libs-x32
--
with-mpc=/mingw-gcc-4_7-branch-libs-x32
--with-ppl=/mingw-gcc-4_7-branch-libs-x3
2 --with-cloog=/mingw-gcc-4_7-branch-libs-x32 --with-pkgversion='MinGW-builds:
h
ttp://sourceforge.net/projects/mingwbuilds/'
--with-bugurl=http://sourceforge.ne
t/projects/mingwbuilds/ CFLAGS='-O2 -pipe -fomit-frame-pointer
-momit-leaf-frame
-pointer -I/mingw-gcc-4_7-branch-libs-x32/include' CXXFLAGS='-O2 -pipe
-fomit-fr
ame-pointer -momit-leaf-frame-pointer' CPPFLAGS= LDFLAGS='-pipe -s
-L/mingw-gcc-
4_7-branch-libs-x32/lib -L/mingw-gcc-4_7-branch-x32/bin'
Thread model: posix
gcc version 4.7.2 20120727 (prerelease) (MinGW-builds:
http://sourceforge.net/pr
ojects/mingwbuilds/)
next reply other threads:[~2012-07-30 14:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-30 14:17 morpheby at gmail dot com [this message]
2012-07-30 14:22 ` [Bug c++/54126] " redi at gcc dot gnu.org
2012-07-30 14:33 ` morpheby at gmail dot com
2012-07-30 14:53 ` redi at gcc dot gnu.org
2012-07-30 14:56 ` morpheby at gmail dot com
2013-02-13 7:29 ` freddie_chopin at op dot pl
2013-02-13 12:20 ` morpheby at gmail dot com
2014-08-29 13:27 ` 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-54126-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).