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 middle-end/100898] [9/10/11 Regression] ICE with -O2: in gimple_call_arg_ptr, at gimple.h:3264 Date: Mon, 07 Jun 2021 07:37:12 +0000 [thread overview] Message-ID: <bug-100898-4-3j3HitMY5o@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100898-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100898 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[9/10/11/12 Regression] ICE |[9/10/11 Regression] ICE |with -O2: in |with -O2: in |gimple_call_arg_ptr, at |gimple_call_arg_ptr, at |gimple.h:3264 |gimple.h:3264 --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Fixed on the trunk so far. Less important on release branches, since they aren't checking by default, but still worth fixing there.
next prev parent reply other threads:[~2021-06-07 7:37 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-04 3:34 [Bug c/100898] New: " cnsun at uwaterloo dot ca 2021-06-04 13:30 ` [Bug middle-end/100898] [9/10/11/12 Regression] " jakub at gcc dot gnu.org 2021-06-04 13:57 ` jakub at gcc dot gnu.org 2021-06-07 7:26 ` cvs-commit at gcc dot gnu.org 2021-06-07 7:37 ` jakub at gcc dot gnu.org [this message] 2021-06-07 9:07 ` [Bug middle-end/100898] [9/10/11 " rguenth at gcc dot gnu.org 2021-06-17 5:59 ` cvs-commit at gcc dot gnu.org 2021-06-17 7:59 ` [Bug middle-end/100898] [9/10 " jakub at gcc dot gnu.org 2022-05-10 8:18 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:20 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:34 ` jakub 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-100898-4-3j3HitMY5o@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: linkBe 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).