removed "volatile" from OutputBufferChunk properties
There is no danger that gcc will optimize access to OutputBufferChunk properties, since decoder and player work in different chunk objects. It is safe to remove "volatile" here. git-svn-id: https://svn.musicpd.org/mpd/trunk@7318 09075e82-0dd4-0310-85a5-a0d7c8717e4f
This commit is contained in:
parent
b0e47fce09
commit
159fb3803b
|
@ -33,9 +33,9 @@
|
|||
#define CHUNK_SIZE 1020
|
||||
|
||||
typedef struct _OutputBufferChunk {
|
||||
volatile mpd_uint16 chunkSize;
|
||||
volatile mpd_uint16 bitRate;
|
||||
volatile float times;
|
||||
mpd_uint16 chunkSize;
|
||||
mpd_uint16 bitRate;
|
||||
float times;
|
||||
char data[CHUNK_SIZE];
|
||||
} OutputBufferChunk;
|
||||
|
||||
|
|
Loading…
Reference in New Issue