FWIW, I see at least some GNU-isms in the hwloc code that might be
problematic for embedding hwloc in other code bases that don't use gcc
to compile. E.g., in OMPI, we'd prefer to use the same compiler suite
to compile hwloc that was used to compile OMPI itself (e.g., intel,
PGI, ...etc. -- configuring/building hwloc with icc results in a *lot*
of warnings; I didn't test functionality).
I don't know if we want to target that for v0.9.1 or not -- my first
reaction is to postpone this to v1.0 in order to get v0.9.1 out the
door. Fully bake in all the embedding -- including cleaning up any
potential GNU-isms -- for v1.0.
Pavan -- is it a problem to always compile hwloc with gcc?
On Oct 21, 2009, at 11:39 AM, Pavan Balaji wrote:
On 10/21/2009 10:38 AM, Samuel Thibault wrote:
> Pavan Balaji, le Wed 21 Oct 2009 10:36:33 -0500, a écrit :
>> On 10/21/2009 10:28 AM, Samuel Thibault wrote:
>>> Pavan Balaji, le Wed 21 Oct 2009 09:55:36 -0500, a écrit :
>>>> 1. I see a AC_PROG_CC_C99 in the configure.ac. Do you require the
>>>> compiler to be C99 capable always?
>>> No, we ended up using constructs which should pass c90 and the
compilers
>>> we have tested (aix, solaris, icc).
>> So shouldn't the AC_PROG_CC_C99 be gotten rid of?
>
> No because when C99 is available, we enable some optimization
features,
> like __hwloc_restrict.
Gotcha! Thanks for the clarification.
-- Pavan
--
Pavan Balaji
http://www.mcs.anl.gov/~balaji
_______________________________________________
hwloc-devel mailing list
hwloc-de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-devel
--
Jeff Squyres
jsquy...@cisco.com
