From: terra@gnome.org (Morten Welinder)
To: jeff@garzik.org
Cc: linux-sparse@vger.kernel.org
Subject: Re: [PATCH] sparse: gcc 4.1 warnings
Date: Mon, 10 Apr 2006 09:21:57 -0400 (EDT) [thread overview]
Message-ID: <20060410132157.4AF15C000E2@dunnock.rentec.com> (raw)
In-Reply-To: <20060408041419.GA8943@havoc.gtf.org> (message from Jeff Garzik on Sat, 8 Apr 2006 00:14:19 -0400)
This doesn't look quite right.
So it looks like gcc 4.1 complains over non-used values that are the
result of a cast. That feels obnoxious, but in this case maybe you
could try just casting to void in add_ptr_list -- is the value ever
used?
Morten
next prev parent reply other threads:[~2006-04-10 13:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-08 4:14 [PATCH] sparse: gcc 4.1 warnings Jeff Garzik
2006-04-10 13:21 ` Morten Welinder [this message]
2006-04-11 0:30 ` Jeff Garzik
2006-04-11 8:56 ` Jörn Engel
2006-04-11 9:10 ` Chris Wedgwood
2006-04-11 9:19 ` Jörn Engel
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=20060410132157.4AF15C000E2@dunnock.rentec.com \
--to=terra@gnome.org \
--cc=jeff@garzik.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