Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: Re: [OMPI devel] u_int8_t
From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2011-01-10 20:23:14

Shrug. If they're not used anywhere, I'd whack them.

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

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
> _______________________________________________
> devel mailing list
> devel_at_[hidden]

Jeff Squyres
For corporate legal information go to: