public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jyong at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/98860] [11 Regression] bootstrap failure on MinGW-w64 windows 10 Date: Tue, 23 Mar 2021 17:59:12 +0000 [thread overview] Message-ID: <bug-98860-4-6TPL0RcBDA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98860-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98860 --- Comment #52 from jyong at gcc dot gnu.org --- Oops I need retest with optimizations enabled to see the debug sections emitted. On the other hand, the new adjusted patch detects the binutils bug fine, tested with new and old binutils.
next prev parent reply other threads:[~2021-03-23 17:59 UTC|newest] Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-27 22:20 [Bug bootstrap/98860] New: boostrap " unlvsur at live dot com 2021-01-27 23:10 ` [Bug bootstrap/98860] " unlvsur at live dot com 2021-01-28 0:34 ` unlvsur at live dot com 2021-01-28 0:49 ` unlvsur at live dot com 2021-01-28 2:35 ` unlvsur at live dot com 2021-01-28 2:40 ` unlvsur at live dot com 2021-01-28 7:39 ` unlvsur at live dot com 2021-01-28 7:41 ` [Bug bootstrap/98860] [11 Regression] " rguenth at gcc dot gnu.org 2021-01-28 8:04 ` unlvsur at live dot com 2021-01-28 8:48 ` unlvsur at live dot com 2021-01-28 9:25 ` unlvsur at live dot com 2021-01-28 9:31 ` jakub at gcc dot gnu.org 2021-01-28 9:32 ` unlvsur at live dot com 2021-01-28 9:36 ` jakub at gcc dot gnu.org 2021-01-28 9:38 ` unlvsur at live dot com 2021-01-28 9:40 ` unlvsur at live dot com 2021-01-28 9:49 ` lh_mouse at 126 dot com 2021-01-28 14:32 ` unlvsur at live dot com 2021-01-28 14:35 ` jakub at gcc dot gnu.org 2021-01-28 15:36 ` unlvsur at live dot com 2021-01-28 15:48 ` unlvsur at live dot com 2021-01-29 3:44 ` lh_mouse at 126 dot com 2021-02-02 12:05 ` ebotcazou at gcc dot gnu.org 2021-02-03 12:56 ` nix at esperi dot org.uk 2021-02-03 15:27 ` nix at esperi dot org.uk 2021-02-03 15:29 ` nix at esperi dot org.uk 2021-02-06 22:08 ` mikpelinux at gmail dot com 2021-02-06 22:14 ` unlvsur at live dot com 2021-02-07 9:19 ` brechtsanders at users dot sourceforge.net 2021-02-07 17:08 ` mikpelinux at gmail dot com 2021-02-07 20:38 ` unlvsur at live dot com 2021-02-08 21:45 ` mikpelinux at gmail dot com 2021-02-09 20:22 ` mikpelinux at gmail dot com 2021-02-09 20:38 ` redi at gcc dot gnu.org 2021-02-09 20:39 ` redi at gcc dot gnu.org 2021-02-16 14:30 ` hjl.tools at gmail dot com 2021-02-26 12:38 ` rguenth at gcc dot gnu.org 2021-02-26 12:48 ` ssbssa at yahoo dot de 2021-02-26 17:55 ` jakub at gcc dot gnu.org 2021-03-01 22:05 ` [Bug bootstrap/98860] [11 Regression] bootstrap " mikpelinux at gmail dot com 2021-03-17 10:42 ` jakub at gcc dot gnu.org 2021-03-17 12:03 ` jyong at gcc dot gnu.org 2021-03-17 12:39 ` jakub at gcc dot gnu.org 2021-03-17 13:05 ` jakub at gcc dot gnu.org 2021-03-18 14:26 ` jyong at gcc dot gnu.org 2021-03-18 14:42 ` jakub at gcc dot gnu.org 2021-03-23 14:02 ` jakub at gcc dot gnu.org 2021-03-23 14:54 ` jyong at gcc dot gnu.org 2021-03-23 15:09 ` jakub at gcc dot gnu.org 2021-03-23 15:43 ` jyong at gcc dot gnu.org 2021-03-23 16:02 ` jakub at gcc dot gnu.org 2021-03-23 16:12 ` jyong at gcc dot gnu.org 2021-03-23 17:12 ` jyong at gcc dot gnu.org 2021-03-23 17:59 ` jyong at gcc dot gnu.org [this message] 2021-03-23 18:16 ` jakub at gcc dot gnu.org 2021-03-23 18:26 ` jakub at gcc dot gnu.org 2021-03-23 18:26 ` jakub at gcc dot gnu.org 2021-03-24 13:44 ` jyong at gcc dot gnu.org 2021-03-24 19:31 ` rogero at howzatt dot co.uk 2021-03-31 7:12 ` cvs-commit at gcc dot gnu.org 2021-03-31 7:13 ` jakub at gcc dot gnu.org 2021-03-31 13:42 ` jyong 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-98860-4-6TPL0RcBDA@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: linkBe 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).