comp.lang.ada
 help / color / mirror / Atom feed
From: Per Sandberg <per.sandberg@bredband.net>
Subject: Re: Memory leak in BLAS/LINPACK - GNAT on OS X
Date: Sat, 19 Apr 2008 08:57:10 +0200
Date: 2008-04-19T08:57:10+02:00	[thread overview]
Message-ID: <480997C6.3030004@bredband.net> (raw)
In-Reply-To: <7fa5fc26-6843-4000-bea7-f8a956b20b3f@2g2000hsn.googlegroups.com>

Thought it i recognized this problem so i checked it out and found:
It is  corrected in the Latest GNATPro version (the problem is in the 
compiler).

/Per

tkrauss wrote:
> There have been a few messages on the GNAT-OSX mailing list about an
> apparent memory leak in the Ada.Numerics.Long_Real_Arrays
> implementation.   The setup is an OS X box (10.4) with the GNAT 4.3
> compiler from the macada.org site.  The Ada.Numerics.Long_Real_Arrays
> is using the Apple-supplied BLAS and LINPACK libraries under the
> hood.  The code snippet below (plagiarized from Jerry's post on the
> mailing list) leaks memory (as reported by top).  Note that the same
> code but with Long_Complex types does not appear to have this problem.
> 
> Has anyone seen this problem on other platforms?  Do other languages
> on OS X behave this way?  I'm not sure how to track down the guilty
> party here.  Is it Apple's BLAS or LINPACK libraries or something in
> the GNAT Long_Real_Arrays multiply method?
> 
> 
> with Ada.Numerics.Long_Real_Arrays;
> use Ada.Numerics.Long_Real_Arrays;
> 
> procedure tst_simple is
>   v        : Real_Vector(1 .. 100_000) := (others => 1.23);
>   res      : Real_Vector(1 .. 100_000);
> begin
>   for i in 1..1000 loop
>     res := 123.456 * v;
>   end loop;
> end tst_simple;
> 



  parent reply	other threads:[~2008-04-19  6:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-16 23:06 Memory leak in BLAS/LINPACK - GNAT on OS X tkrauss
2008-04-18 21:43 ` Jerry
2008-04-18 21:43 ` Jerry
2008-04-19  6:57 ` Per Sandberg [this message]
2008-04-19 22:08   ` Jerry
2008-04-19 22:12   ` Jerry
replies disabled

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox