linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Alexey Zaytsev" <alexey.zaytsev@gmail.com>
To: Derek M Jones <derek@knosof.co.uk>
Cc: David Given <dg@cowlark.com>,
	linux-sparse@vger.kernel.org, Josh Triplett <josh@kernel.org>
Subject: Re: [PATCH 2/15 v2] Unhardcode byte size being 8 bits.
Date: Thu, 18 Dec 2008 06:11:13 +0300	[thread overview]
Message-ID: <f19298770812171911u1e7e3cc0i11d33544cd519fea@mail.gmail.com> (raw)
In-Reply-To: <4949ACDF.50209@knosof.co.uk>

On Thu, Dec 18, 2008 at 04:52, Derek M Jones <derek@knosof.co.uk> wrote:
> All,
>
>> I have reported the bug in gcc.  Track Bug: 38563
>> at: gcc.gnu.org/bugzilla
>
> A very prompt response from a gcc maintainer, bug 38563
> is a duplicate of bug 22086.
>
> "This is a GCC extension. sizeof(void) is invalid C and should error out
> and does with -pedantic-errors"
>
> Yuk, who ever thought to use -pedantic-errors!
>
> -ansi or -std=c89 or -std=c99 don't elicit any diagnostics.

I don't really see why you take this as a tragedy. People seem
to like this extension:
linux/linux-2.6$ make -j 8 CC='gcc -Wpointer-arith' 2>&1 | grep
'warning: pointer of type \'void \*\' used in arithmetic' | uniq | wc
-l
45095

And anyway, that's how gcc works, so sparse can only follow.

P.S:
Dear sir, can you imagine, in Russia, they put pieces of lemon
in their tea! And you worry about gcc being wrong.
/humor

  reply	other threads:[~2008-12-18  3:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-17 20:05 [PATCH 2/15 v2] Unhardcode byte size being 8 bits Alexey Zaytsev
2008-12-17 23:33 ` David Given
2008-12-18  0:33   ` Alexey Zaytsev
2008-12-18  0:58     ` David Given
2008-12-18  1:24       ` Alexey Zaytsev
2008-12-18  1:10     ` Derek M Jones
2008-12-18  1:52       ` Derek M Jones
2008-12-18  3:11         ` Alexey Zaytsev [this message]
2008-12-18 13:05           ` Derek M Jones
2008-12-18 17:07             ` Alexey Zaytsev
2008-12-18 17:12 ` David Given

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=f19298770812171911u1e7e3cc0i11d33544cd519fea@mail.gmail.com \
    --to=alexey.zaytsev@gmail.com \
    --cc=derek@knosof.co.uk \
    --cc=dg@cowlark.com \
    --cc=josh@kernel.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;
as well as URLs for NNTP newsgroup(s).