public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/107120] [13 Regression] trunk fails to bootstrap on powerpc64le-linux-gnu
Date: Mon, 03 Oct 2022 09:26:21 +0000 [thread overview]
Message-ID: <bug-107120-4-Q7KMKEvG8y@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107120-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107120
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2022-10-03
Status|UNCONFIRMED |WAITING
CC| |marxin at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Should be fixed with r13-2932-ga5a9237e2a78a9, can you confirm that?
next prev parent reply other threads:[~2022-10-03 9:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-02 9:01 [Bug bootstrap/107120] New: " doko at gcc dot gnu.org
2022-10-03 9:26 ` marxin at gcc dot gnu.org [this message]
2022-10-03 18:19 ` [Bug bootstrap/107120] " asolokha at gmx dot com
2022-10-06 9:55 ` rguenth at gcc dot gnu.org
2022-10-10 4:37 ` asolokha at gmx dot com
2022-10-24 8:42 ` doko 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-107120-4-Q7KMKEvG8y@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).