From: Jan Beulich <jbeulich@suse.com>
To: Tsukasa OI <research_trasio@irq.a4lg.com>
Cc: binutils@sourceware.org, Nick Clifton <nickc@redhat.com>
Subject: Re: [PATCH v3 1/1] bfd, binutils, gas: Remove/mark unused variables
Date: Thu, 15 Sep 2022 14:58:44 +0200 [thread overview]
Message-ID: <7383d0ef-a858-8542-95c6-8be3dcc9ab09@suse.com> (raw)
In-Reply-To: <d0975d800285f61d60cd7c3f47b185304a09a052.1663245322.git.research_trasio@irq.a4lg.com>
On 15.09.2022 14:46, Tsukasa OI wrote:
> Clang generates a warning on unused (technically, written but not read
> thereafter) variables. By the default configuration (with "-Werror"), it
> causes a build failure (unless "--disable-werror" is specified).
>
> This commit adds ATTRIBUTE_UNUSED attribute to some of them, which means
> they are *possibly* unused (can be used but no warnings occur when
> unused) and removes others.
Okay.
Thanks, Jan
next prev parent reply other threads:[~2022-09-15 12:58 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 ` [PATCH v3 0/1] bfd, binutils, gas: Remove/mark " Tsukasa OI
2022-09-15 12:46 ` [PATCH v3 1/1] " Tsukasa OI
2022-09-15 12:58 ` Jan Beulich [this message]
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=7383d0ef-a858-8542-95c6-8be3dcc9ab09@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.com \
--cc=research_trasio@irq.a4lg.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).