[Bug fortran/97039] New: -fbounds-check misses violation with slice of array but not an element

Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: anthony.debeus at gmail dot com Target Milestone: --- Using built-in specs. COLLECT_GCC=gfortran COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/lto-wrapper Target

[Bug fortran/97039] -fbounds-check misses violation with slice of array but not an element

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97039 --- Comment #2 from Anthony M de Beus --- Clarification for anyone confused, "correct" results by a fortran compiler with bounds-checking enabled would include finding/checking incorrect bounds in (deliberately) incorrect fortran code given in th

[Bug fortran/98046] New: lock in libpthread occurs with gcc-fortran and atlas-lapack

Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: anthony.debeus at gmail dot com Target Milestone: --- When running the following code under kernel 5.8.18-1-MANJARO (among others) and gcc-fortran 10.2.0 PROGRAM bugs USE badwrite x=AC

[Bug fortran/98046] lock in libpthread occurs with gcc-fortran and atlas-lapack

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98046 --- Comment #3 from Anthony M de Beus --- Very interesting discussion in bug 30617. Particularly the view that "If you compile code with undefined behavior in it, run it and that code crashes, hangs or formats your disk, that is a bug in the cod