On Thu, 11 Mar 2010, Kirk, Benjamin (JSC-EG311) wrote:
> tangential issue - did you find that ACX_TLS and is it sufficient to just
> throw TLS in front of a variable to make it so?
Rhys Ulerich pointed me to it, IIRC. I'm afraid I haven't tested it
myself yet (I just rebuilt to use threads yest
tangential issue - did you find that ACX_TLS and is it sufficient to just
throw TLS in front of a variable to make it so?
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, f
On Thu, 11 Mar 2010, Derek Gaston wrote:
> I thought we had decided a while ago that we weren't going to
> upgrade to the newest Getpot. There were more than a few reasons...
> but the killer is the license. It says you can't use it for
> government purposes!
Well, "military" purposes or some
On Thu, 11 Mar 2010, Kirk, Benjamin (JSC-EG311) wrote:
>> Not quite - an idea which part isn't thread-safe? I thought that the
>> only issue was the buffer for char*, and that declaring it as
>> thread-local-storage was enough to fix it.
>
> see _requested_arguments, _requested_variables, _reque
> Nope. We do all parsing and command-line stuff up front... stuffing into our
> own data structures for later use.
>
> We're not crazy like you re-reading the input-file DURING a solve so you
> can change parameters on the fly ;-)
I admit I still do that, but mostly I just like to say
Real
>> title says it all
>
> Not quite - an idea which part isn't thread-safe? I thought that the
> only issue was the buffer for char*, and that declaring it as
> thread-local-storage was enough to fix it.
see _requested_arguments, _requested_variables, _requested_sections
it keeps an internal log
On Mar 11, 2010, at 11:39 AM, Kirk, Benjamin (JSC-EG311) wrote:
> title says it all - derek, do you guys make calls to getpot inside threaded
> functions?
Nope. We do all parsing and command-line stuff up front... stuffing into our
own data structures for later use.
We're not crazy like you...
On Thu, 11 Mar 2010, Kirk, Benjamin (JSC-EG311) wrote:
> title says it all
Not quite - an idea which part isn't thread-safe? I thought that the
only issue was the buffer for char*, and that declaring it as
thread-local-storage was enough to fix it.
---
Roy
-
title says it all - derek, do you guys make calls to getpot inside threaded
functions?
I'm looking into what this is gonna take to fix this - not sure what the new
getpot has bought us except more restrictive licensing, memory leaks, and a
general headache?
-Ben
