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 jit/94778] All jit tests failed with multilib Date: Fri, 08 May 2020 19:13:52 +0000 [thread overview] Message-ID: <bug-94778-4-dGtAmGOLCn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94778-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94778 H.J. Lu <hjl.tools at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |11.0 Ever confirmed|0 |1 Last reconfirmed| |2020-05-08 Keywords| |patch Status|UNCONFIRMED |NEW URL| |https://gcc.gnu.org/piperma | |il/gcc-patches/2020-May/545 | |425.html --- Comment #1 from H.J. Lu <hjl.tools at gmail dot com> --- A patch is posted at https://gcc.gnu.org/pipermail/gcc-patches/2020-May/545425.html
next prev parent reply other threads:[~2020-05-08 19:13 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-26 19:49 [Bug jit/94778] New: " hjl.tools at gmail dot com 2020-05-08 19:13 ` hjl.tools at gmail dot com [this message] 2020-05-14 23:35 ` [Bug jit/94778] " cvs-commit at gcc dot gnu.org 2020-05-14 23:36 ` 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-94778-4-dGtAmGOLCn@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).