public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Tsukasa OI <research_trasio@irq.a4lg.com>,
	Nick Clifton <nickc@redhat.com>, Jan Beulich <jbeulich@suse.com>
Cc: binutils@sourceware.org
Subject: [PATCH v3 0/1] bfd, binutils, gas: Remove/mark unused variables
Date: Thu, 15 Sep 2022 12:46:51 +0000	[thread overview]
Message-ID: <cover.1663245322.git.research_trasio@irq.a4lg.com> (raw)
In-Reply-To: <cover.1663215243.git.research_trasio@irq.a4lg.com>

Hello,

PATCH v1:
<https://sourceware.org/pipermail/binutils/2022-September/122865.html>
PATCH v2:
<https://sourceware.org/pipermail/binutils/2022-September/122873.html>

It "removes" unused variables in bfd, binutils and gas.

[Changes: v2 -> v3]
-   Actually removed some but not all variables
    (instead of adding ATTRIBUTE_UNUSED)

Thanks,
Tsukasa




Tsukasa OI (1):
  bfd, binutils, gas: Remove/mark unused variables

 bfd/elf32-lm32.c      | 2 +-
 bfd/elf32-nds32.c     | 3 ---
 bfd/mmo.c             | 2 +-
 binutils/windmc.c     | 4 +---
 gas/config/tc-riscv.c | 3 ---
 ld/pe-dll.c           | 9 ++-------
 6 files changed, 5 insertions(+), 18 deletions(-)


base-commit: fe39ffdc202f04397f31557f17170b40bc42b77a
-- 
2.34.1


  parent reply	other threads:[~2022-09-15 12:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-15  3:09 [PATCH 0/1] bfd, binutils, gas: Mark " Tsukasa OI
2022-09-15  3:09 ` [PATCH 1/1] " Tsukasa OI
2022-09-15  4:17 ` [PATCH 0/1] " Tsukasa OI
2022-09-15  4:17   ` [PATCH 1/1] " Tsukasa OI
2022-09-15  7:29     ` Jan Beulich
2022-09-15  8:25       ` Tsukasa OI
2022-09-15 23:10         ` Hans-Peter Nilsson
2022-09-15 12:46   ` Tsukasa OI [this message]
2022-09-15 12:46     ` [PATCH v3 1/1] bfd, binutils, gas: Remove/mark " Tsukasa OI
2022-09-15 12:58       ` Jan Beulich
2022-09-20 12:50       ` Nick Clifton
2022-09-21  5:54         ` Tsukasa OI
2022-09-21  6:15           ` Jan Beulich
2022-09-21  9:55           ` Nick Clifton

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=cover.1663245322.git.research_trasio@irq.a4lg.com \
    --to=research_trasio@irq.a4lg.com \
    --cc=binutils@sourceware.org \
    --cc=jbeulich@suse.com \
    --cc=nickc@redhat.com \
    /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).