https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112410
Marek Polacek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112410
--- Comment #6 from GCC Commits ---
The releases/gcc-13 branch has been updated by Marek Polacek
:
https://gcc.gnu.org/g:60979215517629400902938b1c5666f97d0653cf
commit r13-8147-g60979215517629400902938b1c5666f97d0653cf
Author: Marek Polacek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112410
--- Comment #5 from Marek Polacek ---
Fixed on trunk so far; I want to fix it in 13 too.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112410
--- Comment #4 from CVS Commits ---
The trunk branch has been updated by Marek Polacek :
https://gcc.gnu.org/g:70060dadfbf0d0af5f4cab5f3aff3223a4523606
commit r14-5514-g70060dadfbf0d0af5f4cab5f3aff3223a4523606
Author: Marek Polacek
Date: Th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112410
Marek Polacek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112410
--- Comment #2 from Andrew Pinski ---
Confirmed.
Looks like GCC is messing the Most vexing parse here.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112410
Marek Polacek changed:
What|Removed |Added
Ever confirmed|0 |1
CC|
