Re: [PATCH v3 02/14] Change gdb.base/skip-solib.exp deal with lack of epilogue information

[Pedro Alves <pedro@palves.net>]

On 2022-06-09 19:55, Bruno Larsen wrote:
> 
> On 6/9/22 15:25, Pedro Alves wrote:

>>>> I think that we can use that to write a caching proc like:
>>>>
>>>>    # Return true if the compiler emits line information associating prologue insns with
>>>>    # the function's closing brace.  Return false if not, meaning the prologue
>>>>    # associates prologue instructions with function's last line with a statement.
>>>>
>>>>    gdb_caching_proc have_prologue_line_info {
>>>>        use gdb_simple_compile the simple main program from above
>>>>              use "info line 5", and return false if we get "out of range", otherwise return true.
>>>>    }
>>>>
>>>
>>> This sounds like a good idea, I would only change the default behavior to returning false, unless we saw specifically "start at address.*and ends at".
>>
>> ...
>>
>>> This would make GDB changes more pronounced, as GCC would start having different results.
>>
>> Note sure what you mean here.
>>
> 
> I meant that if something changes in GDB and the epilogue detection fails, making gcc's test result different would be easier to detect than making clang's results different.

I see.  Sounds fine.