public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sam at gentoo dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/108208] New: Build failure on large LLVM source files on PPC
Date: Fri, 23 Dec 2022 10:50:53 +0000 [thread overview]
Message-ID: <bug-108208-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108208
Bug ID: 108208
Summary: Build failure on large LLVM source files on PPC
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: sam at gentoo dot org
Target Milestone: ---
We've seen this a few times in Gentoo when building LLVM, but this is the
latest case.
```
$ gcc --version
gcc (Gentoo 13.0.0_pre20221218 p5) 13.0.0 20221218 (experimental)
Copyright (C) 2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
```
```
/usr/bin/c++ -save-temps -O2 -g -pipe -fsanitize=undefined -std=c++17 -fPIC
-fno-semantic-interposition -fvisibility-inlines-hidden -ffunction-sections
-fdata-sections -fno-exceptions -fno-rtti RegisterInfoEmitter.cpp.ii
[...]
a-RegisterInfoEmitter.cpp.s:577996: Error: operand out of range
(0x0000000000009d8c is not between 0xffffffffffff8000 and 0x0000000000007fff)
a-RegisterInfoEmitter.cpp.s:578007: Error: operand out of range
(0x0000000000009d10 is not between 0xffffffffffff8000 and 0x0000000000007fff)
a-RegisterInfoEmitter.cpp.s:578016: Error: operand out of range
(0x0000000000009d18 is not between 0xffffffffffff8000 and 0x0000000000007fff)
a-RegisterInfoEmitter.cpp.s:578024: Error: operand out of range
(0x0000000000009d14 is not between 0xffffffffffff8000 and 0x0000000000007fff)
a-RegisterInfoEmitter.cpp.s:578042: Error: operand out of range
(0x0000000000009d84 is not between 0xffffffffffff8000 and 0x0000000000007fff)
a-RegisterInfoEmitter.cpp.s:578061: Error: operand out of range
(0x0000000000009d5c is not between 0xffffffffffff8000 and 0x0000000000007fff)
a-RegisterInfoEmitter.cpp.s:578071: Error: operand out of range
(0x0000000000009d68 is not between 0xffffffffffff8000 and 0x0000000000007fff)
[...]
```
I've uploaded gcc-RegisterInfoEmitter-ppc.tar.xz at
https://dev.gentoo.org/~sam/bugs/gcc/gcc-RegisterInfoEmitter-ppc/gcc-RegisterInfoEmitter-ppc.tar.xz
(because of the size of the files) which contains:
```
-rw-r--r-- 1 root root 2.8M Dec 23 10:35
gcc-RegisterInfoEmitter-ppc/RegisterInfoEmitter.cpp.ii
-rw-r--r-- 1 root root 42M Dec 23 10:45
gcc-RegisterInfoEmitter-ppc/a-RegisterInfoEmitter.cpp.s
```
Minimising is hard because it only happens with large source files and it's
also time consuming to compile and get the error.
(Sorry for external link, it's too big even when compressed to attach here, as
it's 4MB.)
next reply other threads:[~2022-12-23 10:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 10:50 sam at gentoo dot org [this message]
2022-12-23 10:57 ` [Bug target/108208] Bad assembly? on large LLVM source files on powerpc-unknown-linux-gnu (Error: operand out of range) sam at gentoo dot org
2022-12-27 12:00 ` marxin at gcc dot gnu.org
2022-12-28 21:24 ` segher at gcc dot gnu.org
2024-01-01 10:42 ` glaubitz at physik dot fu-berlin.de
2024-01-01 11:16 ` segher at gcc dot gnu.org
2024-01-01 11:40 ` glaubitz at physik dot fu-berlin.de
2024-01-01 12:34 ` glaubitz at physik dot fu-berlin.de
2024-01-01 13:41 ` segher at gcc dot gnu.org
2024-01-01 14:01 ` glaubitz at physik dot fu-berlin.de
2024-01-01 14:36 ` segher at gcc dot gnu.org
2024-01-02 20:56 ` glaubitz at physik dot fu-berlin.de
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-108208-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).