[Bug fortran/114859] Seeing new segmentation fault in same_type_as

2024-04-26 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114859

--- Comment #4 from Jakub Jelinek  ---
LTO doesn't seem to make a difference.  And without LTO bisection points at
openmpi-build/amgprec/impl/amg_d_hierarchy_bld.o
when this is compiled with r14-9704 even when all other sources are compiled
with
the newer compiler, the testcase works, while when this is compiled with
r14-9924
and all other sources with the older compiler, it crashes.

[Bug fortran/114859] Seeing new segmentation fault in same_type_as

2024-04-26 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114859

--- Comment #3 from Jakub Jelinek  ---
Oh, and start by disabling LTO and see if it makes a difference.

[Bug fortran/114859] Seeing new segmentation fault in same_type_as

2024-04-26 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114859

--- Comment #2 from Jakub Jelinek  ---
If it is Fortran FE, then the possible commits might be
r14-9893 r14-9874 r14-9873 r14-9753 r14-9752 r14-9720 r14-9719 r14-9712
Anyway, best would be to try to compile the
amg_d_jac_smoother_clone_settings.f90
CU with a different compiler from the rest and see whether that is what changes
the testcase, or if not, bisect among *.o files in the package, the *.mod files
should be hopefully compatible between the 2 compilers.  And when a single CU
is known to change the outcome, then bisect it with gcc revisions.

[Bug fortran/114859] Seeing new segmentation fault in same_type_as

2024-04-26 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114859

Jakub Jelinek  changed:

   What|Removed |Added

 CC||jakub at gcc dot gnu.org

--- Comment #1 from Jakub Jelinek  ---
The Fedora versions don't provide any information to upstream,
14.0.1-0.13.fc40 is r14-9704 and 14.0.1-0.15.fc40 is r14-9924