From: Urs Thuermann <urs@isnogud.escape.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [RFC] [PATCH] omnibus header cleanup, certification
Date: 27 Nov 2001 09:32:09 +0100 [thread overview]
Message-ID: <m2bshohawm.fsf@isnogud.escape.de> (raw)
In-Reply-To: <20011127061714.A41881@cantrip.org> <3C03315C.5060203@zytor.com>
In-Reply-To: <3C03315C.5060203@zytor.com>; from "H. Peter Anvin" on Mon, 26 Nov 2001 22:23:24 -0800
"H. Peter Anvin" <hpa@zytor.com> writes:
> It's also worth noting that there is nothing that it can get confused
> with and still have a compilable expression.
Well, there are cases, where -1 and (-1) make a difference (see below)
but these are extremely unlikely to appear in the kernel src code.
Thus, I also think these patches are unnecessary.
For example,
int *p; and int *p
-1[p]; (-1)[p];
are both valid and compilable code segments, with no undefined or
implementation-defined behavior (as long as p points to an element of
an array other than the first and last), and both code segments do
different things.
> I don't believe the unary-expression patches are necessary. They are,
> of course, harmless, except for the fact that my eyes glazed over
> staring at page after page of these, which very few actual potential (!)
> bugs (there were a couple, like the iopage+ ones...)
ack.
urs
next prev parent reply other threads:[~2001-11-27 8:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-27 6:17 [RFC] [PATCH] omnibus header cleanup, certification Nathan Myers
2001-11-27 6:23 ` H. Peter Anvin
2001-11-27 7:14 ` Nathan Myers
2001-11-27 7:16 ` H. Peter Anvin
2001-11-27 8:32 ` Urs Thuermann [this message]
2001-11-27 6:32 ` Ralf Baechle
2001-11-28 20:02 ` David Mosberger
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=m2bshohawm.fsf@isnogud.escape.de \
--to=urs@isnogud.escape.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.