public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "doko at debian dot 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: Thu, 16 Jul 2020 14:28:03 +0000	[thread overview]
Message-ID: <bug-96203-4-qUwiuYAGmH@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 #9 from Matthias Klose <doko at debian dot org> ---
Comment on attachment 48881
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48881
Something like this

please could you update gcc/doc/invoke.texi?

is error only supposed to be passed in LDFLAGS, not in CFLAGS? What would be
the semantics if error passed in CFLAGS?

  parent reply	other threads:[~2020-07-16 14:28 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 [this message]
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-qUwiuYAGmH@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).