public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Thomas Schwinge <tschwinge@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc/devel/rust/master] builtins: Remove unused parameter Date: Sat, 3 Dec 2022 11:49:16 +0000 (GMT) [thread overview] Message-ID: <20221203114916.411B93858C50@sourceware.org> (raw) https://gcc.gnu.org/g:4c66e0f3c105b2ae929d224acadb70b3b95b5333 commit 4c66e0f3c105b2ae929d224acadb70b3b95b5333 Author: Arthur Cohen <arthur.cohen@embecosm.com> Date: Wed Nov 30 12:12:14 2022 +0100 builtins: Remove unused parameter Diff: --- gcc/rust/backend/rust-builtins.cc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gcc/rust/backend/rust-builtins.cc b/gcc/rust/backend/rust-builtins.cc index ee3e42e6b53..ec65026c675 100644 --- a/gcc/rust/backend/rust-builtins.cc +++ b/gcc/rust/backend/rust-builtins.cc @@ -253,7 +253,7 @@ BuiltinsContext::define_builtins () { auto *built_in_attributes = builtin_attributes; auto build_builtin = [this] (built_in_function fn_code, const char *fn_name, - built_in_class fn_class, tree fn_type, bool both, + built_in_class fn_class, tree fn_type, bool fallback, tree attributes, bool implicit) { if (fn_type == error_mark_node) return; @@ -272,7 +272,7 @@ BuiltinsContext::define_builtins () #define DEF_BUILTIN(ENUM, NAME, CLASS, TYPE, LIBTYPE, BOTH_P, FALLBACK_P, \ NONANSI_P, ATTRS, IMPLICIT, COND) \ if (NAME && COND) \ - build_builtin (ENUM, NAME, CLASS, builtin_types[TYPE], BOTH_P, FALLBACK_P, \ + build_builtin (ENUM, NAME, CLASS, builtin_types[TYPE], FALLBACK_P, \ built_in_attributes[ATTRS], IMPLICIT); #include "builtins.def" #undef DEF_BUILTIN
reply other threads:[~2022-12-03 11:49 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=20221203114916.411B93858C50@sourceware.org \ --to=tschwinge@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).