public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Richard Sandiford <rsandifo@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-4305] Remove some unused poly_int variables
Date: Thu, 28 Sep 2023 09:51:11 +0000 (GMT)	[thread overview]
Message-ID: <20230928095111.BC92D3858D20@sourceware.org> (raw)

https://gcc.gnu.org/g:46595ce72e5855189e3c60a140c3ca5aaddfb58c

commit r14-4305-g46595ce72e5855189e3c60a140c3ca5aaddfb58c
Author: Richard Sandiford <richard.sandiford@arm.com>
Date:   Thu Sep 28 10:51:01 2023 +0100

    Remove some unused poly_int variables
    
    Switching to default constructors for poly_int exposed some
    unused variables that weren't previously diagnosed.
    
    gcc/
            * dwarf2out.cc (mem_loc_descriptor): Remove unused variables.
            * tree-affine.cc (expr_to_aff_combination): Likewise.
    
    gcc/cp/
            * constexpr.cc (cxx_fold_indirect_ref): Remove unused variables.
    
    gcc/rust/
            * backend/rust-constexpr.cc (rs_fold_indirect_ref): Remove unused
            variables.

Diff:
---
 gcc/cp/constexpr.cc                | 1 -
 gcc/dwarf2out.cc                   | 1 -
 gcc/rust/backend/rust-constexpr.cc | 1 -
 gcc/tree-affine.cc                 | 1 -
 4 files changed, 4 deletions(-)

diff --git a/gcc/cp/constexpr.cc b/gcc/cp/constexpr.cc
index 2a6601c0cbc..0f948db7c2d 100644
--- a/gcc/cp/constexpr.cc
+++ b/gcc/cp/constexpr.cc
@@ -5643,7 +5643,6 @@ cxx_fold_indirect_ref (const constexpr_ctx *ctx, location_t loc, tree type,
 {
   tree sub = op0;
   tree subtype;
-  poly_uint64 const_op01;
 
   /* STRIP_NOPS, but stop if REINTERPRET_CAST_P.  */
   while (CONVERT_EXPR_P (sub) || TREE_CODE (sub) == NON_LVALUE_EXPR
diff --git a/gcc/dwarf2out.cc b/gcc/dwarf2out.cc
index f60a0656d8f..ad2be7c961a 100644
--- a/gcc/dwarf2out.cc
+++ b/gcc/dwarf2out.cc
@@ -15967,7 +15967,6 @@ mem_loc_descriptor (rtx rtl, machine_mode mode,
   enum dwarf_location_atom op;
   dw_loc_descr_ref op0, op1;
   rtx inner = NULL_RTX;
-  poly_int64 offset;
 
   if (mode == VOIDmode)
     mode = GET_MODE (rtl);
diff --git a/gcc/rust/backend/rust-constexpr.cc b/gcc/rust/backend/rust-constexpr.cc
index 4e581a3f2cf..b28fa27b2d0 100644
--- a/gcc/rust/backend/rust-constexpr.cc
+++ b/gcc/rust/backend/rust-constexpr.cc
@@ -737,7 +737,6 @@ rs_fold_indirect_ref (const constexpr_ctx *ctx, location_t loc, tree type,
 {
   tree sub = op0;
   tree subtype;
-  poly_uint64 const_op01;
 
   /* STRIP_NOPS, but stop if REINTERPRET_CAST_P.  */
   while (CONVERT_EXPR_P (sub) || TREE_CODE (sub) == NON_LVALUE_EXPR
diff --git a/gcc/tree-affine.cc b/gcc/tree-affine.cc
index ee327e63a23..ecab4671ab4 100644
--- a/gcc/tree-affine.cc
+++ b/gcc/tree-affine.cc
@@ -268,7 +268,6 @@ expr_to_aff_combination (aff_tree *comb, tree_code code, tree type,
 			 tree op0, tree op1 = NULL_TREE)
 {
   aff_tree tmp;
-  poly_int64 bitpos, bitsize, bytepos;
 
   switch (code)
     {

                 reply	other threads:[~2023-09-28  9:51 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=20230928095111.BC92D3858D20@sourceware.org \
    --to=rsandifo@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).