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-2389] nvptx: Silence unused variable warning in output_constant_pool_contents()
Date: Sat,  3 Sep 2022 12:10:50 +0000 (GMT)	[thread overview]
Message-ID: <20220903121050.8FC1D3858418@sourceware.org> (raw)

https://gcc.gnu.org/g:08de065293f8b08158e1089fbacce9dbaba95077

commit r13-2389-g08de065293f8b08158e1089fbacce9dbaba95077
Author: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Date:   Sat Sep 3 14:02:57 2022 +0200

    nvptx: Silence unused variable warning in output_constant_pool_contents()
    
    Similar to the rs6000 code, nvptx defines ASM_OUTPUT_DEF_FROM_DECLS as well as
    ASM_OUTPUT_DEF. Make sure that the define's parameters are used by referencing
    them as (void) to silence a warning in output_constant_pool_contents().
    
    2022-09-30  Jan-Benedict Glaw  <jbglaw@lug-owl.de>
    
    gcc/
            * config/nvptx/nvptx.h (ASM_OUTPUT_DEF): Reference macro arguments.

Diff:
---
 gcc/config/nvptx/nvptx.h | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/gcc/config/nvptx/nvptx.h b/gcc/config/nvptx/nvptx.h
index ed72c253191..71297440566 100644
--- a/gcc/config/nvptx/nvptx.h
+++ b/gcc/config/nvptx/nvptx.h
@@ -321,6 +321,9 @@ struct GTY(()) machine_function
 #define ASM_OUTPUT_DEF(FILE,LABEL1,LABEL2)	\
   do						\
     {						\
+      (void) (FILE);				\
+      (void) (LABEL1);				\
+      (void) (LABEL2);				\
       gcc_unreachable ();			\
     }						\
   while (0)

                 reply	other threads:[~2022-09-03 12:10 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=20220903121050.8FC1D3858418@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).