public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/107242] ICE: tree check: expected complex_cst, have plus_expr in output_constant, at varasm.cc:5284 with frounding-math
Date: Thu, 13 Oct 2022 05:25:16 +0000 [thread overview]
Message-ID: <bug-107242-4-3VMrROOVdf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107242-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107242
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
Last reconfirmed| |2022-10-13
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Arseny Solokha from comment #3)
> Testcase w/o dependency on libstdc++:
And reduced all the way:
struct cf {
_Complex float _M_value;
};
cf
test_comparison ()
{
constexpr _Complex float a{2.2}, b{4.4};
return {a + b};
}
next prev parent reply other threads:[~2022-10-13 5:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 4:12 [Bug target/107242] New: ICE: tree check: expected complex_cst, have plus_expr in output_constant, at varasm.cc:5284 asolokha at gmx dot com
2022-10-13 5:01 ` [Bug c++/107242] " pinskia at gcc dot gnu.org
2022-10-13 5:06 ` pinskia at gcc dot gnu.org
2022-10-13 5:17 ` [Bug c++/107242] ICE: tree check: expected complex_cst, have plus_expr in output_constant, at varasm.cc:5284 with frounding-math asolokha at gmx dot com
2022-10-13 5:25 ` pinskia at gcc dot gnu.org [this message]
2022-10-14 7:24 ` rguenth at gcc dot gnu.org
2022-10-14 19:41 ` pinskia 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-107242-4-3VMrROOVdf@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).