From: Nikita Danilov <nikita@clusterfs.com>
To: linux-os@analogic.com
Cc: Linus Torvalds <torvalds@osdl.org>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: sparse segfaults
Date: Mon, 22 Nov 2004 01:29:08 +0300 [thread overview]
Message-ID: <m1brdqn8ej.fsf@clusterfs.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0411211705480.16359@chaos.analogic.com> (linux-os@chaos.analogic.com's message of "Sun, 21 Nov 2004 17:10:59 -0500 (EST)")
linux-os <linux-os@chaos.analogic.com> writes:
> On Sat, 20 Nov 2004, Russell King wrote:
>
[...]
>>
>> int tickadj = 500/HZ ? : 1; /* microsecs */
>>
>> which makes it look like sparse doesn't understand such constructions.
>
> I don't think any 'C' compiler should understand such constructions
> either.
> There is no result for the TRUE condition, and the standard
> does not provide for a default. The compiler should have written
> a diagnostic.
This is GCC extension.
foo ? : bar
is equivalent to
foo ? foo : bar
except that foo is evaluated only once.
Nikita.
next prev parent reply other threads:[~2004-11-21 22:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-20 14:37 sparse segfaults Russell King
2004-11-20 16:58 ` Linus Torvalds
2004-11-20 17:23 ` Russell King
2004-11-21 22:10 ` linux-os
2004-11-21 22:29 ` Nikita Danilov [this message]
2004-11-21 22:37 ` Linus Torvalds
2004-11-21 22:44 ` Jan Engelhardt
2004-11-21 23:43 ` Mitchell Blank Jr
2004-11-22 1:02 ` Linus Torvalds
2004-11-22 10:33 ` Jan Engelhardt
2004-11-22 16:22 ` Linus Torvalds
2004-11-22 18:21 ` Jan Engelhardt
2004-11-22 18:39 ` Mitchell Blank Jr
2004-11-22 18:54 ` Linus Torvalds
2004-11-22 20:30 ` Duncan Sands
2004-11-23 13:59 ` Nix
2004-11-22 19:16 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2005-03-26 22:48 Jan Engelhardt
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=m1brdqn8ej.fsf@clusterfs.com \
--to=nikita@clusterfs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=torvalds@osdl.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