From: "Martin Liška" <mliska@suse.cz>
To: soeren@soeren-tempel.net, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Disable -fsplit-stack support on non-glibc targets
Date: Sat, 22 Jan 2022 10:32:21 +0100 [thread overview]
Message-ID: <463eb1a5-bdfb-62e0-023f-d7f9438cf0a4@suse.cz> (raw)
In-Reply-To: <20211218104317.23622-1-soeren@soeren-tempel.net>
Hello.
I've just noticed the patch broke a few cross compilers:
s390x-ibm-tpf:
/home/marxin/buildworker/zen2-cross-compilers/build/gcc/common/config/s390/s390-common.cc: In function ‘bool s390_supports_split_stack(bool, gcc_options*)’:
/home/marxin/buildworker/zen2-cross-compilers/build/gcc/common/config/s390/s390-common.cc:126:13: error: ‘struct gcc_options’ has no member named ‘x_linux_libc’
126 | if (opts->x_linux_libc == LIBC_GLIBC)
| ^~~~~~~~~~~~
i686-kopensolaris-gnu, i686-symbolics-gnu
/home/marxin/buildworker/zen2-cross-compilers/build/gcc/common/config/i386/i386-common.cc: In function ‘bool ix86_supports_split_stack(bool, gcc_options*)’:
/home/marxin/buildworker/zen2-cross-compilers/build/gcc/common/config/i386/i386-common.cc:1721:13: error: ‘struct gcc_options’ has no member named ‘x_linux_libc’
1721 | if (opts->x_linux_libc != LIBC_GLIBC)
| ^~~~~~~~~~~~
make[1]: *** [Makefile:2418: i386-common.o] Error 1
Can you please take a look? Btw. do you have a bugzilla account?
Cheers,
Martin
next prev parent reply other threads:[~2022-01-22 9:32 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
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
2021-12-18 12:19 ` [PATCH v2] " soeren
2022-01-20 20:45 ` Sören Tempel
2022-01-20 22:52 ` Richard Sandiford
2022-01-21 7:32 ` Andreas Krebbel
2022-01-21 8:17 ` Uros Bizjak
2022-01-21 19:16 ` [PATCH v3] " soeren
2022-01-21 19:23 ` Richard Sandiford
2022-01-21 19:47 ` H.J. Lu
2022-01-21 20:09 ` H.J. Lu
2022-01-21 20:18 ` Jakub Jelinek
2022-01-21 21:31 ` [PATCH] x86: Properly disable " H.J. Lu
2022-01-21 21:42 ` Jakub Jelinek
2022-01-21 21:57 ` [PATCH v2] " H.J. Lu
2022-01-21 22:14 ` Jakub Jelinek
2022-01-21 19:53 ` [PATCH v2] Disable " H.J. Lu
2022-01-21 20:43 ` Sören Tempel
2022-01-22 9:32 ` Martin Liška [this message]
2022-01-22 9:35 ` [PATCH] " 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
2022-01-25 15:27 David Edelsohn
2022-01-28 19:25 ` Iain Sandoe
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=463eb1a5-bdfb-62e0-023f-d7f9438cf0a4@suse.cz \
--to=mliska@suse.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=soeren@soeren-tempel.net \
/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).