public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-3473] riscv: fix cross compiler Date: Tue, 25 Oct 2022 05:14:19 +0000 (GMT) [thread overview] Message-ID: <20221025051419.941C33858437@sourceware.org> (raw) https://gcc.gnu.org/g:5a20a4705c960ac323d1fe25f766e1204e0c98bd commit r13-3473-g5a20a4705c960ac323d1fe25f766e1204e0c98bd Author: Martin Liska <mliska@suse.cz> Date: Tue Oct 25 06:58:17 2022 +0200 riscv: fix cross compiler Move riscv_get_valid_option_values out of Fixes: riscv/riscv-common.cc:1748:40: error: ‘riscv_get_valid_option_values’ was not declared in this scope gcc/ChangeLog: * common/config/riscv/riscv-common.cc (riscv_get_valid_option_values): Get out of ifdef. Diff: --- gcc/common/config/riscv/riscv-common.cc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/gcc/common/config/riscv/riscv-common.cc b/gcc/common/config/riscv/riscv-common.cc index 697bfe435c8..dead3802f83 100644 --- a/gcc/common/config/riscv/riscv-common.cc +++ b/gcc/common/config/riscv/riscv-common.cc @@ -1691,6 +1691,10 @@ riscv_compute_multilib ( return xstrdup (multilib_infos[best_match_multi_lib].path.c_str ()); } +#undef TARGET_COMPUTE_MULTILIB +#define TARGET_COMPUTE_MULTILIB riscv_compute_multilib +#endif + vec<const char *> riscv_get_valid_option_values (int option_code, const char *prefix ATTRIBUTE_UNUSED) @@ -1726,10 +1730,6 @@ riscv_get_valid_option_values (int option_code, return v; } -#undef TARGET_COMPUTE_MULTILIB -#define TARGET_COMPUTE_MULTILIB riscv_compute_multilib -#endif - /* Implement TARGET_OPTION_OPTIMIZATION_TABLE. */ static const struct default_options riscv_option_optimization_table[] = {
reply other threads:[~2022-10-25 5:14 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221025051419.941C33858437@sourceware.org \ --to=marxin@gcc.gnu.org \ --cc=gcc-cvs@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).