[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46CC42EF.3030602@redhat.com>
Date: Wed, 22 Aug 2007 10:06:39 -0400
From: Chris Snook <csnook@...hat.com>
To: Hirokazu Takata <takata@...ux-m32r.org>
CC: linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>,
akpm@...ux-foundation.org, paulmck@...ux.vnet.ibm.com,
Segher Boessenkool <segher@...nel.crashing.org>,
"Luck, Tony" <tony.luck@...el.com>,
Chris Friesen <cfriesen@...tel.com>,
"Robert P. J. Day" <rpjday@...dspring.com>
Subject: Re: [PATCH 11/23] make atomic_read() and atomic_set() behavior consistent
on m32r
Hirokazu Takata wrote:
> I think the parameter of atomic_read() should have "const"
> qualifier to avoid these warnings, and IMHO this modification might be
> worth applying on other archs.
I agree.
> Here is an additional patch to revise the previous one for m32r.
I'll incorporate this change if we get enough consensus to justify a
re-re-re-submit. Since the patch is intended to be a functional no-op on m32r,
I'm inclined to leave it alone at the moment.
> I also tried to rewrite it with inline asm code, but the kernel text size
> bacame roughly 2kB larger. So, I prefer C version.
You're not the only arch maintainer who prefers doing it in C. If you trust
your compiler (a big "if", apparently), inline asm only improves code generation
if you have a whole bunch of general purpose registers for the optimizer to play
with.
-- Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists