https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91780
--- Comment #13 from Mikael Persson ---
Ah right lifetime
On Sun, 19 Dec 2021, 16:02 Mikael Persson,
wrote:
> Looking at it now, not sure why i didnt.
>
> On Sun, 19 Dec 2021, 14:00 redi at gcc dot gnu.org, <
> gcc-bugzi...@gcc.gnu.org>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91780
--- Comment #12 from Mikael Persson ---
Looking at it now, not sure why i didnt.
On Sun, 19 Dec 2021, 14:00 redi at gcc dot gnu.org, <
gcc-bugzi...@gcc.gnu.org> wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91780
>
> --- Comment #11
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91780
--- Comment #10 from Mikael Persson ---
Thats great.
Saw the dates on the other pr, jikes this has been around a while.
Testing
z.containers_[0]->i is clever, ill add a test for that ( or more generally
z.containers_[0]->begin(), static_assert
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91780
--- Comment #1 from Mikael Persson ---
To clarify it also does not work in gcc trunk.
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: mikael.p.persson at gmail dot com
Target Milestone: ---
GCC does not change values in tuple of references
The bug is indicated by a difference between gcc7.4 to 9.2 and gcc trunk and
clang
