Re: Who uses clapack?

From: Victor Eijkhout (see.sig_at_for.addy)
Date: 12/11/04 

Date: Fri, 10 Dec 2004 23:51:09 -0500

Jentje Goslinga <goslinga@telus.net> wrote:

> No dynamic memory allocation but the eternal WORK and IWORK
> arrays which are partitioned up in intricate ways.
> Does Lapack really need to cater to prehistorical compilers
> which do not support dynamic memory allocation?

Ok, it's clear where this use of temporaries comes from. However, it's
not clear that dynamic allocation is the best solution. If your routine
is called once, with a large dataset, then it could do its own
alloation. However, if the routine is called a large number of times
with the same small problem size, then you want to do the allocation
outside it.

We probably have to take a step back to the application level, and see
which routines can be part of a computationally intensive inner loop.

Your comments very much appreciated.

V. 

-- 
email: lastname at cs utk edu
homepage: www cs utk edu tilde lastname

Relevant Pages

  • Re: Who uses clapack?
    ... > which do not support dynamic memory allocation? ... not clear that dynamic allocation is the best solution. ... if the routine is called a large number of times ... www cs utk edu tilde lastname ...
    (sci.math.num-analysis)
  • Re: Name of a programs library
    ... I do not know the DDNAME that TSO CALL uses for the pgmlib allocation, ... ***routine LOCDEBS locates the DEB for all datasets allocated to the region and saves the addresses in a table along with the DDNAME corresponding to the DEB. ...
    (bit.listserv.ibm-main)
  • segmentation fault caused by allocate memory in a loop?
    ... my guess is that SIGSEGV is caused by memory allocation in a loop. ... Get the variable array jac by subroutine radiance_function, ... IV can be evaluated by the routine DRN2G, ...
    (comp.lang.fortran)
  • Re: Who uses clapack?
    ... > not clear that dynamic allocation is the best solution. ... if the routine is called a large number of times ... in form of an allocatable array*, and the called routined checked whether it ... it would allocate at that proper size. ...
    (sci.math.num-analysis)
  • Re: Crash of dlincg
    ... is not allocation for the return inverse but the working space inside ... the routine itself so allocating that memory a priori isn't going to ... memory for the work arrays outside the routine and pass it by using the ... application to be able to allocate this work space, ...
    (comp.lang.fortran)