https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110807
--- Comment #14 from GCC Commits ---
The releases/gcc-13 branch has been updated by Torbjorn Svensson
:
https://gcc.gnu.org/g:5d684a5f7f82b1425cac5eaa11dccc3b51a62d44
commit r13-8309-g5d684a5f7f82b1425cac5eaa11dccc3b51a62d44
Author: Alexandre
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110807
--- Comment #13 from CVS Commits ---
The master branch has been updated by Alexandre Oliva :
https://gcc.gnu.org/g:e39b3e02c27bd771a07e385f9672ecf1a45ced77
commit r14-5260-ge39b3e02c27bd771a07e385f9672ecf1a45ced77
Author: Alexandre Oliva
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110807
--- Comment #12 from Jonathan Wakely ---
I don't think _M_offset can ever be out of range, it's always set by the
library code.
Doesn't the warning come from this line, which doesn't use _M_offset anyway?
_Bit_type* __q =
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110807
Alexandre Oliva changed:
What|Removed |Added
CC||aoliva at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110807
Jonathan Wakely changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110807
--- Comment #9 from CVS Commits ---
The releases/gcc-13 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:962cd3e2c475e8197fd0cfa7330a8f352b4ff5b2
commit r13-7625-g962cd3e2c475e8197fd0cfa7330a8f352b4ff5b2
Author: Jonathan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110807
--- Comment #8 from Jonathan Wakely ---
The new test fails with -m32 -D_GLIBCXX_USE_CXX11_ABI=0
I give up.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110807
--- Comment #7 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:f30e62b0ee05befd20863466d1fb55a34d15c228
commit r14-2802-gf30e62b0ee05befd20863466d1fb55a34d15c228
Author: Jonathan Wakely
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110807
Jonathan Wakely changed:
What|Removed |Added
Summary|[13/14 Regression] Copy |[13 Regression] Copy list
