public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gcc at octaforge dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/113174] gcc fails to bootstrap on pp64le with clang-based host environment (internal compiler error)
Date: Sun, 07 Jan 2024 04:24:09 +0000	[thread overview]
Message-ID: <bug-113174-4-EwTR88uBM7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113174-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Daniel Kolesa <gcc at octaforge dot org> ---
I tried an experiment: I canceled the build after initial generation of
insn-recog.cc and patched the offending part with logic from a stage-2
insn-recog.cc I managed to previously capture:

```
--- insn-recog.cc.orig  2024-01-07 04:46:19.328295337 +0100
+++ insn-recog.cc       2024-01-07 04:41:52.025630846 +0100
@@ -41675,11 +41675,12 @@
       break;
     }
   operands[0] = x3;
-  if (!gpc_reg_operand (operands[0], E_SImode)
+  if (GET_CODE (x2) != MEM
       || GET_MODE (x2) != E_SImode)
     return -1;
   x4 = XEXP (x2, 0);
-  if (GET_MODE (x4) != E_SImode)
+  if (GET_CODE (x4) != PLUS
+      || GET_MODE (x4) != E_SImode)
     return -1;
   switch (GET_CODE (x2))
     {
```

This allowed all 3 stages to finish building. It results in lots of failed
comparisons for stage2 and stage3 files though, and is obviously not a workable
solution.

      parent reply	other threads:[~2024-01-07  4:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-29 23:33 [Bug bootstrap/113174] New: " gcc at octaforge dot org
2023-12-29 23:39 ` [Bug bootstrap/113174] " pinskia at gcc dot gnu.org
2023-12-29 23:46 ` pinskia at gcc dot gnu.org
2023-12-29 23:50 ` gcc at octaforge dot org
2023-12-29 23:53 ` gcc at octaforge dot org
2023-12-29 23:59 ` pinskia at gcc dot gnu.org
2023-12-30  0:44 ` gcc at octaforge dot org
2023-12-30 16:06 ` gcc at octaforge dot org
2024-01-07  4:24 ` gcc at octaforge dot org [this message]

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-113174-4-EwTR88uBM7@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).