https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91556
--- Comment #22 from Thomas Koenig <tkoenig at gcc dot gnu.org> --- A problem with such code is that type violations like that are likely to cause actual wrong code issues because much of the aliasing analysis is type based... What I could do is to a) restrict the number of warnings for each routine to one (put a flag Into the gsym) b) try to figure something out to make this harmless to the middle end... like passing a void* instead of a reference. If we just continue to ignore this error, is is going to bite people sooner or later. And wehn somevody finds that a complex MPI code no longer works, I want to have that warning in the build log. Also, this sort of code is a major obstacle for LTO, If we do not fix this, then I might as well give up on making gfortran LTO clean.
