public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/99818] [10/11 Regression] ICE in gfc_get_tree_for_caf_expr, at fortran/trans-expr.c:2186
Date: Mon, 05 Apr 2021 06:21:38 +0000	[thread overview]
Message-ID: <bug-99818-4-JzJITuL8tB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99818-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99818

--- Comment #6 from Paul Thomas <pault at gcc dot gnu.org> ---
(In reply to G. Steinmetz from comment #4)
> > Have you ever tried to put a tent up in a storm?
> ... geez, how difficult and lengthy ...
> 
> The number of bug reports is admittedly increasing,
> but the number of still unknown bugs is decreasing, isn't it?
> 
> And my impression is indeed that the number of
> unfixed/unknown bugs in gfortran is now roughly limited
> to huge(1_alpha), with alpha=~1.5 ;-)
> 
> The bug reproduction rate is likely less than one :-)

The only way to deal with it is a complete lockdown of gfortran for six months.
If nobody uses it, the number of bugs will surely drop. Then the roadmap out of
lockdown should start with only F95 being allowed, then six months later F2003
and so on. If at any stage the R number goes above unity, we revert one step in
the roadmap.

  parent reply	other threads:[~2021-04-05  6:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-29 19:33 [Bug fortran/99818] New: " gscfq@t-online.de
2021-03-30 13:08 ` [Bug fortran/99818] " rguenth at gcc dot gnu.org
2021-03-31 12:49 ` marxin at gcc dot gnu.org
2021-03-31 13:24 ` pault at gcc dot gnu.org
2021-04-01 13:34 ` pault at gcc dot gnu.org
2021-04-03  9:19 ` gscfq@t-online.de
2021-04-03 11:50 ` cvs-commit at gcc dot gnu.org
2021-04-05  6:21 ` pault at gcc dot gnu.org [this message]
2021-04-08 12:02 ` rguenth at gcc dot gnu.org
2021-05-04 12:31 ` [Bug fortran/99818] [10/11/12 " rguenth at gcc dot gnu.org
2021-08-28 20:05 ` cvs-commit at gcc dot gnu.org
2021-08-28 20:06 ` 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-99818-4-JzJITuL8tB@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).