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/113652] [14/15 regression] Failed bootstrap on ppc unrecognized opcode: `lfiwzx' with -mcpu=7450
Date: Thu, 09 May 2024 09:41:41 +0000	[thread overview]
Message-ID: <bug-113652-4-11z72WsEPY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113652-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113652

--- Comment #26 from Segher Boessenkool <segher at gcc dot gnu.org> ---
(In reply to Michael Meissner from comment #23)
> 1) Ignore it and say to the users don't do that.
> 
> 2) Prevent the IEEE 128-bit libgcc bits from being built on a BE or 32-bit
> LE system unless some configure switch is used.  Or just kick the can down
> the road, and don't provide a configure option in GCC 14, and if people are
> interested do it in GCC 15.
> 
> 3) Only build the IEEE 128-bit libgcc bits if the user configured the
> compiler with --with-cpu=power7, --with-cpu=power8, --with-cpu=power9,
> --with-cpu=power10 (and in the future --with-cpu=power11 or
> --with-cpu=future).  This could be code that if __VSX__ is not defined, the
> libgcc support functions won't get built.  We would then remove the -mvsx
> option from the library support functions.

4) Build those pieces of libgcc with the flags needed for that piece of code.
Like, just as is required for all other code.

  parent reply	other threads:[~2024-05-09  9:41 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-29 13:01 [Bug target/113652] New: ppc: unrecognized opcode: `lfiwzx' csfore at posteo dot net
2024-01-29 13:07 ` [Bug target/113652] [14 regression] Failed bootstrap on ppc unrecognized opcode: `lfiwzx' with -mcpu=7450 rguenth at gcc dot gnu.org
2024-01-29 13:12 ` csfore at posteo dot net
2024-01-29 16:50 ` erhard_f at mailbox dot org
2024-01-29 17:51 ` csfore at posteo dot net
2024-01-29 20:49 ` csfore at posteo dot net
2024-01-30  3:05 ` linkw at gcc dot gnu.org
2024-01-30  3:26 ` linkw at gcc dot gnu.org
2024-01-30  3:44 ` pinskia at gcc dot gnu.org
2024-01-30  6:16 ` [Bug target/113652] " linkw at gcc dot gnu.org
2024-01-30  6:18 ` sjames at gcc dot gnu.org
2024-01-30  6:37 ` linkw at gcc dot gnu.org
2024-01-30  6:59 ` [Bug target/113652] [14 regression] " linkw at gcc dot gnu.org
2024-01-30  8:58 ` linkw at gcc dot gnu.org
2024-02-07 23:15 ` amodra at gmail dot com
2024-02-09  4:21 ` bergner at gcc dot gnu.org
2024-02-12 12:38 ` csfore at posteo dot net
2024-02-15 10:29 ` erhard_f at mailbox dot org
2024-03-27 13:46 ` rguenth at gcc dot gnu.org
2024-03-28 20:37 ` meissner at gcc dot gnu.org
2024-03-29 12:58 ` segher at gcc dot gnu.org
2024-03-29 13:04 ` segher at gcc dot gnu.org
2024-03-29 21:17 ` bergner at gcc dot gnu.org
2024-04-13  4:39 ` meissner at gcc dot gnu.org
2024-05-07  7:44 ` [Bug target/113652] [14/15 " rguenth at gcc dot gnu.org
2024-05-09  3:18 ` bergner at gcc dot gnu.org
2024-05-09  9:41 ` segher at gcc dot gnu.org [this message]
2024-05-09 13:55 ` erhard_f at mailbox dot 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-113652-4-11z72WsEPY@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).