public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/105317] How to deal with this: internal compiler error: in process_init_constructor_array, at cp/typeck2.c:1308?
Date: Wed, 20 Apr 2022 14:33:06 +0000	[thread overview]
Message-ID: <bug-105317-4-ARl3ohomkY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105317-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #12 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I don't think it really matters.  gcc 7 or 8 aren't supported anymore, there
won't be any further releases from those branches, so you either need to report
it to whomever provided you gcc if they still support that gcc by themselves,
or use a newer gcc, or find and backport a fix yourself, or find a workaround.
There is nothing we can do for you, unless the bug is still present in gcc 9 or
later.

  parent reply	other threads:[~2022-04-20 14:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-20  9:21 [Bug c++/105317] New: " szy_mailbox at 126 dot com
2022-04-20  9:50 ` [Bug c++/105317] " marxin at gcc dot gnu.org
2022-04-20  9:58 ` szy_mailbox at 126 dot com
2022-04-20  9:59 ` szy_mailbox at 126 dot com
2022-04-20 10:04 ` marxin at gcc dot gnu.org
2022-04-20 10:09 ` szy_mailbox at 126 dot com
2022-04-20 10:10 ` marxin at gcc dot gnu.org
2022-04-20 10:12 ` szy_mailbox at 126 dot com
2022-04-20 10:13 ` marxin at gcc dot gnu.org
2022-04-20 10:16 ` szy_mailbox at 126 dot com
2022-04-20 10:17 ` marxin at gcc dot gnu.org
2022-04-20 14:28 ` szy_mailbox at 126 dot com
2022-04-20 14:33 ` jakub at gcc dot gnu.org [this message]
2022-04-20 14:42 ` szy_mailbox at 126 dot com
2022-04-20 15:12 ` szy_mailbox at 126 dot com
2022-04-20 15:33 ` szy_mailbox at 126 dot com

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-105317-4-ARl3ohomkY@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).