On Nov 19, 2019, Bernd Edlinger wrote:
> My question to you is this: can you explain, given the following debug
> info, extracted by readelf from alias.c, why the address 0x6e11 is in
> the inlined subroutine and *not* in the get_alias_set function?
The long version of the explanation is in
http
On 11/19/19 3:01 AM, Alexandre Oliva wrote:
> Hello, Bernd,
>
> Apologies for taking so long to respond. I had not noticed your patch
> before being explicitly copied on it.
>
> IIUC you're describing a problem in GDB, that could be summed up as its
> not paying attention to is_stmt and being un
Hello, Bernd,
Apologies for taking so long to respond. I had not noticed your patch
before being explicitly copied on it.
IIUC you're describing a problem in GDB, that could be summed up as its
not paying attention to is_stmt and being unaware of location views, and
you appear to be proposing to
On Fri, Nov 15, 2019 at 4:47 PM Bernd Edlinger
wrote:
>
> Ping...
>
> FYI this jumping into fake inline frames happens rather often
> when debugging, and is especially annoying once you know how
> easy it is to fix it...
Alex, can you please chime in here? I've looked at the patch twice now
and
Ping...
FYI this jumping into fake inline frames happens rather often
when debugging, and is especially annoying once you know how
easy it is to fix it...
Bernd.
On 11/9/19 11:20 AM, Bernd Edlinger wrote:
> Ping...
>
> On 11/2/19 7:49 AM, Bernd Edlinger wrote:
>> Ping...
>>
>> On 10/27/19 9:14
Ping...
On 11/2/19 7:49 AM, Bernd Edlinger wrote:
> Ping...
>
> On 10/27/19 9:14 AM, Bernd Edlinger wrote:
>> Ping...
>>
>> I'd like to ping for this patch:
>> https://gcc.gnu.org/ml/gcc-patches/2019-10/msg01459.html
>>
>>
>> Thanks
>> Bernd.
>>
>> On 10/20/19 9:58 PM, Bernd Edlinger wrote:
>>> H
Ping...
On 10/27/19 9:14 AM, Bernd Edlinger wrote:
> Ping...
>
> I'd like to ping for this patch:
> https://gcc.gnu.org/ml/gcc-patches/2019-10/msg01459.html
>
>
> Thanks
> Bernd.
>
> On 10/20/19 9:58 PM, Bernd Edlinger wrote:
>> Hi,
>>
>> this fixes an issue with the gdb step-over aka. "n" com
Ping...
I'd like to ping for this patch:
https://gcc.gnu.org/ml/gcc-patches/2019-10/msg01459.html
Thanks
Bernd.
On 10/20/19 9:58 PM, Bernd Edlinger wrote:
> Hi,
>
> this fixes an issue with the gdb step-over aka. "n" command.
>
> It can be seen when you debug an optimized stage-3 cc1
> it doe
Hi,
this fixes an issue with the gdb step-over aka. "n" command.
It can be seen when you debug an optimized stage-3 cc1
it does not affect -O0 code, though.
This example debug session will explain the effect.
(gdb) b get_alias_set
Breakpoint 5 at 0xa099f0: file ../../gcc-trunk/gcc/alias.c, line
