>> return conf->last_used = new_disk;
>>
>> (new_disk is a local variable, conf is a function arg.)
>
> Since new_disk is on the stack, is there something about 'conf'
> that guarenetes it is not on the stack too? F.e. what if
> &conf->last_used were one byte into 'new_disk' or something
> like that.
It could -- I had thought the -fno-strict-aliasing option
meant exactly the opposite of what it really means. Since the
compiler has been told to be pessimistic about possibilities
like this maybe that's what it has to do.
------
Chuck