public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/96404] [10 Regression] Bootstrap failure Date: Sat, 01 Aug 2020 15:56:11 +0000 [thread overview] Message-ID: <bug-96404-4-t3P6SnsOwY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96404-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96404 --- Comment #12 from David Edelsohn <dje at gcc dot gnu.org> --- r11-2446 succeeds and r11-2447 fails, so the failure (at least on AIX) is the var-tracking dataflow patch.
next prev parent reply other threads:[~2020-08-01 15:56 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-31 17:43 [Bug bootstrap/96404] New: [10 Regression] AIX Bootstrap failure with DWARF debug changes dje at gcc dot gnu.org 2020-07-31 17:44 ` [Bug bootstrap/96404] " dje at gcc dot gnu.org 2020-07-31 21:05 ` slyfox at gcc dot gnu.org 2020-07-31 21:06 ` slyfox at gcc dot gnu.org 2020-07-31 21:06 ` dje at gcc dot gnu.org 2020-07-31 21:07 ` dje at gcc dot gnu.org 2020-07-31 21:13 ` [Bug bootstrap/96404] [10 Regression] Bootstrap failure slyfox at gcc dot gnu.org 2020-07-31 21:16 ` dje at gcc dot gnu.org 2020-07-31 21:17 ` dje at gcc dot gnu.org 2020-07-31 21:25 ` slyfox at gcc dot gnu.org 2020-07-31 21:32 ` slyfox at gcc dot gnu.org 2020-08-01 1:02 ` dje at gcc dot gnu.org 2020-08-01 11:34 ` dje at gcc dot gnu.org 2020-08-01 15:56 ` dje at gcc dot gnu.org [this message] 2020-08-02 0:34 ` dje at gcc dot gnu.org 2020-08-02 7:53 ` slyfox at gcc dot gnu.org 2020-08-02 10:56 ` slyfox at gcc dot gnu.org 2020-08-02 12:42 ` slyfox at gcc dot gnu.org 2020-08-02 16:45 ` dje at gcc dot gnu.org 2020-08-02 18:37 ` cvs-commit at gcc dot gnu.org 2020-08-02 18:42 ` [Bug bootstrap/96404] [11 " slyfox at gcc dot gnu.org 2020-08-03 7:00 ` rguenth 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-96404-4-t3P6SnsOwY@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).