public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109807] [14 Regression] sse2-mmx-pmaddwd.c met ICE after commit r14-666-g608e7f3ab47 with march=cascadelake Date: Thu, 11 May 2023 07:51:09 +0000 [thread overview] Message-ID: <bug-109807-4-nS08rTJTBr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109807-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109807 David Binderman <dcb314 at hotmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcb314 at hotmail dot com --- Comment #3 from David Binderman <dcb314 at hotmail dot com> --- I see the same for this C code on znver1: typedef struct MonitorInfo MonitorInfo; char *decode_edid_edid; struct MonitorInfo { int width_mm; int height_mm } decode_edid() { MonitorInfo info; MonitorInfo *__trans_tmp_3 = &info; { MonitorInfo *info = __trans_tmp_3; info->width_mm = 10 * decode_edid_edid[5]; info->height_mm = 10 * decode_edid_edid[6]; } decode_headerdecode_vendor_and_product_identificationdecode_edid_version( info); } $ ~/gcc/results.20230511.asan.ubsan/bin/gcc -c -O2 -march=znver1 -w bug919.c during GIMPLE pass: slp bug919.c: In function ‘decode_edid’: bug919.c:6:3: internal compiler error: in ix86_widen_mult_cost, at config/i386/i386.cc:20442 6 | } decode_edid() { | ^~~~~~~~~~~ It was ok yesterday: $ ~/gcc/results.20230510.asan.ubsan/bin/gcc -c -O2 -march=znver1 -w bug919.c $
next prev parent reply other threads:[~2023-05-11 7:51 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-11 6:25 [Bug target/109807] New: [14 Regression] sse2-mmx-pmaddwd.c met ICE after commit gcc-14-666-g608e7f3ab47 " haochen.jiang at intel dot com 2023-05-11 6:52 ` [Bug target/109807] [14 Regression] sse2-mmx-pmaddwd.c met ICE after commit r14-666-g608e7f3ab47 " haochen.jiang at intel dot com 2023-05-11 7:25 ` ubizjak at gmail dot com 2023-05-11 7:51 ` dcb314 at hotmail dot com [this message] 2023-05-11 7:53 ` haochen.jiang at intel dot com 2023-05-11 8:06 ` ubizjak at gmail dot com 2023-05-11 12:50 ` rguenth at gcc dot gnu.org 2023-05-11 15:42 ` ubizjak at gmail dot com 2023-05-11 18:55 ` cvs-commit at gcc dot gnu.org 2023-05-11 18:57 ` ubizjak at gmail dot com 2023-05-13 8:31 ` ubizjak at gmail dot com 2023-05-13 10:44 ` dcb314 at hotmail dot com 2023-05-13 10:50 ` ubizjak at gmail dot com 2023-05-14 19:53 ` cvs-commit at gcc dot gnu.org 2023-05-14 19:56 ` ubizjak at gmail dot com 2023-05-14 19:57 ` ubizjak at gmail dot com 2023-05-14 19:59 ` ubizjak at gmail dot com
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-109807-4-nS08rTJTBr@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).