public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/105073] New: [meta bug]Patch pending for GCC13. Date: Mon, 28 Mar 2022 05:01:55 +0000 [thread overview] Message-ID: <bug-105073-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105073 Bug ID: 105073 Summary: [meta bug]Patch pending for GCC13. Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: crazylht at gmail dot com Target Milestone: --- This metabug is used to track all the patches which have been written during Stage 3 of GCC 12 but do not qualify for that stage, and are waiting for Stage 1 of GCC 13 to be applied. Please, do not attach patches to this bug. Open a new bug report, and mark it as "blocking" this metabug (this metabug will "depend" on the new bug report).
next reply other threads:[~2022-03-28 5:01 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-28 5:01 crazylht at gmail dot com [this message] 2022-03-28 7:02 ` [Bug target/105073] " ubizjak at gmail dot com 2022-04-29 11:33 ` ubizjak at gmail dot com 2022-05-03 16:03 ` ubizjak at gmail dot com 2022-05-09 11:01 ` crazylht at gmail dot com 2022-05-11 7:36 ` crazylht at gmail dot com 2022-05-16 23:09 ` hjl.tools at gmail dot com 2022-05-17 1:35 ` crazylht at gmail dot com 2022-05-18 8:06 ` crazylht at gmail dot com 2022-05-18 8:33 ` crazylht at gmail dot com 2022-07-28 18:54 ` hjl.tools at gmail dot com
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-105073-4@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).