public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "junk at sigpwr dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/104507] [10/11 Regression] internal compiler error: unexpected expression ‘(int)(__ret)’ of kind cast_expr
Date: Mon, 14 Feb 2022 00:57:15 +0000	[thread overview]
Message-ID: <bug-104507-4-ANuuPzgxEX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104507-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Daniel Nelson <junk at sigpwr dot com> ---
Yeah, that was my thought as well (though I'm 99% unfamiliar with the GCC
codebase).

Some more bisecting reveals that this was introduced with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95508

ae2ebf011fec926e003645c33c07a03619ea216a is the first bad commit
commit ae2ebf011fec926e003645c33c07a03619ea216a
Author: Marek Polacek <polacek@redhat.com>
Date:   Wed Jun 17 09:19:02 2020 -0400

    c++: ICE with IMPLICIT_CONV_EXPR in array subscript [PR95508]
...

  parent reply	other threads:[~2022-02-14  0:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-11 21:45 [Bug c++/104507] New: " junk at sigpwr dot com
2022-02-11 21:51 ` [Bug c++/104507] " pinskia at gcc dot gnu.org
2022-02-11 21:53 ` [Bug c++/104507] [10/11 Regression] " pinskia at gcc dot gnu.org
2022-02-13  8:47 ` junk at sigpwr dot com
2022-02-13 23:03 ` pinskia at gcc dot gnu.org
2022-02-14  0:57 ` junk at sigpwr dot com [this message]
2022-02-14  8:32 ` rguenth at gcc dot gnu.org
2022-02-14 11:18 ` jakub at gcc dot gnu.org
2022-02-14 16:57 ` [Bug c++/104507] [10/11/12 " ppalka at gcc dot gnu.org
2022-02-15 16:17 ` ppalka at gcc dot gnu.org
2022-02-16 17:42 ` cvs-commit at gcc dot gnu.org
2022-02-16 17:43 ` [Bug c++/104507] [10/11 " ppalka at gcc dot gnu.org
2022-04-12 23:44 ` cvs-commit at gcc dot gnu.org
2022-05-04  0:22 ` [Bug c++/104507] [10 " ppalka 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-104507-4-ANuuPzgxEX@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).