public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "wilson at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/91602] GCC fails to build for riscv in a combined tree due to misconfigured leb128 support Date: Mon, 19 Jul 2021 14:40:43 +0000 [thread overview] Message-ID: <bug-91602-4-ijvVVtkio3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-91602-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91602 --- Comment #14 from Jim Wilson <wilson at gcc dot gnu.org> --- I posted a patch but didn't get a review, and then got distracted by other stuff and failed to follow up. https://gcc.gnu.org/pipermail/gcc-patches/2020-January/539461.html
next prev parent reply other threads:[~2021-07-19 14:40 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-91602-4@http.gcc.gnu.org/bugzilla/> 2021-07-16 8:06 ` belyshev at depni dot sinp.msu.ru 2021-07-16 8:24 ` jakub at gcc dot gnu.org 2021-07-19 14:40 ` wilson at gcc dot gnu.org [this message] 2021-07-21 14:59 ` belyshev at depni dot sinp.msu.ru 2021-08-20 21:29 ` cvs-commit at gcc dot gnu.org 2021-08-20 21:34 ` belyshev at depni dot sinp.msu.ru
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-91602-4-ijvVVtkio3@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).