https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106423
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|--- |13.0
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106423
--- Comment #4 from Ville Voutilainen ---
(In reply to Tom Honermann from comment #3)
> I believe this issue can be resolved as fixed via commit
> 60468d6cd46a3bd3afe8ff856f82afcd4c65a217 for the gcc 13 release.
Yes, it's normal procedure that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106423
--- Comment #3 from Tom Honermann ---
I believe this issue can be resolved as fixed via commit
60468d6cd46a3bd3afe8ff856f82afcd4c65a217 for the gcc 13 release.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106423
--- Comment #2 from CVS Commits ---
The master branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:60468d6cd46a3bd3afe8ff856f82afcd4c65a217
commit r13-2081-g60468d6cd46a3bd3afe8ff856f82afcd4c65a217
Author: Tom Honermann
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106423
Ville Voutilainen changed:
What|Removed |Added
CC||ville.voutilainen at gmail dot
com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106423
--- Comment #1 from Tom Honermann ---
A patch for this issue was submitted to the gcc-patches mailing list and is
available at https://gcc.gnu.org/pipermail/gcc-patches/2022-July/598736.html.
