Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:10547
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <20040616215849.54272.qmail@pb1.pair.com>
To: internals@lists.php.net
References: <40D07D35.4060602@php.net> <916EFAA7BAA5D5119A7200E0291BBFCC71261E@darwin.journeys.travel>
Date: Wed, 16 Jun 2004 14:58:48 -0700
Lines: 26
Subject: Re: [PHP-DEV] 64 bit safety...
From: pollita@php.net ("Sara Golemon")

>  1. Does that mean PHP on 64-bit is declared not safe for Production
> use?
>
It means it's not as heavily tested as on 32bit platforms :)

>  2. Will it be safe on Linux AMD64, if we compiled PHP with
> CFLAGS="-m32" ?
>
iirc, Linux treats both int and long as 64bit datatypes so it'd be a
non-issue there.  The concern is platforms which treat int and long as
different sizes.  Watch your configure output for:
checking size of long...X
checking size of int...Y

If X and Y are the same you're fine.  If they're different, then any
extension which abuses zend_parse_parameters by using the wrong data types
will have issue.  There's also the possibility that some folks are using
entirely different data types like size_t which can depend on other factors
such as LFS.  The good news is that it doesn't take much to scan through for
problems like that and fix them.

Anyone up for a bugsquash?

-Sara