https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86295
--- Comment #4 from Jonathan Wakely ---
P.S. the uninitialized_xxx algos have to work that way, because if an exception
occurs the caller has no way to know how many objects got created before the
exception, so the functions could never be used r
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86295
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86295
--- Comment #2 from Kristian Spangsege ---
Oh, I missed that crucial fact. Sorry. We can close this as invalid then.
On Mon, Jun 25, 2018 at 3:35 PM, redi at gcc dot gnu.org <
gcc-bugzi...@gcc.gnu.org> wrote:
> https://gcc.gnu.org/bugzilla/show
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86295
--- Comment #1 from Jonathan Wakely ---
(In reply to Kristian Spangsege from comment #0)
> The problem occurs when either `std::__uninitialized_copy_a()` or
> `std::__uninitialized_move_a()` throws due to throwing from the copy or move
> construc
