public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/95413] [11 regression] i686-linux --enable-targets=all cannot configure m64 libgomp
Date: Fri, 29 May 2020 14:25:48 +0000	[thread overview]
Message-ID: <bug-95413-4-lWb4LnHeqA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95413-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95413

--- Comment #4 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to ro@CeBiTec.Uni-Bielefeld.DE from comment #2)
> > How did CET changes add -march=i486 -mtune=i686? Can you bisect to the commit?
> 
> Done: the reghunt identified
> 
> commit 4c1a5d8b71e29b71e0bc1004480c12c5fc427cb7
> Author: H.J. Lu <hjl.tools@gmail.com>
> Date:   Fri May 15 09:06:50 2020 -0700
> 
>     x86: Also check if -fcf-protection works

I can't reproduce it.

  parent reply	other threads:[~2020-05-29 14:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-29 11:56 [Bug bootstrap/95413] New: " ro at gcc dot gnu.org
2020-05-29 11:56 ` [Bug bootstrap/95413] " ro at gcc dot gnu.org
2020-05-29 13:02 ` hjl.tools at gmail dot com
2020-05-29 14:19 ` ro at CeBiTec dot Uni-Bielefeld.DE
2020-05-29 14:24 ` hjl.tools at gmail dot com
2020-05-29 14:25 ` hjl.tools at gmail dot com [this message]
2020-05-29 14:39 ` hjl.tools at gmail dot com
2020-05-29 15:57 ` jakub at gcc dot gnu.org
2020-05-29 17:51 ` hjl.tools at gmail dot com
2020-05-29 18:57 ` ro at CeBiTec dot Uni-Bielefeld.DE
2020-05-29 19:53 ` hjl.tools at gmail dot com
2020-05-29 19:56 ` cvs-commit at gcc dot gnu.org
2020-05-29 19:57 ` 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-95413-4-lWb4LnHeqA@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).