[Bug fortran/119800] Use of Fortran TRANSFER intrinsic with argument of derived type containing allocatable causes storage aliasing

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119800 --- Comment #7 from Keith Refson --- Yes, definitely. Any scalar with an ultimate allocatable component should be warned about.

[Bug fortran/119800] Use of Fortran TRANSFER intrinsic with argument of derived type containing allocatable causes storage aliasing

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119800 --- Comment #3 from Keith Refson --- I think it probably also needs to flag up if MOLD contains an allocatable or pointer component too. Modifying the example to TRANSFER to an integer, followed by a second TRANSFER with SOURCE= as an integer a

[Bug fortran/119800] New: Use of Fortran TRANSFER intrinsic with argument of derived type containing allocatable causes double-free abort

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119800 Bug ID: 119800 Summary: Use of Fortran TRANSFER intrinsic with argument of derived type containing allocatable causes double-free abort Product: gcc Version: 14.

[Bug fortran/103045] New: False report substring out of bounds with -fbounds-check

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103045 Bug ID: 103045 Summary: False report substring out of bounds with -fbounds-check Product: gcc Version: 10.3.0 Status: UNCONFIRMED Severity: normal Pr