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/12 Regression] internal compiler error: unexpected expression ‘(int)(__ret)’ of kind cast_expr
Date: Mon, 14 Feb 2022 16:57:18 +0000 [thread overview]
Message-ID: <bug-104507-4-m7xIqnnVId@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
----------------------------------------------------------------------------
Ever confirmed|0 |1
Summary|[10/11 Regression] internal |[10/11/12 Regression]
|compiler error: unexpected |internal compiler error:
|expression ‘(int)(__ret)’ |unexpected expression
|of kind cast_expr |‘(int)(__ret)’ of kind
| |cast_expr
Status|UNCONFIRMED |NEW
Last reconfirmed| |2022-02-14
Known to fail| |12.0
--- Comment #6 from Patrick Palka <ppalka at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #3)
> (In reply to Daniel Nelson from comment #2)
> > Had a few moments to do some testing/bisecting, and found the commit that
> > fixed this in mainline.
>
> I kinda of see how that might help here but not really. I wonder if there is
> another testcase which might shows the issue on the trunk still.
trunk crashes on this version:
#define ERR_MAX -20
#define s_errmsg(r) \
_k_errmsg[(((int)r) <= 0 && r) ? -(r) : -ERR_MAX]
extern const char *_k_errmsg[];
template <int size>
inline int DoFoo() {
int __ret = 0;
const char *n = s_errmsg(__ret);
return __ret;
}
next prev parent reply other threads:[~2022-02-14 16: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
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 ` ppalka at gcc dot gnu.org [this message]
2022-02-15 16:17 ` [Bug c++/104507] [10/11/12 " 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-m7xIqnnVId@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).