From: David Edelsohn <dje.gcc@gmail.com>
To: Martin Liska <mliska@suse.cz>, Jakub Jelinek <jakub@redhat.com>,
Iain Sandoe <iain@sandoe.co.uk>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Disable -fsplit-stack support on non-glibc targets
Date: Tue, 25 Jan 2022 10:27:22 -0500 [thread overview]
Message-ID: <CAGWvnykefRCy=c6aa6cwaS9f6FF+kh_5U3A4sVVFDe6U2ojkGA@mail.gmail.com> (raw)
This patch broke bootstrap on AIX. It may have broken Darwin. I have
applied the following patch. AIX doesn't need to distinguish between
different Linux libc implementations.
Bootstrapped on powerpc-ibm-aix7.2.3.0
Thanks, David
aix: AIX is not GLIBC.
A recent patch added tests for OPTION_GLIBC that is defined in
linux.h and linux64.h. This broke bootstrap for non-Linux rs6000
configurations. This patch defines OPTION_GLIBC as 0.
* config/rs6000/aix.h (OPTION_GLIBC): Define as 0.
diff --git a/gcc/config/rs6000/aix.h b/gcc/config/rs6000/aix.h
index ad3238bf09a..eb7a0c09f72 100644
--- a/gcc/config/rs6000/aix.h
+++ b/gcc/config/rs6000/aix.h
@@ -23,6 +23,7 @@
#define DEFAULT_ABI ABI_AIX
#undef TARGET_AIX
#define TARGET_AIX 1
+#define OPTION_GLIBC 0
next reply other threads:[~2022-01-25 15:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 15:27 David Edelsohn [this message]
2022-01-28 19:25 ` Iain Sandoe
-- strict thread matches above, loose matches on Subject: below --
2021-12-18 10:43 soeren
2021-12-18 10:54 ` Andrew Pinski
2021-12-18 11:13 ` Sören Tempel
2021-12-18 11:22 ` Andrew Pinski
2022-01-22 9:32 ` Martin Liška
2022-01-22 9:35 ` Jakub Jelinek
2022-01-22 12:16 ` Jakub Jelinek
2022-01-22 18:03 ` Jakub Jelinek
2022-01-23 9:06 ` Uros Bizjak
2022-01-23 10:06 ` Jakub Jelinek
2022-01-24 9:33 ` Jakub Jelinek
2022-01-24 10:09 ` Richard Biener
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='CAGWvnykefRCy=c6aa6cwaS9f6FF+kh_5U3A4sVVFDe6U2ojkGA@mail.gmail.com' \
--to=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iain@sandoe.co.uk \
--cc=jakub@redhat.com \
--cc=mliska@suse.cz \
/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).