From: Matthew Wilcox <willy@debian.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] Re: Gate DSO not building properly?
Date: Fri, 24 Oct 2003 12:06:42 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106699727807797@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106679437709356@msgid-missing>
On Fri, Oct 24, 2003 at 11:07:22AM +0100, Nick Clifton wrote:
> > && (attr &~ ssect->attr &~ SHF_MERGE &~ SHF_STRINGS) = 0)
>
> I would appreciate it if you could add a space between the '&' and the
> '~'. These are separate operators and should not be juxtaposed like
> that. I know that this is not part of your original patch, but since
> we are modifying this area of code, I think that it would be a good
> idea to clean this up.
There's two schools of thought on this one ... it really depends how
you prefer to think about it. Myself, I'm used to ARM with its BIC
(BIt Clear) instruction, which I translate to the &~ "operator". I
know some people prefer to think of it as "invert all the bits and mask"
but that's just less intuitive for me.
I'd have more sympathy for the latter view if it could lead to subtle
bugs, but I've been unable to come up with a situation where it makes
a difference. The type promotion rules seem to prevent inadvertent bits
being cleared.
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
next prev parent reply other threads:[~2003-10-24 12:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-22 3:45 [PATCH] Re: Gate DSO not building properly? Ian Wienand
2003-10-22 5:48 ` H. J. Lu
2003-10-22 18:08 ` David Mosberger
2003-10-23 1:52 ` Ian Wienand
2003-10-23 4:56 ` David Mosberger
2003-10-24 10:07 ` Nick Clifton
2003-10-24 12:06 ` Matthew Wilcox [this message]
2003-10-24 12:21 ` Andreas Schwab
2003-10-24 15:15 ` H. J. Lu
2003-10-24 18:27 ` Matthew Wilcox
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=marc-linux-ia64-106699727807797@msgid-missing \
--to=willy@debian.org \
--cc=linux-ia64@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