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/96203] [11 Regression] LTO bootstrap with --enable-cet is broken
Date: Mon, 27 Jul 2020 11:43:57 +0000 [thread overview]
Message-ID: <bug-96203-4-T9JnTO3x7L@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96203-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96203
--- Comment #17 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:c4c22e830251e1961c6ebec78d28d039eb2e6017
commit r11-2361-gc4c22e830251e1961c6ebec78d28d039eb2e6017
Author: H.J. Lu <hjl.tools@gmail.com>
Date: Thu Jul 16 07:03:27 2020 -0700
LTO: Add -fcf-protection=check
Mixing -fcf-protection and -fcf-protection=none objects are allowed.
Linker just merges -fcf-protection values from all input objects.
Add -fcf-protection=check for the final link with LTO. An error is
issued if LTO object files are compiled with different -fcf-protection
values. Otherwise, -fcf-protection=check is ignored at the compile
time. Without explicit -fcf-protection at link time, -fcf-protection
values from LTO object files are merged at the final link.
gcc/
PR bootstrap/96203
* common.opt: Add -fcf-protection=check.
* flag-types.h (cf_protection_level): Add CF_CHECK.
* lto-wrapper.c (merge_and_complain): Issue an error for
mismatching -fcf-protection values with -fcf-protection=check.
Otherwise, merge -fcf-protection values.
* doc/invoke.texi: Document -fcf-protection=check.
gcc/testsuite/
PR bootstrap/96203
* gcc.target/i386/pr96203-1.c: New test.
* gcc.target/i386/pr96203-2.c: Likewise.
next prev parent reply other threads:[~2020-07-27 11:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 7:21 [Bug bootstrap/96203] New: " rguenth at gcc dot gnu.org
2020-07-15 7:23 ` [Bug bootstrap/96203] " rguenth at gcc dot gnu.org
2020-07-15 7:28 ` cvs-commit at gcc dot gnu.org
2020-07-15 9:05 ` doko at debian dot org
2020-07-15 9:12 ` [Bug bootstrap/96203] [11 Regression] " rguenth at gcc dot gnu.org
2020-07-15 11:35 ` hjl.tools at gmail dot com
2020-07-15 11:40 ` hjl.tools at gmail dot com
2020-07-16 9:28 ` doko at debian dot org
2020-07-16 14:05 ` hjl.tools at gmail dot com
2020-07-16 14:28 ` doko at debian dot org
2020-07-16 14:32 ` hjl.tools at gmail dot com
2020-07-16 21:19 ` hjl.tools at gmail dot com
2020-07-16 21:20 ` hjl.tools at gmail dot com
2020-07-17 7:18 ` rguenth at gcc dot gnu.org
2020-07-17 12:37 ` hjl.tools at gmail dot com
2020-07-17 13:23 ` rguenther at suse dot de
2020-07-17 13:47 ` hjl.tools at gmail dot com
2020-07-27 11:43 ` cvs-commit at gcc dot gnu.org [this message]
2020-07-27 11:45 ` hjl.tools at gmail dot com
2020-09-11 10:21 ` 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-96203-4-T9JnTO3x7L@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).