public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "asolokha at gmx dot com" <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:17:19 +0000 [thread overview] Message-ID: <bug-107242-4-QJmWJOOOlZ@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 --- Comment #3 from Arseny Solokha <asolokha at gmx dot com> --- Testcase w/o dependency on libstdc++: template <typename> class complex; template <> struct complex<float> { template <typename _Tp> constexpr void operator+= (_Tp __z) { _M_value += __z._M_value; } _Complex float _M_value; }; constexpr complex<float> operator+ (complex<float> __x, complex<float> __y) { complex __r = __x; __r += __y; return __r; } complex<float> test_comparison () { constexpr complex<float> a{2.2}, b{4.4}; return a + b; } % powerpc-e300c3-linux-gnu-g++-13 -Og -frounding-math -c micz0onj.cc micz0onj.cc:32:1: internal compiler error: tree check: expected complex_cst, have plus_expr in output_constant, at varasm.cc:5284 32 | } | ^ 0x803d1f tree_check_failed(tree_node const*, char const*, int, char const*, ...) /var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-13.0.0_p20221009/work/gcc-13-20221009/gcc/tree.cc:8827 0x819d94 tree_check(tree_node*, char const*, int, char const*, tree_code) /var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-13.0.0_p20221009/work/gcc-13-20221009/gcc/tree.h:3526 0x819d94 output_constant /var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-13.0.0_p20221009/work/gcc-13-20221009/gcc/varasm.cc:5284 0x14b1c1a output_constructor_regular_field /var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-13.0.0_p20221009/work/gcc-13-20221009/gcc/varasm.cc:5562 0x14b1c1a output_constructor /var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-13.0.0_p20221009/work/gcc-13-20221009/gcc/varasm.cc:5829 0x14b3625 assemble_constant_contents /var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-13.0.0_p20221009/work/gcc-13-20221009/gcc/varasm.cc:3638 0x14b3d34 output_object_block /var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-13.0.0_p20221009/work/gcc-13-20221009/gcc/varasm.cc:8070 0x14b3d34 output_object_blocks() /var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-13.0.0_p20221009/work/gcc-13-20221009/gcc/varasm.cc:8148
next prev parent reply other threads:[~2022-10-13 5:17 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 ` asolokha at gmx dot com [this message] 2022-10-13 5:25 ` [Bug c++/107242] ICE: tree check: expected complex_cst, have plus_expr in output_constant, at varasm.cc:5284 with frounding-math pinskia at gcc dot gnu.org 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-QJmWJOOOlZ@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).