Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
29274 Discussions

DLLEXPORT symbols may not be specified as threadprivate

stydofe1
Beginner
‎06-21-2011 12:14 PM
635 Views

With IVF12, Can a module variable with dllexport or dllimport attribute be a threadprivate varaible, I tiried this without success. Is it a compiler problem? Thanks.


0 Kudos

Link Copied

3 Replies
Steven_L_Intel1
Employee
‎06-21-2011 12:19 PM
635 Views
It is a Windows restriction. Can't do it in C++ either.
0 Kudos
Copy link
martymike
Novice
‎06-21-2011 01:24 PM
635 Views
Do you know why this restriction is there?

Our app has thousands of exported module variables (I work with syddofe1). Other than the obvious - writing functions to access and change the variables - is there any other strategy you would recommend?
0 Kudos
Copy link
Steven_L_Intel1
Employee
‎06-21-2011 02:43 PM
635 Views
It's just something not implemented in the Microsoft linker and/or image loader. I can't say "why".

Access functions would seem appropriate to me.
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.