Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Alex_K_6
Beginner
77 Views

Atomic.h(16): internal error: access violation occuring on multiple files

Hi all,

Using ICL 13 SP1 Update 5 and Visual Studio 2013 Update 4 I get the following error on multiple files:

C:\Program Files (x86)\Intel\Composer XE 2013 SP1\compiler\include\atomic(16): internal error: access violation
    #include_next <atomic>
                          ^

I've attached the following things:

  • Files this error occurs on
  • Build log
  • Preprocess of those files

There are many more files where the same issue occurs, but too many to include.

Any help would be greatly appreciated!

0 Kudos
3 Replies
Alex_K_6
Beginner
77 Views

An update to this, modifying atomic to the following:

#ifndef __USE_INTEL_ATOMICS
  #if _MSC_VER > 0 && _MSC_VER <= 1800
    #define __USE_INTEL_ATOMICS 1
  #endif
  #if __GNUC__ > 0 && (__GNUC__ < 4 || __GNUC__ == 4 && __GNUC_MINOR__ < 5)
    #define __USE_INTEL_ATOMICS 1
  #endif
  #if defined(__VXWORKS__)
    #define __USE_INTEL_ATOMICS 1
  #endif
#endif

#if __USE_INTEL_ATOMICS
  #include <stdatomic.h>
#else
  #include_next <atomic>
#endif

Changes the issues to being the exact same issue as defined in this previous thread Intel C++ 2013 compatibility issue with VC++11 in <atomic>. The problem is the temporary solution provided there doesn't work, because the error changes from already declared in scope to undefined.

EDIT: Can also confirm this occurs on ICL 15 Update 2

Bernard
Black Belt
77 Views

I am not sure if this is an internal compiler error.

pbkenned1
Employee
77 Views

I can't reproduce any errors or warnings using your pre-processed files.  What's your command line?

C:\ISN_Forums\U545082\Intel Debug>icl -c GenericModule.i plugin-container.i -Qstd=c++11 /TP
Intel(R) C++ Intel(R) 64 Compiler XE for applications running on Intel(R) 64, Version 15.0.2.179 Build 20150121
Copyright (C) 1985-2015 Intel Corporation.  All rights reserved.

GenericModule.i
plugin-container.i

C:\ISN_Forums\U545082\Intel Debug>

 

Patrick

Reply