This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: [PATCH] Re: Gate DSO not building properly?
- From: Matthew Wilcox <willy at debian dot org>
- To: Nick Clifton <nickc at redhat dot com>
- Cc: "H. J. Lu" <hjl at lucon dot org>, Ian Wienand <ianw at gelato dot unsw dot edu dot au>,linux-ia64 at vger dot kernel dot org, binutils at sources dot redhat dot com
- Date: Fri, 24 Oct 2003 13:06:42 +0100
- Subject: Re: [PATCH] Re: Gate DSO not building properly?
- References: <20031021061051.GA5846@cse.unsw.EDU.AU> <20031022034547.GA14783@cse.unsw.EDU.AU> <20031022054813.GA7488@lucon.org> <m3ad7rne3p.fsf@redhat.com>
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