From: Aleksandar Ristovski <aristovski@qnx.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: [patch] cleanup: Wunused corefile.c
Date: Thu, 31 Jan 2013 19:36:00 -0000 [thread overview]
Message-ID: <510AC74E.1010709@qnx.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 546 bytes --]
Hello,
In addition to already posted/committed Wunused I have a bunch of
patches which work around unused vars by adding attribute unused.
Rationale was: either it was unclear whether the assignment might have
side-effects or there was something that should have been done (e.g.
this case) with the variable.
Let me know if this is acceptable approach.
Thank you,
Aleksandar Ristovski
QNX Software Systems
ChangeLog:
* corefile.c (reopen_exec_file): Add unused attribute to res,
add FIXME comment for future cleanup.
[-- Attachment #2: Wunused-corefile-201301311429.patch --]
[-- Type: text/x-patch, Size: 755 bytes --]
Index: gdb/corefile.c
===================================================================
RCS file: /cvs/src/src/gdb/corefile.c,v
retrieving revision 1.71
diff -u -p -r1.71 corefile.c
--- gdb/corefile.c 14 Jan 2013 21:03:54 -0000 1.71
+++ gdb/corefile.c 30 Jan 2013 22:25:14 -0000
@@ -136,7 +136,7 @@ void
reopen_exec_file (void)
{
char *filename;
- int res;
+ int res __attribute__ ((unused));
struct stat st;
struct cleanup *cleanups;
@@ -149,6 +149,8 @@ reopen_exec_file (void)
cleanups = make_cleanup (xfree, filename);
res = stat (filename, &st);
+ /* FIXME: error checking using 'res' (and remove attribute unused). */
+
if (exec_bfd_mtime && exec_bfd_mtime != st.st_mtime)
exec_file_attach (filename, 0);
else
next reply other threads:[~2013-01-31 19:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 19:36 Aleksandar Ristovski [this message]
2013-01-31 20:24 ` Tom Tromey
2013-01-31 20:29 ` Aleksandar Ristovski
2013-02-01 21:16 ` Tom Tromey
2013-02-01 21:31 ` Aleksandar Ristovski
2013-02-01 21:54 ` Aleksandar Ristovski
2013-02-03 0:05 ` Sergio Durigan Junior
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=510AC74E.1010709@qnx.com \
--to=aristovski@qnx.com \
--cc=gdb-patches@sourceware.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