In-Reply-To: <200603261618.30090.rob@landley.net>
References: <200603141619.36609.mmazur@kernel.pl> <1143394195.3055.1.camel@laptopd505.fenrus.org> <4426D609.2050700@argo.co.il> <200603261618.30090.rob@landley.net>
Mime-Version: 1.0 (Apple Message framework v746.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <D83B3618-200F-4D4F-92E4-9EF85CAC8625@mac.com>
Cc: Avi Kivity <avi@argo.co.il>, Arjan van de Ven <arjan@infradead.org>,
       nix@esperi.org.uk, mmazur@kernel.pl, linux-kernel@vger.kernel.org,
       llh-discuss@lists.pld-linux.org
Content-Transfer-Encoding: 7bit
From: Kyle Moffett <mrmacman_g4@mac.com>
Subject: Re: [RFC][PATCH 0/2] KABI example conversion and cleanup
Date: Sun, 26 Mar 2006 19:18:52 -0500
To: Rob Landley <rob@landley.net>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1047
Lines: 25

On Mar 26, 2006, at 16:18:29, Rob Landley wrote:
>>> The problem is things like u64 etc that is VERY common in all  
>>> headers, but then again __u64 etc are just fine, history has  
>>> proven that already.
>>
>> Agree. But to be on the safe side one can use uint64_t and friends  
>> (which the kernel can typedef to u64 and first degree relatives)
>
> Now that the kernel no longer targets gcc before 3.2, c99 names are  
> merely ugly rather than an actual problem. :)

No, they're still a problem in ABI headers because they have defined  
visibility.  A userspace program that does not include <stdint.h>  
will not have those types put in its namespace.  Including <sys/ 
time.h> _cannot_ bring <stdint.> in automatically, that breaks the  
POSIX symbol visibility rules.

Cheers,
Kyle Moffett

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/