When should the volatile and dregister modifier be used

Question

Please answer in C/C++/Java context :)

Answer 1

volatile qualifier always a good idea when reading or writing hardware registers, because it ensures that each access you perform in your C code actually shows up in the generated code.

Usually prefer to write macros like this

#define READ_LCDCW1() ...  
#define WRITE_LCDCW1(value) ...

LCDCW1 i Some registers require a multi-step process to read from the hardware.
the simplest definitions should be:

#define LCDCW1_ADDR 0xc000  
#define READ_LCDCW1()  (*(volatile uint32_t *)LCDCW1_ADDR)
#define WRITE_LCDCW1(val)   ((*(volatile uint32_t *)LCDCW1_ADDR) = (val))

Answer 2

The volatile modifier is a directive to the compiler’s optimizer that operations involving this variable should not be optimized in certain ways. There are two special cases in which use of the volatile modifier is desirable. The first case involves memory-mapped hardware (a device such as a graphics adaptor that appears to the computer’s hardware as if it were part of the computer’s memory), and the second involves shared memory (memory used by two or more programs running simultaneously).

Answer 3

The volatile modifier is a directive to the compiler’s optimizer that operations involving this variable should not be optimized in certain ways. There are two special cases in which use of the volatile modifier is desirable. The first case involves memory-mapped hardware (a device such as a graphics adaptor that appears to the computer’s hardware as if it were part of the computer’s memory), and the second involves shared memory (memory used by two or more programs running simultaneously).

The register modifier hints to the compiler that the variable will be heavily used and should be kept in the CPU’s registers, if possible, so that it can be accessed faster.