If you saw Mellanox's commit this morning, you noticed a comment about how the
glibc malloc hooks are deprecated. I pinged Mike D. about this off-list, and
he sent me the following reference from the glibc 2.14 release notes at
http://sourceware.org/ml/libc-alpha/2011-05/msg00103.html:
* T
On 6/10/13 8:23 AM, "Jeff Squyres (jsquyres)" wrote:
>If you saw Mellanox's commit this morning, you noticed a comment about
>how the glibc malloc hooks are deprecated. I pinged Mike D. about this
>off-list, and he sent me the following reference from the glibc 2.14
>release notes at
>http://so
On Sat, Jun 08, 2013 at 12:28:02PM +0200, George Bosilca wrote:
> All Windows objects that are managed as HANDLES can easily be modified to
> have static initializer. A clean solution is attached to the question at
> stackoverflow:
> http://stackoverflow.com/questions/3555859/is-it-possible-to-do
On Jun 10, 2013, at 17:18 , Nathan Hjelm wrote:
> On Sat, Jun 08, 2013 at 12:28:02PM +0200, George Bosilca wrote:
>> All Windows objects that are managed as HANDLES can easily be modified to
>> have static initializer. A clean solution is attached to the question at
>> stackoverflow:
>> http:/
On Jun 10, 2013, at 10:29 AM, "Barrett, Brian W" wrote:
> At least they've finally come to that conclusion. I look forward to not
> shipping a memory allocator with our communication library ;).
+1 on that.
That being said, that release note was for glibc 2.14. I just downloaded and
built 2
