"The order of volatile accesses is undefined in this statement" 경고문

기술노트 99411

아키텍처:

All

컴포넌트:

compiler

업데이트:

2018-02-28 오전 1:48

Introduction

The message below is issued if 2 (or more) of the variables in a C statement are volatile.

Warning[Pa082]: undefined behavior: the order of volatile accesses is undefined in this statement

The central information the message is the text "...order of volatile accesses is undefined..." . That is, IAR C/C++ Compiler will (as it follows the ISO/ANSI standard) access the variables in an order that is not defined.

Q. Is this a problem , or not?

A. Well that depends on your application.

Volatile is (typically) used for variables that are accessed from several threads in the application, and for Special Function Register that are the connection in/out of the chip. So you must study the volatile variables that are present in this C statement and from the usage of these volatile variables decide if you must make a change or not.

How to change

The change is to break up the C statement, so that each new C statement holds only one access to a volatile variable. In this small example the variables internalChannelSelect and ADC are volatile. If so, the following C source will issue the "Warning[Pa082]".

intAnalogSample[internalChannelSelect] = ADC[internalChannelSelect];

The following change will make the C source predictable. Note that the temporary variables are NOT volatile.

int i;
int k;
i = internalChannelSelect;
k = ADC[i];
intAnalogSample[i] = k;

 

All product names are trademarks or registered trademarks of their respective owners.

죄송하지만, 당사 사이트에서는 Internet Explorer를 지원하지 않습니다.보다 편안한 사이트를 위해 Chrome, Edge, Firefox 등과 같은 최신 브라우저를 사용해 주시길 부탁드립니다.