Message-ID: <4989AA1C.70300@gmail.com>
Date: Wed, 04 Feb 2009 14:45:48 +0000
From: Dave Korn <dave.korn.cygwin@googlemail.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: "Incompatible" typedefs
References: <1233680809.17414.1298297091@webmail.messagingengine.com> <20090203171556.GB12192@ednor.casa.cgf.cx> <4989511F.4040200@cwilson.fastmail.fm>
In-Reply-To: <4989511F.4040200@cwilson.fastmail.fm>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Charles Wilson wrote:

> I would have thought that these two:
> 
> typedef unsigned int u_int16_t __attribute__ ((__mode__ (__HI__)));
> typedef unsigned short int uint16_t;
> 
> are very different. 

   I wouldn't have.  They're both unsigned, they're both integers, and they're 
both 16 bits.  HImode is the internal GCC type that gets mapped to C short 
ints.  Why do you think they would differ?

> I'm not sure what useful conclusions we can draw from looking at how
> linux does it, Or maybe I just need some sleep.

   I think we just add 'int' where it's missing from longs and long longs and 
we're done.  And there should be a handy test-case to reduce from the octave 
sources.

     cheers,
       DaveK


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/