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-2847] ranger: remove unused function Date: Mon, 26 Sep 2022 07:31:54 +0000 (GMT) [thread overview] Message-ID: <20220926073154.72C323858CDA@sourceware.org> (raw) https://gcc.gnu.org/g:7ed1a816bab15098e959c249bd0aef8452913223 commit r13-2847-g7ed1a816bab15098e959c249bd0aef8452913223 Author: Martin Liska <mliska@suse.cz> Date: Mon Sep 26 09:30:44 2022 +0200 ranger: remove unused function gcc/ChangeLog: * value-range.cc (tree_compare): Remove unused function. Diff: --- gcc/value-range.cc | 9 --------- 1 file changed, 9 deletions(-) diff --git a/gcc/value-range.cc b/gcc/value-range.cc index 9ca442478c9..754379add19 100644 --- a/gcc/value-range.cc +++ b/gcc/value-range.cc @@ -258,15 +258,6 @@ frange::accept (const vrange_visitor &v) const v.visit (*this); } -// Helper function to compare floats. Returns TRUE if op1 .CODE. op2 -// is nonzero. - -static inline bool -tree_compare (tree_code code, tree op1, tree op2) -{ - return !integer_zerop (fold_build2 (code, integer_type_node, op1, op2)); -} - // Flush denormal endpoints to the appropriate 0.0. void
reply other threads:[~2022-09-26 7:31 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=20220926073154.72C323858CDA@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).