This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/35566] New: multiset constructor uses insert_unique instead of insert_equal!
- From: "dennis dot czeremin at smiths-heimann dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 13 Mar 2008 10:46:58 -0000
- Subject: [Bug c++/35566] New: multiset constructor uses insert_unique instead of insert_equal!
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
Using the constructor of a multimap with 2 input iterators does not insert
multible keys any longer (gcc-4.2.3 had done it)
fix: Replace insert_unique with insert_equal in
/usr/local/gcc-4.3.0/include/c++/4.3.0/bits/stl_multimap.h:
190- * @param first An input iterator.
191- * @param last An input iterator.
192- *
193- * Create a %multimap consisting of copies of the elements from
194- * [first,last). This is linear in N if the range is already
sorted,
195- * and NlogN otherwise (where N is distance(first,last)).
196- */
197- template<typename _InputIterator>
198- multimap(_InputIterator __first, _InputIterator __last)
199- : _M_t()
200: { _M_t._M_insert_unique(__first, __last); }
--
Summary: multiset constructor uses insert_unique instead of
insert_equal!
Product: gcc
Version: 4.3.0
Status: UNCONFIRMED
Severity: major
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dennis dot czeremin at smiths-heimann dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35566