Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures
From: <hidden>
Date: 2007-08-21 22:53:58
Also in:
linux-arch, lkml
Possibly related (same subject, not in this thread)
- 2007-09-11 · Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures · Segher Boessenkool <hidden>
- 2007-09-10 · Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures · Paul E. McKenney <hidden>
- 2007-09-10 · Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures · Christoph Lameter <hidden>
- 2007-09-10 · Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures · Paul E. McKenney <hidden>
- 2007-09-10 · Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures · Kyle Moffett <hidden>
On Tue, 21 Aug 2007 09:16:43 PDT, "Paul E. McKenney" said:
I agree that instant gratification is hard to come by when synching up compiler and kernel versions. Nonetheless, it should be possible to create APIs that are are conditioned on the compiler version.
We've tried that, sort of. See the mess surrounding the whole extern/static/inline/__whatever boondogle, which seems to have changed semantics in every single gcc release since 2.95 or so. And recently mention was made that gcc4.4 will have *new* semantics in this area. Yee. Hah.
Attachments
- (unnamed) [application/pgp-signature] 226 bytes