public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/104829] [12 Regression] Pure 32-bit PowerPC build broken Date: Mon, 07 Mar 2022 21:57:59 +0000 [thread overview] Message-ID: <bug-104829-4-0aT4NnzUKe@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104829-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104829 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2022-03-07 Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- .
next prev parent reply other threads:[~2022-03-07 21:57 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-07 21:56 [Bug target/104829] New: " segher at gcc dot gnu.org 2022-03-07 21:56 ` [Bug target/104829] " segher at gcc dot gnu.org 2022-03-07 21:57 ` [Bug target/104829] [12 Regression] " pinskia at gcc dot gnu.org 2022-03-07 21:57 ` pinskia at gcc dot gnu.org [this message] 2022-03-08 21:38 ` bergner at gcc dot gnu.org 2022-03-10 10:06 ` segher at gcc dot gnu.org 2022-03-10 10:24 ` sebastian.huber@embedded-brains.de 2022-03-10 14:14 ` segher at gcc dot gnu.org 2022-03-10 15:39 ` joseph at codesourcery dot com 2022-03-10 16:23 ` bergner at gcc dot gnu.org 2022-03-10 16:26 ` jsm28 at gcc dot gnu.org 2022-03-10 16:27 ` jsm28 at gcc dot gnu.org 2022-03-10 16:43 ` segher at gcc dot gnu.org 2022-03-10 16:55 ` segher at gcc dot gnu.org 2022-03-10 19:44 ` joseph at codesourcery dot com 2022-03-10 21:16 ` bergner at gcc dot gnu.org 2022-03-10 23:40 ` segher at gcc dot gnu.org 2022-03-11 0:04 ` joseph at codesourcery dot com 2022-03-12 16:03 ` cvs-commit at gcc dot gnu.org 2022-03-12 16:09 ` segher at gcc dot gnu.org 2022-06-20 20:25 ` cvs-commit at gcc dot gnu.org 2022-06-20 20:41 ` cvs-commit 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-104829-4-0aT4NnzUKe@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).