https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90904
Martin Sebor changed:
What|Removed |Added
Status|ASSIGNED|NEW
Assignee|msebor at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90904
Martin Sebor changed:
What|Removed |Added
Keywords||patch
Assignee|unassigned at gc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90904
--- Comment #5 from Martin Sebor ---
Looks like move ctor/assignment have been added to auto_vec in
g:4b9d61f79c0c0185a33048ae6cc72269cf7efa31 but not copy ctor/assignment.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90904
--- Comment #4 from rguenther at suse dot de ---
On Tue, 18 Jun 2019, msebor at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90904
>
> --- Comment #3 from Martin Sebor ---
> (In reply to Richard Biener from comment #1)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90904
--- Comment #3 from Martin Sebor ---
(In reply to Richard Biener from comment #1)
> I ran into a similar issue while trying
>
> hash_map >
>
> where copying fails to adjust the pointer to the in-place storage giving
> even more obscure errors.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90904
--- Comment #2 from Jonathan Wakely ---
Declare them private, but don't define them. In 99.9% of cases you'll get an
error at compile time for trying to use a private member. If the use happens
from inside the class itself, the private member wil
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90904
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
