public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-2495] Document unused function argument
Date: Tue,  6 Sep 2022 11:08:17 +0000 (GMT)	[thread overview]
Message-ID: <20220906110817.8DF8A3858024@sourceware.org> (raw)

https://gcc.gnu.org/g:26ea6ca1fc76752875e74edd628bc3066c642a29

commit r13-2495-g26ea6ca1fc76752875e74edd628bc3066c642a29
Author: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Date:   Tue Sep 6 13:05:21 2022 +0200

    Document unused function argument
    
    This patch fixes a small warning about the unused outer_rtx argument in the
    msp430 backend.
    
    2022-09-06  Jan-Benedict Glaw  <jbglaw@lug-owl.de>
    
    gcc/ChangeLog:
            * config/msp430/msp430.cc (msp430_single_op_cost): Document unused argument.

Diff:
---
 gcc/config/msp430/msp430.cc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/config/msp430/msp430.cc b/gcc/config/msp430/msp430.cc
index 7a378ceac56..6c15780a2b6 100644
--- a/gcc/config/msp430/msp430.cc
+++ b/gcc/config/msp430/msp430.cc
@@ -1460,7 +1460,7 @@ msp430_get_inner_dest_code (rtx x)
 /* Calculate the cost of an MSP430 single-operand instruction, for operand DST
    within the RTX OUTER_RTX, optimizing for speed if SPEED is true.  */
 static int
-msp430_single_op_cost (rtx dst, bool speed, rtx outer_rtx)
+msp430_single_op_cost (rtx dst, bool speed, rtx /* outer_rtx */)
 {
   enum rtx_code dst_code = GET_CODE (dst);
   const struct single_op_cost *cost_p;

                 reply	other threads:[~2022-09-06 11:08 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=20220906110817.8DF8A3858024@sourceware.org \
    --to=jbglaw@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: 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).