public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth 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: Wed, 15 Jul 2020 09:12:42 +0000 [thread overview]
Message-ID: <bug-96203-4-fA38xOqGMj@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
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|LTO bootstrap with |[11 Regression] LTO
|--enable-cet is broken |bootstrap with --enable-cet
| |is broken
Target Milestone|--- |11.0
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
Arguably the simplest solution is to demote the error to a warning,
--enable-cet
is supposed to only enable CET instrumentation of (part of) the runtime. If
we want to keep the error we'd need to build several variants of libiberty
(in this case). Not sure why libiberty was CET enabled in the first place - is
it used in target libraries?
next prev parent reply other threads:[~2020-07-15 9:12 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 ` rguenth at gcc dot gnu.org [this message]
2020-07-15 11:35 ` [Bug bootstrap/96203] [11 Regression] " 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
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-fA38xOqGMj@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).