Hello Andrew,

I would prefer if the relevant CFLAG for thread local memory were determined in configure.ac.

Best regards

Heinrich


On 09.01.17, 13:26 Andrew Makhorin <[email protected]> wrote:
Please see an updated version of glpk here:
http://sourceforge.net/projects/noumenon/files/tmp/
(Note that this is *not* an official release.)

The following main changes were made:

1. The option was added to build a stdcall DLL with MSVC10 (for MS
Windows version).

2. The option was added to build a re-entrant version of the package.

A re-entrant version of the package allows running multiple
*independent* instances of glpk in different threads of a multi-threaded
application.

A re-entrant version of the package can be built, for example, with the
following commands:

./configure ...
make CFLAGS="-DTLS=__thread" ...

The storage-class specifier defined by macro TLS depends on the compiler
used. It may be __thread for older versions of gcc, or _Thread_local if
the compiler conforms to C11.

If the application calls glpk routines from multiple threads, the
following should be taken into account:

1) a thread should not access glpk program objects (e.g. glp_proc)
created by other threads;

2) to prevent memory leaks each thread before termination should call
the glpk api routine glp_free_env.


Andrew Makhorin


_______________________________________________
Help-glpk mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/help-glpk
_______________________________________________
Help-glpk mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/help-glpk

Reply via email to