public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/99122] [10/11 Regression] ICE in force_constant_size, at gimplify.c:733
Date: Mon, 29 Mar 2021 16:43:22 +0000	[thread overview]
Message-ID: <bug-99122-4-BIvBcvZIv2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99122-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #29 from Martin Jambor <jamborm at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #28)
> So fixed for GCC 11 now?

Yes, it should be fixed in GCC 11.

We talked about backporting the patches to GCC 10 with Richi on IRC today and
decided to wait for potential fallout even if we miss the 10.3 release.

  parent reply	other threads:[~2021-03-29 16:43 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-16 17:38 [Bug c/99122] New: " gscfq@t-online.de
2021-02-16 18:24 ` [Bug ipa/99122] " jakub at gcc dot gnu.org
2021-02-17 16:38 ` jakub at gcc dot gnu.org
2021-02-17 17:03 ` jamborm at gcc dot gnu.org
2021-02-17 17:10 ` jamborm at gcc dot gnu.org
2021-02-17 17:15 ` jakub at gcc dot gnu.org
2021-02-17 17:52 ` jamborm at gcc dot gnu.org
2021-02-17 17:57 ` jakub at gcc dot gnu.org
2021-02-18  9:09 ` rguenth at gcc dot gnu.org
2021-02-18 11:20 ` rguenth at gcc dot gnu.org
2021-02-18 11:26 ` rguenth at gcc dot gnu.org
2021-02-18 11:27 ` jakub at gcc dot gnu.org
2021-02-18 12:00 ` jakub at gcc dot gnu.org
2021-02-18 12:24 ` jamborm at gcc dot gnu.org
2021-02-18 12:42 ` jamborm at gcc dot gnu.org
2021-02-18 13:38 ` cvs-commit at gcc dot gnu.org
2021-02-18 18:13 ` jamborm at gcc dot gnu.org
2021-02-19  8:37 ` rguenth at gcc dot gnu.org
2021-02-19  8:42 ` rguenth at gcc dot gnu.org
2021-02-19 10:31 ` jamborm at gcc dot gnu.org
2021-02-19 10:40 ` jakub at gcc dot gnu.org
2021-02-19 10:54 ` rguenther at suse dot de
2021-02-19 13:20 ` cvs-commit at gcc dot gnu.org
2021-02-25 13:01 ` rguenth at gcc dot gnu.org
2021-03-04 14:22 ` jamborm at gcc dot gnu.org
2021-03-05 14:28 ` jamborm at gcc dot gnu.org
2021-03-06 10:54 ` dcb314 at hotmail dot com
2021-03-24 19:28 ` cvs-commit at gcc dot gnu.org
2021-03-29 16:31 ` jakub at gcc dot gnu.org
2021-03-29 16:43 ` jamborm at gcc dot gnu.org [this message]
2021-04-08 12:02 ` [Bug ipa/99122] [10 " rguenth at gcc dot gnu.org
2021-06-02 11:27 ` ebotcazou at gcc dot gnu.org
2021-06-02 11:44 ` rguenth at gcc dot gnu.org
2021-06-02 12:25 ` ebotcazou at gcc dot gnu.org
2021-06-02 12:42 ` rguenth at gcc dot gnu.org
2021-06-02 13:03 ` ebotcazou at gcc dot gnu.org
2021-06-03 10:46 ` cvs-commit at gcc dot gnu.org
2021-06-03 10:49 ` cvs-commit at gcc dot gnu.org
2022-06-28 10:43 ` jakub at gcc dot gnu.org
2023-07-07  9:27 ` 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-99122-4-BIvBcvZIv2@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).