On Fri, 8 Oct 1999, Tom Lane wrote:
>Bruce Momjian <maillist@candle.pha.pa.us> writes:
>> New code in Makefile.alpha is:
>
>> /* some platforms define __alpha, but not __alpha__ */
>> #if defined(__alpha) && !defined(__alpha__)
>> #define __alpha__
>> #endif
>
>OK, so we're going to standardize on __alpha__ to recognize that
>platform? OK by me, unless the Alpha users know a reason not to.
I don't see any. The only problem I can see is that __alpha (or __alpha__)
used to mean "Alpha/Tru64 Unix", and this is no longer true because of
Alpha/Linux. If there is any place in the code that's valid only for
Alpha/Tru64, then __osf__ should be used.
For example, s_lock.h uses the msem_xxx functions to implement spinlocks
when gcc is not used. These functions are related to msemaphores, which
are semaphores that live in shared memory segments (or "mmap"ed files). I
don't know wheter this group of functions is specific to Tru64 Unix, but
at least FreeBSD doesn't have them. If Alpha/Linux doesn't have them, then
__osf__ should be used there instead of __alpha__ (or at least a
combination of both).
Regards,
Pedro.
--
-------------------------------------------------------------------
Pedro José Lobo Perea Tel: +34 91 336 78 19
Centro de Cálculo Fax: +34 91 331 92 29
E.U.I.T. Telecomunicación e-mail: pjlobo@euitt.upm.es
Universidad Politécnica de Madrid
Ctra. de Valencia, Km. 7 E-28031 Madrid - España / Spain
