public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bugreporter66 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109004] New: wrong code for -O2 (any above -O0) with g++ 11.3 for POWER9 (cross-compiler on x86_64 host) Date: Fri, 03 Mar 2023 09:59:23 +0000 [thread overview] Message-ID: <bug-109004-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109004 Bug ID: 109004 Summary: wrong code for -O2 (any above -O0) with g++ 11.3 for POWER9 (cross-compiler on x86_64 host) Product: gcc Version: 11.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: bugreporter66 at gmail dot com Target Milestone: --- Created attachment 54574 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54574&action=edit archive with all the necessary source and output files The code sample is attached with all the necessary output files. It's a regression from g++ 9.x series, where it worked properly. The line that fails the test is a ternary operator working on two memory floating point operands: farr[n] < farr[m] ? farr[n] : farr[m]; Two potential workarounds for this are turning optimizations off (-O0) or re-targeting to POWER8 instead (-O2 -mcpu=power8). The test case is taken from https://github.com/VectorChief/UniSIMD-assembler, where that test fails (v1.1.0c) for POWER9 target on Ubuntu MATE 22.04.2
next reply other threads:[~2023-03-03 9:59 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-03 9:59 bugreporter66 at gmail dot com [this message] 2023-03-03 12:32 ` [Bug target/109004] [10/11/12/13 Regression] " rguenth at gcc dot gnu.org 2023-03-04 6:42 ` bugreporter66 at gmail dot com 2023-03-15 8:43 ` jakub at gcc dot gnu.org 2023-03-16 10:40 ` bugreporter66 at gmail dot com 2023-03-16 10:45 ` bugreporter66 at gmail dot com 2023-03-16 11:01 ` bugreporter66 at gmail dot com 2023-03-16 11:12 ` jakub at gcc dot gnu.org 2023-03-16 11:29 ` bugreporter66 at gmail dot com 2023-03-16 11:49 ` jakub at gcc dot gnu.org 2023-03-16 12:47 ` bugreporter66 at gmail dot com 2023-03-16 12:48 ` bugreporter66 at gmail dot com 2023-03-16 12:51 ` bugreporter66 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-109004-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).