Re: [PATCH] blktap2: update connection handling to fix build with gcc5

[Olaf Hering <olaf@aepfle.de>]

On Tue, Jul 21, Jan Beulich wrote:

> But anyway, the primary question remains - isn't what you're seeing
> a compiler bug? If yes, that's imo _yet another_ reason for doing a
> minimal workaround (if any at all).

I dont think its a compiler bug. How should the compiler know that the
index variable matches the array size? If the code would modify index
and array all inside the same unit it may have a chance to see that it
can never be above array_size. But as it stands the pointer comes from
outside the unit.

One could argue that the struct is defined just inside that unit and it
gets passed back in as a void pointer. So an optimistic view on the
issue could be: noone knows what "void *p" is all about, so nothing
would touch it. But gcc doesnt work that way. Not sure if it should.

Olaf