public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/103735] [12 Regression] Extra glibc "make check" failures by r12-4764 Date: Mon, 27 Dec 2021 13:40:17 +0000 [thread overview] Message-ID: <bug-103735-4-VQZ1Psz4P3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103735-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103735 H.J. Lu <hjl.tools at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |MOVED --- Comment #3 from H.J. Lu <hjl.tools at gmail dot com> --- Moved to https://sourceware.org/bugzilla/show_bug.cgi?id=28713
prev parent reply other threads:[~2021-12-27 13:40 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-15 14:32 [Bug c/103735] New: [12 Regression] Extra glibc "make check" failures hjl.tools at gmail dot com 2021-12-15 19:47 ` [Bug middle-end/103735] " pinskia at gcc dot gnu.org 2021-12-16 14:20 ` hjl.tools at gmail dot com 2021-12-16 18:15 ` [Bug middle-end/103735] [12 Regression] Extra glibc "make check" failures by r12-4764 hjl.tools at gmail dot com 2021-12-27 13:40 ` hjl.tools at gmail dot com [this message]
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-103735-4-VQZ1Psz4P3@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).