From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id C811A385780B; Sun, 20 Dec 2020 05:24:53 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C811A385780B From: "gtoth at umich dot edu" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/92065] [8/9/10/11 Regression] internal compiler error: in expand_expr_real_1 Date: Sun, 20 Dec 2020 05:24:53 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 9.2.1 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: gtoth at umich dot edu X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P4 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.5 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Dec 2020 05:24:53 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D92065 --- Comment #10 from Gabor --- Good to know that gfortran has come to an end. It means, for example, that i will not rely on the openacc implementation either. Or openmp5. I develop software as part of my work, and when someone reports a bug, my reaction is to try to fix it, not giving a lecture to the user. I am not a compiler developer. I have interacted with various compiler developer groups, including Intel, nag and pgi. Not all of them are equally good or competent or quick, but at least they don't try to push the blame on the user. If you haven't fixed a bug for years, why do you respond to a complaint about it the same day? G=C3=A1bor On Sat, Dec 19, 2020, 7:02 PM sgk at troutmask dot apl.washington.edu < gcc-bugzilla@gcc.gnu.org> wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D92065 > > --- Comment #9 from Steve Kargl > --- > On Sat, Dec 19, 2020 at 11:35:24PM +0000, gtoth at umich dot edu wrote: > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D92065 > > > > > > Apparently this bug was reported years ago, and it was not fixed. There > was no > > suggestion on how to avoid it either. > > > > I am not sure why gfortran is not supported by GNU, as it is used > heavily in > > the computational physics community and gfortran is one of the compilers > (the > > other is ifort) installed on supercomputers around the world. There are > > millions and millions of lines of code depending on Fortran and there > are 10s > > of thousands of scientists and students using these codes. The only hope > to > > adopt new (meaning beyond F77 and F90) features of Fortran by the > community is > > to have compilers that can handle these new features. Why am I wasting > time to > > write a nice piece of code (in this case a general interpolation routine > that > > can handle any type of numbers) if in the end I get a compiler internal > error. > > nagfor can handle it, ifort can handle it, gfortran cannot. And gfortran > is one > > of the MAIN fortran compilers. So now I have to dumb down my code to the > usual > > cut-and-paste style, repetition and so on, because I cannot use > class(*). > > > > So I am frustrated. And maybe my frustration will motivate you to fix t= he > > problem. > > > > Apparently, you missed the word "volunteer". How much did you > (and others) pay in ifort and nagfor licenses and support > contracts? No one is willing to pay for general maintianence > of gfortran. At best, you may find someone willing to pay for > a specific feature (e.g., ORNL's support for work on openacc). > I've fixed 100s of bugs and implemented some new features for > gfortran. Many of my fixes are for bugs that affected my own > Fortran code. Some are for bugs in areas of the compiler I > know well. I've also reviewed 100s of patches by others. > I do not use the OOP features of Fortran, so I have very little > knowledge about its implementation details. So, your SOL > if you're waiting for me to fix this bug. > > Rants, like yours here, are one of two reasons why I've > stopped contributing to gfortran. I will no longer review > patches, and if I submit a patch, it will be to fix a bug > affecting my code. > > -- > You are receiving this mail because: > You are on the CC list for the bug.=