Paolo Bonzini writes:
> Il 11/05/2013 00:58, Anthony Liguori ha scritto:
>> Aurelien Jarno writes:
>>
>>> On Fri, May 10, 2013 at 01:47:55PM -0500, Anthony Liguori wrote:
Most QOM types use type_register_static but we still strdup the
passed data. However, the original pointers are u
Il 11/05/2013 00:58, Anthony Liguori ha scritto:
> Aurelien Jarno writes:
>
>> On Fri, May 10, 2013 at 01:47:55PM -0500, Anthony Liguori wrote:
>>> Most QOM types use type_register_static but we still strdup the
>>> passed data. However, the original pointers are useful because
>>> GCC is pretty
On Fri, May 10, 2013 at 05:58:23PM -0500, Anthony Liguori wrote:
> Aurelien Jarno writes:
>
> > On Fri, May 10, 2013 at 01:47:55PM -0500, Anthony Liguori wrote:
> >> Most QOM types use type_register_static but we still strdup the
> >> passed data. However, the original pointers are useful becaus
Aurelien Jarno writes:
> On Fri, May 10, 2013 at 01:47:55PM -0500, Anthony Liguori wrote:
>> Most QOM types use type_register_static but we still strdup the
>> passed data. However, the original pointers are useful because
>> GCC is pretty good about collapsing strings so its very likely any
>>
On Fri, May 10, 2013 at 01:47:55PM -0500, Anthony Liguori wrote:
> Most QOM types use type_register_static but we still strdup the
> passed data. However, the original pointers are useful because
> GCC is pretty good about collapsing strings so its very likely any
> use of the pointer will end up
Most QOM types use type_register_static but we still strdup the
passed data. However, the original pointers are useful because
GCC is pretty good about collapsing strings so its very likely any
use of the pointer will end up being that same address.
IOW, with a little trickery, we can compare typ
