public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/104170] [12 Regression] Failed to bootstrap by r12-6807
Date: Fri, 21 Jan 2022 22:36:37 +0000 [thread overview]
Message-ID: <bug-104170-4-pQsoKdDfQg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104170-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104170
--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by H.J. Lu <hjl@gcc.gnu.org>:
https://gcc.gnu.org/g:60953a23d57b13a672f751bec0c6eefc059eb1ab
commit r12-6811-g60953a23d57b13a672f751bec0c6eefc059eb1ab
Author: H.J. Lu <hjl.tools@gmail.com>
Date: Fri Jan 21 13:24:00 2022 -0800
x86: Properly disable -fsplit-stack support on non-glibc targets
Revert x86 changes in
commit c163647ffbc9a20c8feb6e079dbecccfe016c82e
Author: Soren Tempel <soeren@soeren-tempel.net>
Date: Fri Jan 21 19:22:46 2022 +0000
Disable -fsplit-stack support on non-glibc targets
and change ix86_supports_split_stack to return true only on glibc.
PR bootstrap/104170
* common/config/i386/i386-common.cc (ix86_supports_split_stack):
Return true only on glibc.
* config/i386/gnu-user-common.h (STACK_CHECK_STATIC_BUILTIN):
Revert commit c163647ffbc.
* config/i386/gnu.h (TARGET_LIBC_PROVIDES_SSP): Likewise.
next prev parent reply other threads:[~2022-01-21 22:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 20:08 [Bug bootstrap/104170] New: " hjl.tools at gmail dot com
2022-01-21 20:08 ` [Bug bootstrap/104170] " hjl.tools at gmail dot com
2022-01-21 21:32 ` hjl.tools at gmail dot com
2022-01-21 22:36 ` cvs-commit at gcc dot gnu.org [this message]
2022-01-22 0:02 ` hjl.tools at gmail dot com
2022-01-24 10:18 ` cvs-commit 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-104170-4-pQsoKdDfQg@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).