https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121628
--- Comment #24 from kargls at comcast dot net --- (In reply to Christopher Albert from comment #23) > (In reply to kargls from comment #22) > > (In reply to Jerry DeLisle from comment #21) > > > (In reply to Christopher Albert from comment #20) > > > > > > > > Thanks Jerry, I couldn't believe how fast this was merged, so I see this > > > > positive. I posted a patch here that should provide a fix together with > > > > Harald's comments. Test suite is still finishing run, but it looks good > > > > so > > > > far. Can you check if you agree with this solution? > > > > > > Your time and skill is greatly appreciated. I applied and tested the fixer > > > patch here. I will hold for any last minute comments from Steve or Harald. > > > > > > Regression tests OK as well. > > > > I've read the new patch, but unfortunately, the relevant > > part that fixes the issue appears to be c++. If it passes > > regression testing and no one else comments, jerry feel > > free to commit. > > Sorry about that Steve, I was not aware that you would like to keep that > part of gcc free of C++. Would you like it to be rewritten in pure C? (btw I > just saw that there one std::swap was added to the file already in 2015 when > it still had .c extension) No. C++ is used elsewhere in GCC and is slowly moving into the Fortran portion. Perhaps, the move towards C++ will attract a new generation of gfortran contributors.
