https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106684
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |INVALID
Status|U
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106684
--- Comment #7 from Jorn Bruggeman ---
None from me; thanks for the explanation!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106684
--- Comment #6 from Steve Kargl ---
On Fri, Aug 19, 2022 at 07:16:21PM +, j...@bolding-bruggeman.com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106684
>
> --- Comment #5 from Jorn Bruggeman ---
> Thanks; it does look like older
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106684
--- Comment #5 from Jorn Bruggeman ---
Thanks; it does look like older gfortran versions (and ifort) are too forgiving
here, and that, given the F2018 definition of "conformable", the latest
gfortran releases are correct.
As for "stand-alone" v
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106684
--- Comment #4 from Steve Kargl ---
On Fri, Aug 19, 2022 at 06:01:46PM +, j...@bolding-bruggeman.com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106684
>
> --- Comment #2 from Jorn Bruggeman ---
>
> Are you effectively saying th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106684
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106684
--- Comment #2 from Jorn Bruggeman ---
I interpret the quoted F2018, 7.5.10 as "the same rules should govern
initialization of components of derived types and initialization of stand-alone
variables". That was previously (in 10.3, 11.2, and othe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106684
kargl at gcc dot gnu.org changed:
What|Removed |Added
CC||kargl at gcc dot gnu.org
---
