public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joel at jms dot id.au" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/105325] New: power10: Error: operand out of range
Date: Thu, 21 Apr 2022 05:14:45 +0000 [thread overview]
Message-ID: <bug-105325-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105325
Bug ID: 105325
Summary: power10: Error: operand out of range
Product: gcc
Version: 11.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: joel at jms dot id.au
Target Milestone: ---
Created attachment 52839
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52839&action=edit
prepocessed source
When building a C++ application
(https://github.com/the-OpenROAD-Project/openROAD/) with -mcpu=power10, the
assembler fails:
as -v -I /home/joel/dev/OpenROAD/include -I /usr/include/tcl -I
/home/joel/dev/OpenROAD/src/rcx/src/../include -I
/home/joel/dev/OpenROAD/src/odb/include -I
/home/joel/dev/OpenROAD/src/utl/include -I
/home/joel/dev/OpenROAD/src/odb/include/odb -I
/home/joel/dev/OpenROAD/src/odb/src/def/def -I
/home/joel/dev/OpenROAD/src/odb/src/def/defzlib -I
/home/joel/dev/OpenROAD/src/odb/src/lef/lef -I
/home/joel/dev/OpenROAD/src/odb/src/lef/lefzlib -I
/home/joel/dev/OpenROAD/src/sta/include -a64 -mpower10 -many -mlittle -o
CMakeFiles/rcx.dir/extmain.cpp.o CMakeFiles/rcx.dir/extmain.cpp.s
/tmp/cc5ook6I.s: Assembler messages:
/tmp/cc5ook6I.s:15503: Error: operand out of range (0x0000000000031b60 is not
between 0xffffffffffff8000 and 0x0000000000007ffc)
/tmp/cc5ook6I.s:15585: Error: operand out of range (0x0000000000031b60 is not
between 0xffffffffffff8000 and 0x0000000000007ffc)
/tmp/cc5ook6I.s:15956: Error: operand out of range (0x0000000000031b60 is not
between 0xffffffffffff8000 and 0x0000000000007ffc)
The full command line is attached.
Building the attached preprocessed source with -O1, 2, 3 shows the issue:
c++ -mcpu=power10 -O3 -c extmain.cpp.ii
Building at -O0 or with no -O option does not reproduce:
c++ -mcpu=power10 -c extmain.cpp.ii
Building with -mcpu=power9 does not reproduce:
c++ -mcpu=power9 -O3 -c extmain.cpp.ii
Versions:
GNU C++17 (Ubuntu 11.2.0-7ubuntu2) version 11.2.0 (powerpc64le-linux-gnu)
compiled by GNU C version 11.2.0, GMP version 6.2.1, MPFR version
4.1.0, MPC version 1.2.0, isl version isl-0.24-GMP
GNU assembler version 2.37 (powerpc64le-linux-gnu) using BFD version (GNU
Binutils for Ubuntu) 2.37
The distro is Ubuntu 21.10, running on a ppc64le machine.
next reply other threads:[~2022-04-21 5:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 5:14 joel at jms dot id.au [this message]
2022-04-21 5:15 ` [Bug c++/105325] " joel at jms dot id.au
2022-04-21 9:21 ` [Bug target/105325] " marxin at gcc dot gnu.org
2022-04-21 9:38 ` joel at jms dot id.au
2022-04-21 9:48 ` marxin at gcc dot gnu.org
2022-04-21 10:08 ` linkw at gcc dot gnu.org
2022-04-21 10:26 ` marxin at gcc dot gnu.org
2022-04-21 10:53 ` marxin at gcc dot gnu.org
2022-04-21 11:03 ` marxin at gcc dot gnu.org
2022-04-21 11:42 ` jakub at gcc dot gnu.org
2022-04-22 8:17 ` linkw at gcc dot gnu.org
2022-04-26 13:40 ` segher at gcc dot gnu.org
2022-04-28 23:05 ` segher at gcc dot gnu.org
2023-01-26 22:54 ` acsawdey at gcc dot gnu.org
2023-03-21 4:01 ` meissner at gcc dot gnu.org
2023-04-18 13:47 ` bergner at gcc dot gnu.org
2023-04-26 6:55 ` rguenth at gcc dot gnu.org
2023-04-27 16:00 ` bergner at gcc dot gnu.org
2023-04-27 16:05 ` bergner at gcc dot gnu.org
2023-06-23 15:37 ` cvs-commit at gcc dot gnu.org
2023-07-05 16:46 ` cvs-commit at gcc dot gnu.org
2023-07-05 18:09 ` cvs-commit at gcc dot gnu.org
2023-07-05 19:50 ` cvs-commit at gcc dot gnu.org
2023-07-05 19:53 ` meissner 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-105325-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).