public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <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: Wed, 16 Feb 2022 17:43:23 +0000 [thread overview] Message-ID: <bug-104507-4-PLbFpVlCRC@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 Patrick Palka <ppalka at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[10/11/12 Regression] |[10/11 Regression] internal |internal compiler error: |compiler error: unexpected |unexpected expression |expression ‘(int)(__ret)’ |‘(int)(__ret)’ of kind |of kind cast_expr |cast_expr | --- Comment #8 from Patrick Palka <ppalka at gcc dot gnu.org> --- Fixed for GCC 12 so far.
next prev parent reply other threads:[~2022-02-16 17:43 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 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 ` ppalka at gcc dot gnu.org [this message] 2022-04-12 23:44 ` [Bug c++/104507] [10/11 " 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-PLbFpVlCRC@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).