public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "meissner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/103317] New: Spec 2017 benchmark blender_r fails with -Ofast on PowerPc (power9, power10) Date: Thu, 18 Nov 2021 16:02:07 +0000 [thread overview] Message-ID: <bug-103317-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103317 Bug ID: 103317 Summary: Spec 2017 benchmark blender_r fails with -Ofast on PowerPc (power9, power10) Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: meissner at gcc dot gnu.org Target Milestone: --- Created attachment 51832 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51832&action=edit Preprocessed .i file that shows the bug (gzipped). As of November 17th, the current trunk compiler for GCC 12 fails when compiling the Spec 2017 benchmark blender_r for PowerPC using -Ofast. I see failures for both power9 and power10 systems. Here is the traceback: libpng/png.c: In function 'png_build_gamma_table': libpng/png.c:2872:1: error: definition in block 19 does not dominate use in block 18 2872 | } | ^ for SSA_NAME: _57 in statement: shift_48 = PHI <_57(18), _58(19)> PHI argument _57 for PHI node shift_48 = PHI <_57(18), _58(19)> during GIMPLE pass: phiopt libpng/png.c:2872:1: internal compiler error: verify_ssa failed 0x10c5f64b verify_ssa(bool, bool) /home/meissner/fsf-src/trunk-2021-11-17/gcc/tree-ssa.c:1211 0x1080e97f execute_function_todo /home/meissner/fsf-src/trunk-2021-11-17/gcc/passes.c:2049 0x1080f613 execute_todo /home/meissner/fsf-src/trunk-2021-11-17/gcc/passes.c:2096 Please submit a full bug report, with preprocessed source if appropriate. I see it with -O2, -O3, and -Ofast, using -mcpu=power8, -mcpu=power9, and -mcpu=power10 on PowerPC little endian systems. It did compile with the compiler I checked out on November 4th. I will attach the .i file compressed with gzip.
next reply other threads:[~2021-11-18 16:02 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-18 16:02 meissner at gcc dot gnu.org [this message] 2021-11-18 16:03 ` [Bug tree-optimization/103317] " meissner at gcc dot gnu.org 2021-11-18 16:22 ` bergner at gcc dot gnu.org 2021-11-18 16:32 ` meissner at gcc dot gnu.org 2021-11-18 16:55 ` bergner at gcc dot gnu.org 2021-11-18 17:10 ` bergner at gcc dot gnu.org 2021-11-18 18:13 ` bergner at gcc dot gnu.org 2021-11-18 18:26 ` pinskia at gcc dot gnu.org 2021-11-18 18:30 ` pinskia at gcc dot gnu.org 2021-11-18 20:51 ` bergner at gcc dot gnu.org 2021-11-18 20:55 ` pinskia at gcc dot gnu.org 2021-11-18 20:56 ` pinskia at gcc dot gnu.org 2021-11-18 23:31 ` [Bug tree-optimization/103317] [12 regression] " pinskia at gcc dot gnu.org 2021-11-19 0:42 ` bergner at gcc dot gnu.org 2021-11-19 1:54 ` pinskia at gcc dot gnu.org 2021-11-19 7:20 ` cvs-commit at gcc dot gnu.org 2021-11-19 7:21 ` pinskia at gcc dot gnu.org 2021-11-19 11:51 ` 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-103317-4@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).