public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gtoth at umich dot edu" <gcc-bugzilla@gcc.gnu.org>
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 17:39:58 +0000 [thread overview]
Message-ID: <bug-92065-4-2ZuqMigRFS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-92065-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92065
--- Comment #14 from Gabor <gtoth at umich dot edu> ---
Hi All,
I am sorry if I hurt anyone’s feelings. My goal was to get things improved for
the future. If my dry humor offended you, my apologies. Even if you fixed the
bug today, I would still have to find a work-around. My nightly tests fail, the
users of our software will not upgrade to the latest gfortran, the super
computers keep running old versions, and they are not willing to update. So,
why I may look selfish in your eyes, the main goal of reporting that the bug
still exists in gfortran 10 was to get things better eventually. I have no time
to learn how gcc works and find this bug in it and fix it. One would assume
that the person who wrote this part of the compiler could fix it easily given
the tiny amount of code that can reproduce the problem. For anyone else it is
hard.
In the end, I have split my module into two parts and that somehow solved the
problem. The smallest code producing the issue had 4 functions. I am attaching
it in case anyone actually wants it.
I have assumed, apparently incorrectly, that gcc and its part gfortran are
maintained by the GNU project and that the GNU project has some business model.
gcc seems to thrive. I guess gfortran is not important enough. You should take
pride in having a compiler as good as intel, nag and much better than pgi.
Cheers,
Gabor
next prev parent reply other threads:[~2020-12-20 17:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-92065-4@http.gcc.gnu.org/bugzilla/>
2020-04-20 20:08 ` [Bug fortran/92065] [8/9/10 " anlauf at gcc dot gnu.org
2020-12-19 22:22 ` [Bug fortran/92065] [8/9/10/11 " gtoth at umich dot edu
2020-12-19 23:17 ` kargl at gcc dot gnu.org
2020-12-19 23:35 ` gtoth at umich dot edu
2020-12-20 0:02 ` sgk at troutmask dot apl.washington.edu
2020-12-20 5:24 ` gtoth at umich dot edu
2020-12-20 7:07 ` sgk at troutmask dot apl.washington.edu
2020-12-20 12:14 ` dominiq at lps dot ens.fr
2020-12-20 13:55 ` tkoenig at gcc dot gnu.org
2020-12-20 17:39 ` gtoth at umich dot edu [this message]
2020-12-20 20:01 ` dominiq at lps dot ens.fr
2020-12-21 8:52 ` drikosev at gmail dot com
2020-12-21 9:40 ` jakub at gcc dot gnu.org
2020-12-21 10:09 ` jakub at gcc dot gnu.org
2020-12-21 10:12 ` dominiq at lps dot ens.fr
2020-12-21 10:13 ` jakub at gcc dot gnu.org
2020-12-22 21:15 ` drikosev at gmail dot com
2020-12-24 11:10 ` drikosev at gmail dot com
2020-12-26 1:04 ` drikosev at gmail dot com
2020-12-26 2:58 ` gtoth at umich dot edu
2021-05-14 9:52 ` [Bug fortran/92065] [9/10/11/12 " jakub at gcc dot gnu.org
2021-05-20 18:54 ` anlauf at gcc dot gnu.org
2021-05-21 6:59 ` rguenth at gcc dot gnu.org
2021-05-21 8:17 ` jakub at gcc dot gnu.org
2021-05-25 19:49 ` anlauf at gcc dot gnu.org
2021-06-01 8:15 ` rguenth at gcc dot gnu.org
2021-09-06 19:12 ` [Bug fortran/92065] [9/10/11 " anlauf at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-92065-4-2ZuqMigRFS@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).