public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "h2+bugs at fsfe dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/106369] [12/13 Regression] ICE in output_constructor_regular_field, at varasm.cc:5515
Date: Thu, 21 Jul 2022 11:11:07 +0000	[thread overview]
Message-ID: <bug-106369-4-pF2OiwCszu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106369-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Hannes Hauswedell <h2+bugs at fsfe dot org> ---
I have found a workaround for my code:

template <typename derived_type, auto size>
-class aminoacid_base : public alphabet_base<derived_type, size, char>, public
aminoacid_empty_base
+class aminoacid_base : public aminoacid_empty_base, public
alphabet_base<derived_type, size, char>

This change prevents the bug from triggering. Maybe that helps in pinning it
down?

  parent reply	other threads:[~2022-07-21 11:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-20 10:26 [Bug c++/106369] New: " h2+bugs at fsfe dot org
2022-07-20 12:09 ` [Bug c++/106369] " rguenth at gcc dot gnu.org
2022-07-20 15:33 ` mpolacek at gcc dot gnu.org
2022-07-20 15:35 ` [Bug c++/106369] [12/13 Regression] " pinskia at gcc dot gnu.org
2022-07-20 15:47 ` pinskia at gcc dot gnu.org
2022-07-20 21:07 ` pinskia at gcc dot gnu.org
2022-07-21 11:11 ` h2+bugs at fsfe dot org [this message]
2022-07-21 15:24 ` [Bug c++/106369] [12/13 Regression] ICE in output_constructor_regular_field, at varasm.cc:5515 since r12-2975-g32c3a75390623a pinskia at gcc dot gnu.org
2022-07-25 15:02 ` rguenth at gcc dot gnu.org
2022-07-25 22:49 ` ppalka at gcc dot gnu.org
2022-07-26  6:42 ` rguenther at suse dot de
2022-07-26  9:15 ` jakub at gcc dot gnu.org
2022-07-26  9:19 ` jakub at gcc dot gnu.org
2022-07-26 14:31 ` jason at gcc dot gnu.org
2022-07-31  6:05 ` cvs-commit at gcc dot gnu.org
2022-08-10 13:13 ` [Bug c++/106369] [12 " rguenth at gcc dot gnu.org
2022-08-12  8:11 ` cvs-commit at gcc dot gnu.org
2022-08-12  8:12 ` 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-106369-4-pF2OiwCszu@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).