Volatile modifier variable

Volatile affects compiler compilation results. It is pointed out that volatile variables may change at any time. computation related to volatile variables should not be optimized to avoid errors, (VC ++ will compile and optimize the release executable code, and the computation related to variables with the volatile keyword will not be compiled and optimized .).

For example:

Volatile int I = 10;

Int J = I;

...

Int K = I;

Volatile tells the compiler that I may change at any time and must be read from the address of I each time it is used, therefore, the executable code generated by the compiler will re-read data from the I address and put it in K.

The optimization method is because the compiler finds that the data is read from I twiceCodeThe Code does not perform operations on I, and it will automatically put the last read data in K. Instead of reading from I again. In this way, if I is a register variable or indicates that data on a port is prone to errors, volatile can ensure stable access to special addresses without errors.

/**********************

A variable defined as volatile means that this variable may be unexpectedly changed, so that the compiler will not assume the value of this variable.Precisely, the optimizer must carefully re-read the value of this variable every time when using this variable, rather than using the backup stored in the register. The following are examples of volatile variables:

1) Hardware registers of parallel devices (for example, Status Registers)

2) An Interrupted service subaccountProgramNon-automatic variables that will be accessed in)

3) variables shared by several tasks in multi-threaded applications

I think this is the most basic problem to distinguish between C programmers and embedded system programmers. Embedded people often deal with hardware, interruptions, RTOS, etc. All of these require volatile variables. If you do not know volatile content, it will lead to disasters. If the subject correctly answers this question (well, I suspect it will be the case), I will go a little deeper to see if this guy understands the full importance of volatile.

1) can a parameter be const or volatile? Explain why.

2) can a pointer be volatile? Explain why.

3); what are the following function errors:

Int square (volatile int * PTR)

{

Return * PTR ** PTR;

}

The answer is as follows:

1) Yes. One example is read-only status registers. It is volatile because it may be unexpectedly changed. It is const because the program should not try to modify it.

2) Yes. Although this is not very common. One example is when a service subroutine repairs a pointer to a buffer.

3) This code is a little abnormal. The purpose of this Code is to return the pointer * PTR points to the square of the value. However, since * PTR points to a volatile parameter, the compiler will generate code similar to the following:

Int square (volatile int * PTR)

{

Int A, B;

A = * PTR;

B = * PTR;

Return a * B;

}

* The value of * PTR may be unexpectedly changed, so a and B may be different. As a result, this Code may not return the expected square value! The correct code is as follows:

Long square (volatile int * PTR)

{

Int;

A = * PTR;

Return a *;

}

Bit manipulation)

//*********************

The keyword volatile is often used in embedded programming. The usage of volatile can be summarized as follows:

I. Tell compiler not to perform any Optimization

For example, to send two commands to a specific address:

Int * IP =...; // device address

* IP = 1; // The First Command

* IP = 2; // The Second instruction.

The compiler program above may be optimized:

Int * IP = ...;

* IP = 2;

The first command is lost. If volatile is used, compiler will not allow any optimization, so as to ensure the program's original intention:

Volatile int * IP = ...;

* IP = 1;

* IP = 2;

Even if you want compiler to optimize it, it will not convert the two payment statements into one. It can only perform other optimizations. This is useful to device driver programmers.

2: variables defined with volatile will be changed outside the program. Each time they are read from the memory, they cannot be reused in the cache or register.

For example, volatile char;

A = 0;

While (! A ){

// Do some things;

}

Doother ();

If there is no volatile doother (), it will not be executed.

Original article:

Http://www.cnblogs.com/chio/archive/2007/11/24/970632.html