public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tommy_murphy at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/111065] [RISCV] t-linux-multilib specifies incorrect multilib reuse patterns
Date: Sat, 19 Aug 2023 16:32:03 +0000	[thread overview]
Message-ID: <bug-111065-4-vZK8jkPiv9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111065-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111065

--- Comment #6 from Tommy Murphy <tommy_murphy at hotmail dot com> ---
Hi Kito/Palmer - should I maybe close this issue here and take it up in the
riscv-gnu-toolchain/riscv-gcc repos instead? 

* https://github.com/riscv-collab/riscv-gnu-toolchain
* https://github.com/riscv-collab/riscv-gcc

It sounds like the issue of RISC-V multilib specification and management needs
some work and has (at least in the case of the Linux toolchain) diverged from
what was previously intended and what is currently documented with regard to
the multilib-generator script etc.

*
https://github.com/riscv-collab/riscv-gnu-toolchain#installation-newliblinux-multilib

  parent reply	other threads:[~2023-08-19 16:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-18 13:31 [Bug target/111065] New: " tommy_murphy at hotmail dot com
2023-08-18 14:41 ` [Bug target/111065] " kito at gcc dot gnu.org
2023-08-18 16:04 ` tommy_murphy at hotmail dot com
2023-08-18 16:11 ` palmer at gcc dot gnu.org
2023-08-18 16:27 ` kito at gcc dot gnu.org
2023-08-18 21:09 ` tommy_murphy at hotmail dot com
2023-08-19 16:32 ` tommy_murphy at hotmail dot com [this message]
2023-12-31 17:43 ` tommy_murphy at hotmail 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-111065-4-vZK8jkPiv9@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: link
Be 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).