This is the mail archive of the fortran@gcc.gnu.org mailing list for the GNU Fortran project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Are complex*16 variables static by default?

From: Jerry DeLisle <jvdelisle at charter dot net>
To: Steffen Boerm <sb at informatik dot uni-kiel dot de>, fortran at gcc dot gnu dot org
Date: Fri, 27 Jan 2017 15:19:36 -0800
Subject: Re: Are complex*16 variables static by default?
Authentication-results: sourceware.org; auth=none
References: <4acd98cf-3ac5-7dec-7c9e-6457210508d2@informatik.uni-kiel.de>

On 01/27/2017 02:46 PM, Steffen Boerm wrote:


Hello,

how are complex*16 variables handled by gfortran if "-frecursive" is
not specified?

Is it possible that they are stored as static variables?

I am using LAPACK's zlarfg and zlarf functions within a C program, and
my code works just fine as long as OpenMP is disabled. When I enable
multi-threading, the code behaves erratically, and I am wondering
whether this might be due to the complex*16 constants "one" and "zero"
in zlarf or the complex*16 variable "temp" in zgerc.


I am not the best person to answer this.

I am doubtful LAPACK is thread safe. I think you need to force single threadthrough execution of those functions.

We may need more information. Have you asked on comp.lang.fortran. It would bemore appropriate to ask your question there.


Jerry

Follow-Ups:
- Re: Are complex*16 variables static by default?
  - From: Janne Blomqvist

References:
- Are complex*16 variables static by default?
  - From: Steffen Boerm

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]