http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46698
Summary: internal compiler error: in
build_data_member_initialization, at
cp/semantics.c:5503
Product: gcc
Version: 4.6.0
Status: RESOLVED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassig...@gcc.gnu.org
ReportedBy: mi...@gnu.org
miles at gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |DUPLICATE
I don't know if this is the same as the other ICEs in
build_data_member_initialization, but it's at a different line number anyway...
Compiler version is:
g++ (Debian 20101128-1) 4.6.0 20101128 (experimental) [trunk revision 167220]
Here's the un-preprocessed source (preprocessed source attached):
#include <string>
#include <map>
void f (const std::string &name, const std::string &val)
{
std::map<const std::string, std::string>::value_type (name, val);
}
Compiled with:
g++-snapshot -c -std=c++0x ,oink.cc
yields:
In file included from
/usr/lib/gcc-snapshot/lib/gcc/x86_64-linux-gnu/4.6.0/../../../../include/c++/4.6.0/bits/stl_algobase.h:65:0,
from
/usr/lib/gcc-snapshot/lib/gcc/x86_64-linux-gnu/4.6.0/../../../../include/c++/4.6.0/bits/char_traits.h:41,
from
/usr/lib/gcc-snapshot/lib/gcc/x86_64-linux-gnu/4.6.0/../../../../include/c++/4.6.0/string:42,
from ,oink.cc:1:
/usr/lib/gcc-snapshot/lib/gcc/x86_64-linux-gnu/4.6.0/../../../../include/c++/4.6.0/bits/stl_pair.h:
In constructor 'constexpr std::pair<_T1, _T2>::pair(const _T1&, const _T2&)
[with _T1 = const std::basic_string<char>, _T2 = std::basic_string<char>]':
,oink.cc:6:66: instantiated from here
/usr/lib/gcc-snapshot/lib/gcc/x86_64-linux-gnu/4.6.0/../../../../include/c++/4.6.0/bits/stl_pair.h:102:35:
internal compiler error: in build_data_member_initialization, at
cp/semantics.c:5503
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-snapshot/README.Bugs> for instructions.
Thanks,
-miles
--- Comment #1 from miles at gnu dot org 2010-11-29 05:14:53 UTC ---
(I accidentally filed the same bug multiple times, so I'm marking all but one
as duplicates)
*** This bug has been marked as a duplicate of bug 46701 ***
