X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C80509.AAF6684B@onstor-exch02.onstor.net>; Tue, 2 Oct 2007 07:34:06 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: use of atol in our code
Date: Tue, 2 Oct 2007 07:34:07 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E05CB8111@onstor-exch02.onstor.net>
In-Reply-To: <20071001185814.6a9b4b3e@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: use of atol in our code
Thread-Index: AcgEl7J4VTVFwec7SASXdw+0a/DwoAAcYYJQ
References: <BB375AF679D4A34E9CA8DFA650E2B04E05CB7FFD@onstor-exch02.onstor.net> <20071001185814.6a9b4b3e@ripper.onstor.net>
From: "Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>,
	"Jobi Ariyamannil" <jobi.ariyamannil@onstor.com>
Cc: "Jonathan Goldick" <jonathan.goldick@onstor.com>

I would not use atol() anyway regardless of what it returns. According
to the same man page it is deprecated and you can't really check for a
conversion error. I usually convert them to strtol(l) when I see them.

Why would we compile user space to i32lp64 on cougar? We do not have any
use of the pointers that size. Can Linux support mixed mode (kernel 64
bit, user 32 bit)?

>-----Original Message-----
>From: Andy Sharp
>Sent: Monday, October 01, 2007 6:58 PM
>To: Jobi Ariyamannil
>Cc: Maxim Kozlovsky; Jonathan Goldick
>Subject: Re: use of atol in our code
>
>On Mon, 1 Oct 2007 18:38:40 -0700 "Jobi Ariyamannil"
><jobi.ariyamannil@onstor.com> wrote:
>
>> Hi,
>>
>>
>>
>> I see a lot of places we call atol() to initialize 64 bit values.
>>
>> But atol() returns long of size 32 bits.
>
>According to the man page, it returns long, the size of which would be
>target dependent.  I believe we are compiling I32LP64 on the sibytes,
>which would include the management cpu on cougar as well now.  ILP32 on
>the R9K but of course.
>
>Cheers,
>
>a
