https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115241
--- Comment #6 from Andrew Pinski ---
(In reply to sadineniharish8446 from comment #4)
> Is GCC upstream planning to backport the patch to older release branches for
> gcc versions? If yes, which release versions will have it?
>
> We can help t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115241
Sam James changed:
What|Removed |Added
CC||sjames at gcc dot gnu.org
--- Comment #5 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115241
--- Comment #4 from sadineniharish8446 at gmail dot com ---
Is GCC upstream planning to backport the patch to older release branches for
gcc versions? If yes, which release versions will have it?
We can help to backport the patch, if needed.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115241
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|--- |15.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115241
--- Comment #2 from Andrew Macleod ---
(In reply to sadineniharish8446 from comment #0)
> The scripts in contrib/header-tools/ are breaks with python3.
> These scripts were for python2 and we did update it for python3 and sent the
> patches to g
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115241
Andrew Pinski changed:
What|Removed |Added
CC||amacleod at redhat dot com
--- Comment
