qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 2/9] tcg: declare __jit_debug_descriptor to be s


From: Jim Meyering
Subject: Re: [Qemu-devel] [PATCH 2/9] tcg: declare __jit_debug_descriptor to be static
Date: Tue, 22 May 2012 12:26:54 +0200

Peter Maydell wrote:
> On 21 May 2012 21:10, Jim Meyering <address@hidden> wrote:
>> Peter Maydell wrote:
>>> On 21 May 2012 20:51, Jim Meyering <address@hidden> wrote:
>>>> From: Jim Meyering <address@hidden>
>>>>
>>>>
>>>> Signed-off-by: Jim Meyering <address@hidden>
>>>> ---
>>>>  tcg/tcg.c | 2 +-
>>>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> diff --git a/tcg/tcg.c b/tcg/tcg.c
>>>> index ab589c7..350fdad 100644
>>>> --- a/tcg/tcg.c
>>>> +++ b/tcg/tcg.c
>>>> @@ -2293,7 +2293,7 @@ void __jit_debug_register_code(void)
>>>>
>>>>  /* Must statically initialize the version, because GDB may check
>>>>    the version before we can set it.  */
>>>> -struct jit_descriptor __jit_debug_descriptor = { 1, 0, 0, 0 };
>>>> +static struct jit_descriptor __jit_debug_descriptor = { 1, 0, 0, 0 };
>>>>
>>>>  /* End GDB interface.  */
>>>
>>> Nak. This symbol is global so that gdb can find it by fishing around
>>> in the executable's symbol table.
>>
>> Thanks for the quick feedback.
>>
>> How does the scope of the symbol affect whether gdb can find it?
>
> If you mark it 'static' the compiler can throw it away or completely
> rearrange it if it's feeling clever enough, I think.
>
> Anyway, we're following a prescribed interface here:
> http://sourceware.org/gdb/onlinedocs/gdb/Declarations.html
>
> and I don't think we should deviate from it. As the comment says,
> "THE FOLLOWING MUST MATCH GDB DOCS.".
>
>> If declaring this variable "static" is not appropriate,
>> then the comment saying that static initialization is desired
>> should be changed.
>
> The comment means "statically initialize this variable rather than
> doing it dynamically in some function at startup".

Thanks.  I've clarified the comments and posted a V2.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]