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.
On Mar 13, 2012, at 5:51 AM, Hartmut Kaiser wrote:
> But the problems I was seeing were not MSVC specific. It's a proliferation
> of arcane (non-POSIX) function use (like strcasecmp, etc.) missing use of
> HAVE_UNISTD_H, HAVE_STRINGS_H to wrap non-standard headers, unsafe mixing of
> int32<->int64 data types, reliance on int (and other types) having a certain
> bit-size, totally unsafe shift operations, wide use of (non-C-standard) gcc
> extensions, etc. Should I go on?
Can you send patches?
FWIW, hwloc is working for me with a wide array of POSIX-ish compilers on POSIX-ish platforms (albeit perhaps many of them are quite similar -- 64 bit systems on more-or-less modern-ish hardware). There's quite a degree of portability built in, but if we missed some stuff, well, we're not perfect. :-)
For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/