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] building for POWER8 leaks into POWER9 ISA with g++ 11.3 (cross-compiler on x86_64 host)
Date: Sat, 04 Mar 2023 10:36:27 +0000 [thread overview]
Message-ID: <bug-109007-4-VkgqNh9iSL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109007-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109007
--- Comment #7 from bugreporter66 at gmail dot com ---
After disassembling the instruction in question is stxv at 100034b0:
0000000010003470 <_GLOBAL__sub_I_eh_alloc.cc>:
10003470: 15 10 40 3c lis r2,4117
10003474: 00 7c 42 38 addi r2,r2,31744
10003478: a6 02 08 7c mflr r0
1000347c: f0 ff c1 fb std r30,-16(r1)
10003480: f8 ff e1 fb std r31,-8(r1)
10003484: 10 00 01 f8 std r0,16(r1)
10003488: d1 ff 21 f8 stdu r1,-48(r1)
1000348c: 01 00 e0 3f lis r31,1
10003490: d0 02 00 f0 xxspltib vs0,0
10003494: 00 00 c0 3b li r30,0
10003498: 00 00 00 60 nop
1000349c: 00 1c ff 63 ori r31,r31,7168
100034a0: 00 00 00 60 nop
100034a4: f0 c7 22 39 addi r9,r2,-14352
100034a8: 78 fb e3 7f mr r3,r31
100034ac: 28 c8 e2 fb std r31,-14296(r2)
100034b0: 05 00 09 f4 stxv vs0,0(r9)
100034b4: 15 00 09 f4 stxv vs0,16(r9)
100034b8: 00 00 00 60 nop
100034bc: 10 c8 c2 fb std r30,-14320(r2)
100034c0: 29 6a 07 48 bl 10079ee8 <__libc_malloc+0x8>
next prev parent reply other threads:[~2023-03-04 10:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 11:58 [Bug target/109007] New: " bugreporter66 at gmail dot com
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 [this message]
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-VkgqNh9iSL@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).