public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <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 11:16:18 +0000	[thread overview]
Message-ID: <bug-108208-4-1xRNQRFyhP@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 #4 from Segher Boessenkool <segher at gcc dot gnu.org> ---
See my previous comment?

You can either write better code, or use -mcmodel=large or similar, accepting
the not-so-stellar generated code you get then.

  parent reply	other threads:[~2024-01-01 11:16 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 [this message]
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-1xRNQRFyhP@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).