public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/113507] can't build a cross compiler to rs6000-ibm-aix7.2
Date: Tue, 23 Jan 2024 06:31:27 +0000	[thread overview]
Message-ID: <bug-113507-4-svFhrkIhrr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113507-4@http.gcc.gnu.org/bugzilla/>

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

Kewen Lin <linkw at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
                 CC|                            |segher at gcc dot gnu.org
   Last reconfirmed|                            |2024-01-23
     Ever confirmed|0                           |1

--- Comment #5 from Kewen Lin <linkw at gcc dot gnu.org> ---
(In reply to H.J. Lu from comment #3)
> (In reply to Kewen Lin from comment #2)
> > Guessing /usr/local/bin/ld is a gnu ld? Based on what I heard before, gnu ld
> > has some problems on aix, people pass object files to aix system and use aix
> > ld there. Not sure if the understanding still holds.
> 
> I am building a cross compiler.  No AIX tools are involved.

Thanks for clarifying, I was dull and misunderstood it.

Confirmed, some symbols are from rs6000-builtin.cc (which is not generated) but
it requires some symbols in rs6000-builtins.cc (which is generated). Both
object files are not included in linking. The below diff can fix it:

diff --git a/gcc/config.gcc b/gcc/config.gcc
index b2d7d7dd475..6b62e4fe56c 100644
--- a/gcc/config.gcc
+++ b/gcc/config.gcc
@@ -557,8 +557,10 @@ rs6000*-*-*)
         extra_options="${extra_options} g.opt fused-madd.opt
rs6000/rs6000-tables.opt"
         extra_objs="rs6000-string.o rs6000-p8swap.o rs6000-logue.o"
         extra_objs="${extra_objs} rs6000-call.o rs6000-pcrel-opt.o"
+        extra_objs="${extra_objs} rs6000-builtin.o rs6000-builtins.o"
         target_gtfiles="$target_gtfiles
\$(srcdir)/config/rs6000/rs6000-logue.cc
\$(srcdir)/config/rs6000/rs6000-call.cc"
         target_gtfiles="$target_gtfiles
\$(srcdir)/config/rs6000/rs6000-pcrel-opt.cc"
+        target_gtfiles="$target_gtfiles ./rs6000-builtins.h"
         ;;
 sparc*-*-*)
         cpu_type=sparc

According to David's comments "rs6000-ibm-aix doesn't exist any more" and I
vaguely remembered Segher also mentioned rs6000*-*-*) becomes stale, maybe we
can aggressively drop the whole rs6000*-*-*) case handling?

  parent reply	other threads:[~2024-01-23  6:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-19 17:56 [Bug target/113507] New: " hjl.tools at gmail dot com
2024-01-20  8:46 ` [Bug target/113507] " pinskia at gcc dot gnu.org
2024-01-22  3:29 ` linkw at gcc dot gnu.org
2024-01-22 12:53 ` hjl.tools at gmail dot com
2024-01-23  3:11 ` dje at gcc dot gnu.org
2024-01-23  6:31 ` linkw at gcc dot gnu.org [this message]
2024-02-26 11:46 ` linkw at gcc dot gnu.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-113507-4-svFhrkIhrr@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).