public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-5231] go: define two builtin functions used by middle-end Date: Tue, 17 Jan 2023 17:05:35 +0000 (GMT) [thread overview] Message-ID: <20230117170535.B843338582BE@sourceware.org> (raw) https://gcc.gnu.org/g:6d80690132a2f00fae1f619d4ffd950ce8cfdbc7 commit r13-5231-g6d80690132a2f00fae1f619d4ffd950ce8cfdbc7 Author: Ian Lance Taylor <iant@golang.org> Date: Tue Jan 17 09:02:49 2023 -0800 go: define two builtin functions used by middle-end PR go/108426 * go-gcc.cc (Gcc_backend::Gcc_backend): Define __builtin_ctzl and __builtin_clzl. Patch by Andrew Pinski. Diff: --- gcc/go/go-gcc.cc | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/gcc/go/go-gcc.cc b/gcc/go/go-gcc.cc index a4a0e5d903e..07c34a58241 100644 --- a/gcc/go/go-gcc.cc +++ b/gcc/go/go-gcc.cc @@ -627,6 +627,11 @@ Gcc_backend::Gcc_backend() unsigned_type_node, NULL_TREE), builtin_const); + this->define_builtin(BUILT_IN_CTZL, "__builtin_ctzl", "ctzl", + build_function_type_list(integer_type_node, + long_unsigned_type_node, + NULL_TREE), + builtin_const); this->define_builtin(BUILT_IN_CTZLL, "__builtin_ctzll", "ctzll", build_function_type_list(integer_type_node, long_long_unsigned_type_node, @@ -637,6 +642,11 @@ Gcc_backend::Gcc_backend() unsigned_type_node, NULL_TREE), builtin_const); + this->define_builtin(BUILT_IN_CLZL, "__builtin_clzl", "clzl", + build_function_type_list(integer_type_node, + long_unsigned_type_node, + NULL_TREE), + builtin_const); this->define_builtin(BUILT_IN_CLZLL, "__builtin_clzll", "clzll", build_function_type_list(integer_type_node, long_long_unsigned_type_node,
reply other threads:[~2023-01-17 17:05 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=20230117170535.B843338582BE@sourceware.org \ --to=ian@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).