public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/79426] [10 Regression] fortran - internal compiler error: in fold_convert_loc, at fold-const.c:2251
Date: Wed, 14 Dec 2022 19:40:37 +0000	[thread overview]
Message-ID: <bug-79426-4-29r4TPcf3B@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-79426-4@http.gcc.gnu.org/bugzilla/>

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

anlauf at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[10/11/12/13 Regression]    |[10 Regression] fortran -
                   |fortran - internal compiler |internal compiler error: in
                   |error: in fold_convert_loc, |fold_convert_loc, at
                   |at fold-const.c:2251        |fold-const.c:2251
      Known to work|                            |11.3.1, 12.2.1, 13.0
      Known to fail|                            |10.4.0

--- Comment #16 from anlauf at gcc dot gnu.org ---
Adding recent known to work/known to fail versions.

There are a couple of patches by Jose that look like they may have contributed
to fixing this one, but if multiple patches are needed, it may be risky to
backport.

I've marked it as a 10 regression, so that it may be closed as WONTFIX for
10-branch when it closes.

  parent reply	other threads:[~2022-12-14 19:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-79426-4@http.gcc.gnu.org/bugzilla/>
2021-05-14  9:48 ` [Bug fortran/79426] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01  8:08 ` rguenth at gcc dot gnu.org
2022-05-27  9:36 ` [Bug fortran/79426] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:32 ` jakub at gcc dot gnu.org
2022-12-13 21:49 ` anlauf at gcc dot gnu.org
2022-12-14 19:40 ` anlauf at gcc dot gnu.org [this message]
2023-07-07  7:37 ` [Bug fortran/79426] [10 " rguenth 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-79426-4-29r4TPcf3B@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).