http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61023
--- Comment #4 from Nevin Liber ---
Good point about the Standard.
However, the current behavior for move assignment breaks the invariant of the
container, since the comparator is what enforces the insertion ordering and
element equivalence.
Tak
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61023
--- Comment #2 from Nevin Liber ---
Also happens with multiset and multimap.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61023
--- Comment #1 from Nevin Liber ---
Created attachment 32719
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32719&action=edit
Test case using set showing the problem
ormal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: nevin at eviloverlord dot com
If you have a stateful comparator, set/map move assignment does not move (or
copy, for that matter) the comparator.
Test case:
struct Co
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60852
--- Comment #1 from Nevin Liber ---
Also filed this as a Boost bug at https://svn.boost.org/trac/boost/ticket/9913
: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: nevin at eviloverlord dot com
Created attachment 32608
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32608&action=edit
Reproducible test program
This works under gcc 4.7.2 and clang 3.4, but fails to compile un
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55826
--- Comment #2 from Nevin Liber 2012-12-28
19:56:29 UTC ---
Created attachment 29061
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29061
Build output
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55826
--- Comment #1 from Nevin Liber 2012-12-28
19:55:55 UTC ---
Created attachment 29060
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29060
Output of -save-temps
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55826
Bug #: 55826
Summary: -ftime-report causes internal compiler error with
Boost.Asio
Classification: Unclassified
Product: gcc
Version: 4.7.2
Status: UNCONFIR
--- Comment #3 from nevin at eviloverlord dot com 2008-06-18 19:06 ---
Expanding on my last comment: which lines in the following code should fail to
compile:
struct Squeeze
{
short s;
} __attribute__((aligned(1), packed));
void VerticallyChallenged(short*) {}
void
--- Comment #2 from nevin at eviloverlord dot com 2008-06-18 18:49 ---
Why is this an error (I couldn't find anything in the documentation)?
Also, if pointers are used instead of references, should that be an error
(currently that compiles just fine)?
--
http://gcc.gn
Version: 4.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: nevin at eviloverlord dot com
GCC build triplet: i686-apple-darwin9
GCC host triplet: i686-apple-darw
12 matches
Mail list logo