Linux SPARSE checker discussions
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: linux-sparse@vger.kernel.org
Subject: [PATCH] Fix warnings from gcc 4.1.1
Date: Sat, 08 Jul 2006 02:00:04 -0400	[thread overview]
Message-ID: <20060708060004.20321.50429.stgit@dv.roinet.com> (raw)

From: Pavel Roskin <proski@gnu.org>

These warnings are reported for every file:
lib.h: In function 'add_symbol':
lib.h:171: warning: value computed is not used
lib.h: In function 'add_statement':
lib.h:176: warning: value computed is not used
lib.h: In function 'add_expression':
lib.h:181: warning: value computed is not used

That's the way new versions of gcc warn about values that are cast to a
type but not used.

The cast in add_ptr_list_tag() is not really needed.  Its return value
is used only in one place (add_pseudo) where it's converted to (void *)
anyway.

Signed-off-by: Pavel Roskin <proski@gnu.org>
---

 ptrlist.h |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/ptrlist.h b/ptrlist.h
index b42a0ca..7a786cb 100644
--- a/ptrlist.h
+++ b/ptrlist.h
@@ -46,7 +46,7 @@ extern int linearize_ptr_list(struct ptr
  * extensions..
  */
 #define add_ptr_list_tag(list,entry,tag) \
-	(TYPEOF(*(list))) (CHECK_TYPE(*(list),(entry)),__add_ptr_list((struct ptr_list **)(list), (entry), (tag)))
+	(CHECK_TYPE(*(list),(entry)),__add_ptr_list((struct ptr_list **)(list), (entry), (tag)))
 #define add_ptr_list(list,entry) \
 	add_ptr_list_tag(list,entry,0)
 #define free_ptr_list(list) \

             reply	other threads:[~2006-07-08  6:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-08  6:00 Pavel Roskin [this message]
2006-07-08 18:14 ` [PATCH] Fix warnings from gcc 4.1.1 Linus Torvalds
2006-07-08 20:28   ` Linus Torvalds
2006-07-09  6:31   ` Pavel Roskin
2006-07-10 19:13     ` Morten Welinder
2006-07-11  7:03       ` Pavel Roskin

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=20060708060004.20321.50429.stgit@dv.roinet.com \
    --to=proski@gnu.org \
    --cc=linux-sparse@vger.kernel.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