From: Tom Tromey <tromey@redhat.com>
To: Aleksandar Ristovski <aristovski@qnx.com>
Cc: "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [patch] cleanup: Wunused corefile.c
Date: Thu, 31 Jan 2013 20:24:00 -0000 [thread overview]
Message-ID: <87vcad5cf1.fsf@fleche.redhat.com> (raw)
In-Reply-To: <510AC74E.1010709@qnx.com> (Aleksandar Ristovski's message of "Thu, 31 Jan 2013 14:34:38 -0500")
>>>>> "Aleksandar" == Aleksandar Ristovski <aristovski@qnx.com> writes:
Aleksandar> In addition to already posted/committed Wunused I have a bunch of
Aleksandar> patches which work around unused vars by adding attribute unused.
You should probably try a --enable-targets=all build if you want to
enable -Wunused in configure...
Aleksandar> Rationale was: either it was unclear whether the assignment
Aleksandar> might have side-effects or there was something that should
Aleksandar> have been done (e.g. this case) with the variable.
Aleksandar> Let me know if this is acceptable approach.
It definitely isn't in this form, and perhaps not in other forms.
First, in this case, the is just buggy. If stat fails, then st.st_mtime
isn't necessarily set, and so the subsequent test is reading garbage.
This is the sort of bug that -Wunused helps to diagnose -- so adding an
attribute to silence the error isn't what we should do.
Second, using __attribute__ unconditionally isn't ok. We can use the
ATTRIBUTE_UNUSED macro; but I would imagine in most cases it would be
better to fix the problem in some other way.
Tom
next prev parent reply other threads:[~2013-01-31 20:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 19:36 Aleksandar Ristovski
2013-01-31 20:24 ` Tom Tromey [this message]
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=87vcad5cf1.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=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