> I suppose we could use memcmp on the as variable itself, to inspect > the actual stored padding rather than the returned copy of it.
Yes, that's probably the only safe stance when optimization is enabled. -- Eric Botcazou
Eric Botcazou via Gcc-patches Mon, 31 Oct 2022 10:03:38 -0700
> I suppose we could use memcmp on the as variable itself, to inspect > the actual stored padding rather than the returned copy of it.
Yes, that's probably the only safe stance when optimization is enabled. -- Eric Botcazou