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/94998] GCC 10 won't configure for host=x86, build!=host, linker=bfd due to CET
Date: Tue, 12 May 2020 17:42:34 +0000 [thread overview]
Message-ID: <bug-94998-4-EiW3WNhrsN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94998-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94998
--- Comment #5 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:d17cdc17c90ce77cb90c569322c1f241d3530cec
commit r11-333-gd17cdc17c90ce77cb90c569322c1f241d3530cec
Author: H.J. Lu <hjl.tools@gmail.com>
Date: Tue May 12 10:39:42 2020 -0700
Enable CET in cross compiler if possible
Don't perform CET run-time check for host when cross compiling. Instead,
enable CET in cross compiler if possible so that it will run on both CET
and non-CET hosts.
config/
PR bootstrap/94998
* cet.m4 (GCC_CET_HOST_FLAGS): Enable CET in cross compiler if
possible.
libiberty/
PR bootstrap/94998
* configure: Regenerated.
lto-plugin/
PR bootstrap/94998
* configure: Regenerated.
next prev parent reply other threads:[~2020-05-12 17:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 8:40 [Bug bootstrap/94998] New: " harald at gigawatt dot nl
2020-05-08 8:44 ` [Bug target/94998] " harald at gigawatt dot nl
2020-05-08 11:17 ` hjl.tools at gmail dot com
2020-05-08 11:28 ` [Bug bootstrap/94998] " rguenth at gcc dot gnu.org
2020-05-08 13:11 ` hjl.tools at gmail dot com
2020-05-08 17:02 ` harald at gigawatt dot nl
2020-05-12 17:42 ` cvs-commit at gcc dot gnu.org [this message]
2020-05-12 17:50 ` hjl.tools at gmail dot com
2020-06-22 8:50 ` slyfox at inbox dot ru
2020-06-22 8:55 ` rguenth at gcc dot gnu.org
2020-06-22 12:09 ` [Bug bootstrap/94998] [10 Regression] " cvs-commit at gcc dot gnu.org
2020-06-22 12:10 ` hjl.tools at gmail dot com
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-94998-4-EiW3WNhrsN@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).