DLLEXPORT symbols may not be specified as threadprivate

DLLEXPORT symbols may not be specified as threadprivate

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.

4 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

It is a Windows restriction. Can't do it in C++ either.

Steve - Intel Developer Support

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?

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.

Steve - Intel Developer Support

Leave a Comment

Please sign in to add a comment. Not a member? Join today