sim: ppc: workaround uninitialized variable compiler warnings
Some compilers don't understand the semctl API and think it's an input argument even when it's used as an output, and then complains that it is being used uninitialized. Zero it out explicitly to workaround it. This adds some runtime overhead, but should be fairly minor as it's a small stack buffer, and shouldn't be that relevant relative to all the other logic in these functions.
This commit is contained in:
parent
9f17cdda31
commit
92bdeb2888
@ -111,7 +111,7 @@ hw_sem_init_data(device *me)
|
|||||||
hw_sem_device *sem = (hw_sem_device*)device_data(me);
|
hw_sem_device *sem = (hw_sem_device*)device_data(me);
|
||||||
const device_unit *d;
|
const device_unit *d;
|
||||||
int status;
|
int status;
|
||||||
union semun help;
|
union semun help = {};
|
||||||
|
|
||||||
/* initialize the properties of the sem */
|
/* initialize the properties of the sem */
|
||||||
|
|
||||||
@ -190,7 +190,7 @@ hw_sem_io_read_buffer(device *me,
|
|||||||
struct sembuf sb;
|
struct sembuf sb;
|
||||||
int status;
|
int status;
|
||||||
uint32_t u32;
|
uint32_t u32;
|
||||||
union semun help;
|
union semun help = {};
|
||||||
|
|
||||||
/* do we need to worry about out of range addresses? */
|
/* do we need to worry about out of range addresses? */
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user