From: terra@gnome.org (Morten Welinder)
To: proski@gnu.org
Cc: linux-sparse@vger.kernel.org
Subject: Re: [PATCH] Fix warnings from gcc 4.1.1
Date: Mon, 10 Jul 2006 15:13:59 -0400 (EDT) [thread overview]
Message-ID: <20060710191359.27AACC000E4@dunnock.rentec.com> (raw)
In-Reply-To: <1152426703.6603.2.camel@dv> (message from Pavel Roskin on Sun, 09 Jul 2006 02:31:43 -0400)
> 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.
I'm sure they mean well, but this warning is getting in the way
of lots of people doing stuff with macros.
M.
next prev parent reply other threads:[~2006-07-10 19:14 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 [this message]
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=20060710191359.27AACC000E4@dunnock.rentec.com \
--to=terra@gnome.org \
--cc=linux-sparse@vger.kernel.org \
--cc=proski@gnu.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