Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Development mailing list

Subject: Re: [OMPI devel] u_int8_t
From: Eugene Loh (eugene.loh_at_[hidden])
Date: 2011-01-11 14:05:52


Jeff Squyres wrote:

>Shrug. If they're not used anywhere, I'd whack them.
>
>
Excellent. They screw things up (at least for me). Turns out, Solaris
IB uses such types and has the sense to typedef them. But such typedefs
conflict with opal_config.h, which #define's them (for apparently no
reason).

>Do we have configure tests for them, or just #define's?
>
>
Configure tests.

>On Jan 10, 2011, at 7:51 PM, Eugene Loh wrote:
>
>
>>Why do
>> u_int8_t
>> u_int16_t
>> u_int32_t
>> u_int64_t
>>get defined in opal_config.h? I don't see them used anywhere in the OMPI/OPAL/ORTE code base.
>>
>>Okay, one exception, in opal/util/if.c:
>>
>>#if defined(__DragonFly__)
>>#define IN_LINKLOCAL(i) (((u_int32_t)(i) & 0xffff0000) == 0xa9fe0000)
>>#endif
>>
>>
Ah, and even this one exception you got rid of in r22869.