Linux SPARSE checker discussions
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: Morten Welinder <terra@gnome.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [PATCH] Fix warnings from gcc 4.1.1
Date: Tue, 11 Jul 2006 03:03:36 -0400	[thread overview]
Message-ID: <1152601416.29932.63.camel@dv> (raw)
In-Reply-To: <20060710191359.27AACC000E4@dunnock.rentec.com>

On Mon, 2006-07-10 at 15:13 -0400, Morten Welinder wrote:
> > Indeed, that's a bug number 26632:
> > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26632
> > Nobody is arguing that it's a feature.
> 
> That's a bit too optimistic in my reading.  As I read it, they
> want to keep the warning for explicit casts, but drop it for
> casts that the gcc front end decides to insert itself.

Now I understand why 27825 is a duplicate of 26632!

> I'm sure they mean well, but this warning is getting in the way
> of lots of people doing stuff with macros.

OK, I didn't search well enough.  This issue is bug 24900, which is
marked "WONTFIX".  It's interesting that the statement expression is
proposed as a workaround - exactly what Linus did!

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24900

The argument that statement expressions are not portable has been
ignored so far.

-- 
Regards,
Pavel Roskin

      reply	other threads:[~2006-07-11  7:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-08  6:00 [PATCH] Fix warnings from gcc 4.1.1 Pavel Roskin
2006-07-08 18:14 ` 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 [this message]

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=1152601416.29932.63.camel@dv \
    --to=proski@gnu.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=terra@gnome.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