public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/95555] [11 regression] bootstrap build failure starting with r11-959
Date: Mon, 08 Jun 2020 15:07:46 +0000	[thread overview]
Message-ID: <bug-95555-4-JFUym3SNlT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95555-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Martin Sebor <msebor@gcc.gnu.org>:

https://gcc.gnu.org/g:c1057cc0a8ad972e0a2218ab74038a56e5514c39

commit r11-1067-gc1057cc0a8ad972e0a2218ab74038a56e5514c39
Author: Martin Sebor <msebor@redhat.com>
Date:   Mon Jun 8 09:06:48 2020 -0600

    PR bootstrap/95555 - powepc64 bootstrap failure due to
-Wmaybe-uninitialized in reload_cse_simplify_operands

    gcc/ChangeLog:

            * postreload.c (reload_cse_simplify_operands): Clear first array
element
            before using it.  Assert a precondition.

  parent reply	other threads:[~2020-06-08 15:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-05 18:15 [Bug bootstrap/95555] New: " seurer at linux dot vnet.ibm.com
2020-06-05 19:00 ` [Bug bootstrap/95555] " msebor at gcc dot gnu.org
2020-06-05 19:50 ` schwab@linux-m68k.org
2020-06-05 21:07 ` msebor at gcc dot gnu.org
2020-06-05 22:24 ` seurer at linux dot vnet.ibm.com
2020-06-06  7:19 ` schwab@linux-m68k.org
2020-06-06 20:31 ` msebor at gcc dot gnu.org
2020-06-08 15:07 ` cvs-commit at gcc dot gnu.org [this message]
2020-06-08 15:08 ` msebor 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-95555-4-JFUym3SNlT@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).