From: Mitchell Blank Jr <mitch@sfgoth.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: sparse segfaults
Date: Sun, 21 Nov 2004 15:43:30 -0800 [thread overview]
Message-ID: <20041121234330.GA28381@gaz.sfgoth.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0411212343340.17752@yvahk01.tjqt.qr>
Jan Engelhardt wrote:
> >Actually, this is documented gcc behaviour,[...]
> >you can do
> > int tickadj = *ptr++ ? : 1;
> >and it's well-behaved in that it increments the pointer only once.
>
> And it's specific to GCC. This kinda ruins some tries to get ICC working on the
> kernel tree :)
By ICC do you mean the Intel compiler? It's supported the GCC Extension
"Conditionals with Omitted Operands" since at least version 5.0.1. See:
http://www.intel.com/software/products/compilers/c50/linux/comp501.pdf
-Mitch
next prev parent reply other threads:[~2004-11-21 23:42 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
2004-11-21 22:37 ` Linus Torvalds
2004-11-21 22:44 ` Jan Engelhardt
2004-11-21 23:43 ` Mitchell Blank Jr [this message]
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=20041121234330.GA28381@gaz.sfgoth.com \
--to=mitch@sfgoth.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@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