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/109007] New: building for POWER8 leaks into POWER9 ISA with g++ 11.3 (cross-compiler on x86_64 host)
Date: Fri, 03 Mar 2023 11:58:10 +0000 [thread overview]
Message-ID: <bug-109007-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109007
Bug ID: 109007
Summary: building for POWER8 leaks into POWER9 ISA with g++
11.3 (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 54577
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54577&action=edit
archive with the source code and screenshot to reproduce the issue
The code sample is attached with the source files and a screenshot. It's a
regression from g++ 9.x series, where it worked properly.
Building for POWER8 (-mcpu=power8) creates binary that has illegal instruction
for POWER8 ISA, as confirmed by running the code with QEMU (see screenshot).
The command line for building is the following (change to test directory
first):
make -f core_make_p64.mk build_le -j4
The command line for emulation with QEMU (spits illegal instruction):
qemu-ppc64le -cpu POWER8 core_test.p64f32Lp8
The test case is taken from https://github.com/VectorChief/QuadRay-engine,
where that test fails (master) for POWER8 target on Ubuntu MATE 22.04.2
next reply other threads:[~2023-03-03 11:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 11:58 bugreporter66 at gmail dot com [this message]
2023-03-03 18:23 ` [Bug target/109007] " jakub at gcc dot gnu.org
2023-03-03 20:24 ` pinskia at gcc dot gnu.org
2023-03-04 6:47 ` bugreporter66 at gmail dot com
2023-03-04 9:56 ` bugreporter66 at gmail dot com
2023-03-04 9:58 ` bugreporter66 at gmail dot com
2023-03-04 10:10 ` jakub at gcc dot gnu.org
2023-03-04 10:36 ` bugreporter66 at gmail dot com
2023-03-04 10:40 ` bugreporter66 at gmail dot com
2023-03-04 10:49 ` jakub at gcc dot gnu.org
2023-03-04 11:24 ` bugreporter66 at gmail dot com
2023-03-04 11:30 ` jakub at gcc dot gnu.org
2023-03-04 21:12 ` bugreporter66 at gmail dot com
2023-03-04 22:02 ` segher at gcc dot gnu.org
2023-03-05 15:31 ` bugreporter66 at gmail dot com
2023-03-05 18:59 ` segher at gcc dot gnu.org
2023-03-05 20:07 ` jakub at gcc dot gnu.org
2023-03-05 21:40 ` segher at gcc dot gnu.org
2023-03-06 11:06 ` bugreporter66 at gmail dot com
2023-03-06 11:19 ` 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-109007-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: link
Be 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).