public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/95940] [11 Regression] sparc64-linux bootstrap with gcc-9.3 broken
Date: Mon, 29 Jun 2020 20:53:29 +0000	[thread overview]
Message-ID: <bug-95940-4-s7WJPNGMyH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95940-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Hans-Peter Nilsson <hp at gcc dot gnu.org> ---
Created attachment 48810
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48810&action=edit
tree-ssanames.ii.gz

Beware, gzippped file.

Repeat with /home/hp/combcheck/o0/./prev-gcc/cc1plus -fpreprocessed
tree-ssanames.ii -quiet -dumpbase tree-ssanames.c -dumpbase-ext .c -mcpu=v9 -g
-gtoggle -O2 -Wextra -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual
-Wno-error=format-diag -Wsuggest-attribute=format -Woverloaded-virtual
-Wpedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Werror
-version -fno-PIE -fno-checking -fno-exceptions -fno-rtti
-fasynchronous-unwind-tables -fno-common -o tree-ssanames.s

(in stage 2)

  parent reply	other threads:[~2020-06-29 20:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-27 11:43 [Bug bootstrap/95940] New: " hp at gcc dot gnu.org
2020-06-29 10:35 ` [Bug bootstrap/95940] [11 Regression] " rguenth at gcc dot gnu.org
2020-06-29 14:48 ` msebor at gcc dot gnu.org
2020-06-29 20:49 ` hp at gcc dot gnu.org
2020-06-29 20:53 ` hp at gcc dot gnu.org [this message]
2020-07-01  7:46 ` [Bug bootstrap/95940] [11 Regression] bootstrap broken by -Wmaybe-unintialized warnings ebotcazou at gcc dot gnu.org
2020-07-02  3:15 ` hp at gcc dot gnu.org
2020-07-02  6:57 ` ebotcazou 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-95940-4-s7WJPNGMyH@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).