public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kito Cheng <kito.cheng@sifive.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Kito Cheng via Gcc-patches <gcc-patches@gcc.gnu.org>,
	Kito Cheng <kito.cheng@gmail.com>,
	palmer@dabbelt.com,  jeffreyalaw@gmail.com
Subject: Re: [PATCH v2] RISC-V: Handle multi-lib path correclty for linux
Date: Fri, 12 May 2023 16:59:34 +0800	[thread overview]
Message-ID: <CALLt3Tjn98iJSLfA7KL9BtVvr=xAMgXXgrfSg=+pgs2iTiM37w@mail.gmail.com> (raw)
In-Reply-To: <874joi2bfn.fsf@igel.home>

Apologize for that...

fixed on top of trunk:
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=7a7f6b26259d22115ee4813ce130622ad1073d16

On Fri, May 12, 2023 at 4:36 PM Andreas Schwab <schwab@linux-m68k.org> wrote:
>
> WTF?
>
> ../../gcc/common/config/riscv/riscv-common.cc: In function 'const char* riscv_select_multilib_by_abi(const std::string&, const std::string&, const riscv_subset_list*, const switchstr*, int, const std::vector<riscv_multi_lib_info_t>&)':
> ../../gcc/common/config/riscv/riscv-common.cc:1599:22: error: unused parameter 'riscv_current_arch_str' [-Werror=unused-parameter]
>  1599 |   const std::string &riscv_current_arch_str,
>       |   ~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~
> ../../gcc/common/config/riscv/riscv-common.cc:1601:28: error: unused parameter 'subset_list' [-Werror=unused-parameter]
>  1601 |   const riscv_subset_list *subset_list, const struct switchstr *switches,
>       |   ~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~
> ../../gcc/common/config/riscv/riscv-common.cc:1601:65: error: unused parameter 'switches' [-Werror=unused-parameter]
>  1601 |   const riscv_subset_list *subset_list, const struct switchstr *switches,
>       |                                         ~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~
> ../../gcc/common/config/riscv/riscv-common.cc:1602:7: error: unused parameter 'n_switches' [-Werror=unused-parameter]
>  1602 |   int n_switches, const std::vector<riscv_multi_lib_info_t> &multilib_infos)
>       |   ~~~~^~~~~~~~~~
> ../../gcc/common/config/riscv/riscv-common.cc: In function 'const char* riscv_select_multilib(const std::string&, const std::string&, const riscv_subset_list*, const switchstr*, int, const std::vector<riscv_multi_lib_info_t>&)':
> ../../gcc/common/config/riscv/riscv-common.cc:1613:22: error: unused parameter 'riscv_current_arch_str' [-Werror=unused-parameter]
>  1613 |   const std::string &riscv_current_arch_str,
>       |   ~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~
> cc1plus: all warnings being treated as errors
> make[3]: *** [Makefile:2485: riscv-common.o] Error 1
>
> --
> Andreas Schwab, schwab@linux-m68k.org
> GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
> "And now for something completely different."

      reply	other threads:[~2023-05-12  8:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04  8:01 Kito Cheng
2023-05-08  7:03 ` Kito Cheng
2023-05-12  8:36   ` Andreas Schwab
2023-05-12  8:59     ` Kito Cheng [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='CALLt3Tjn98iJSLfA7KL9BtVvr=xAMgXXgrfSg=+pgs2iTiM37w@mail.gmail.com' \
    --to=kito.cheng@sifive.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.com \
    --cc=kito.cheng@gmail.com \
    --cc=palmer@dabbelt.com \
    --cc=schwab@linux-m68k.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).