public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "glaubitz at physik dot fu-berlin.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/108208] Bad assembly? on large LLVM source files on powerpc-unknown-linux-gnu (Error: operand out of range) Date: Mon, 01 Jan 2024 14:01:15 +0000 [thread overview] Message-ID: <bug-108208-4-DzaKdiTFnh@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108208-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108208 --- Comment #8 from John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin.de> --- (In reply to Segher Boessenkool from comment #7) > This PR is for the sysv ABI, while most discussion was about the "ELFv1" ABI. Doesn't the subject clearly mention "powerpc-unknown-linux-gnu"? > Only the 64-bit ABIs have the code model ABI, for the powerpc*-*-* > configurations. > Some other architectures have it for more things, and some for fewer, or > even none. I am trying -O3 now. > If you get an error at line 577996 of a source file, changes are your code > is just > completely unreasonably large, esp. on a smaller target like this :-) I understand. But it's not always possible to change the code size, especially when the code is not mine but some random upstream code. What I don't understand is that other 32-bit architectures don't seem to be affected. For example, hppa-unknown-linux-gnu is not affected. And, secondly, using LLVM as the bootstrap compiler resolves the issue with LLVM for me.
next prev parent reply other threads:[~2024-01-01 14:01 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-23 10:50 [Bug target/108208] New: Build failure on large LLVM source files on PPC sam at gentoo dot org 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 [this message] 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-DzaKdiTFnh@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).