From: Kito Cheng <kito.cheng@gmail.com>
To: Kito Cheng <kito.cheng@sifive.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, Jim Wilson <jimw@sifive.com>
Subject: Re: [PATCH 0/2] New target hook TARGET_COMPUTE_MULTILIB and implementation for RISC-V
Date: Fri, 30 Jul 2021 02:44:09 +0800 [thread overview]
Message-ID: <CA+yXCZA1zvCxrLvxicPkpx2UxADbRryUXTd6ubcGp6qWfkhHyA@mail.gmail.com> (raw)
In-Reply-To: <20210721092810.66070-1-kito.cheng@sifive.com>
ping
On Wed, Jul 21, 2021 at 5:28 PM Kito Cheng <kito.cheng@sifive.com> wrote:
>
> This patch set allow target to use customized multi-lib mechanism rather than the built-in
> multi-lib mechanism.
>
> The motivation of this patch is RISC-V might have very complicated multi-lib re-use
> rule*, which is hard to maintain and use current multi-lib scripts,
> we even hit the "argument list too long" error when we tried to add more
> multi-lib reuse rule.
>
> * Here is an example for RISC-V multi-lib rules:
> https://gist.github.com/kito-cheng/0289cd42d9a756382e5afeb77b42b73b
>
> V2 Changes:
> - NO changes for first patch(TARGET_COMPUTE_MULTILIB part) since first version.
> - Handle option other than -march and -mabi for riscv_compute_multilib.
>
>
next prev parent reply other threads:[~2021-07-29 18:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 9:28 Kito Cheng
2021-07-21 9:28 ` [PATCH 1/2] Add TARGET_COMPUTE_MULTILIB hook to override multi-lib result Kito Cheng
2021-09-01 0:16 ` Jim Wilson
2021-07-21 9:28 ` [PATCH 2/2] RISC-V: Implement TARGET_COMPUTE_MULTILIB Kito Cheng
2021-09-01 0:22 ` Jim Wilson
2021-09-01 0:23 ` Jim Wilson
2021-09-16 4:12 ` Kito Cheng
2022-09-09 7:20 ` Andreas Schwab
2022-09-09 9:58 ` Kito Cheng
2021-07-29 18:44 ` Kito Cheng [this message]
2021-07-29 19:00 ` [PATCH 0/2] New target hook TARGET_COMPUTE_MULTILIB and implementation for RISC-V Palmer Dabbelt
2022-09-02 9:28 ` Kito Cheng
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=CA+yXCZA1zvCxrLvxicPkpx2UxADbRryUXTd6ubcGp6qWfkhHyA@mail.gmail.com \
--to=kito.cheng@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jimw@sifive.com \
--cc=kito.cheng@sifive.com \
/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).