public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/111903] [14 Regression] ICE: tree check: expected class 'type', have 'exceptional' (error_mark) in create_tmp_from_val, at gimplify.cc:567 with -mno-sse2 and _Float16 Date: Mon, 23 Oct 2023 10:55:43 +0000 [thread overview] Message-ID: <bug-111903-4-emMgaaJ2G0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111903-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111903 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Andrew Pinski <pinskia@gcc.gnu.org>: https://gcc.gnu.org/g:13c0d052478bb45cc97869f5cc333f269aadb36f commit r14-4858-g13c0d052478bb45cc97869f5cc333f269aadb36f Author: Andrew Pinski <pinskia@gmail.com> Date: Fri Oct 20 14:47:55 2023 -0700 convert_to_complex vs invalid_conversion [PR111903] convert_to_complex when creating a COMPLEX_EXPR does not currently check if either the real or imag parts was not error_mark_node. This later on confuses the gimpilfier when there was a SAVE_EXPR wrapped around that COMPLEX_EXPR. The simple fix is after calling convert inside convert_to_complex_1, check that the either result was an error_operand and return an error_mark_node in that case. Bootstrapped and tested on x86_64-linux-gnu with no regressions. PR c/111903 gcc/ChangeLog: * convert.cc (convert_to_complex_1): Return error_mark_node if either convert was an error when converting from a scalar. gcc/testsuite/ChangeLog: * gcc.target/i386/float16-8.c: New test.
next prev parent reply other threads:[~2023-10-23 10:55 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-20 21:00 [Bug target/111903] New: " zsojka at seznam dot cz 2023-10-20 21:03 ` [Bug c/111903] " pinskia at gcc dot gnu.org 2023-10-20 21:36 ` pinskia at gcc dot gnu.org 2023-10-21 18:07 ` pinskia at gcc dot gnu.org 2023-10-23 10:55 ` cvs-commit at gcc dot gnu.org [this message] 2023-10-23 10:55 ` cvs-commit at gcc dot gnu.org 2023-10-23 10:56 ` 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-111903-4-emMgaaJ2G0@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).