[OpenAFS-devel] Disposing of non-64bit environment code

[omalleys@msu.edu]

I thought the plan was to keep the "obsolete" systems in the 1.4  
branch and take them out of the 1.6 release. I don't recall exactly  
about 1.5.x. off the top of my head..

Is this not the case?


Quoting Steve Simmons <scs@umich.edu>:

> On Sep 26, 2010, at 5:09 PM, Simon Wilkinson wrote:
>
>> According to the settings in config/param.h we have a very, very  
>> small number of configuration settings which don't set the  
>> AFS_64BIT_ENV define...
>>
>> These are:
>>
>> sun4_413
>> sub4x_55
>> sunx86_54
>> *_nbsd15
>> *_nbsd16
>>
>> Does anyone still care about these platforms, or can we get rid of  
>> the AFS_64BIT_ENV code?
>
> No interest here; none of them are in use in any systems we support.  
> There may be a few clients out there in the field, but they seem to  
> be perfectly happy running an obsolete AFS version on their obsolete  
> OS version.
>
>> Second question...
>>
>> Even on 64 bit platforms, afs_hyper_t uses two 32 bit values to  
>> represent an 64 bit value. Do we still need to do this (the && 0  
>> which disables this dates back to IBM days)?
>
> Nuke 'me._______________________________________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-devel
>