This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
RE: [patch] Disable if_conversion2 for Og
- From: "Joey Ye" <joey dot ye at arm dot com>
- To: "Richard Earnshaw" <Richard dot Earnshaw at arm dot com>
- Cc: <gcc-patches at gcc dot gnu dot org>
- Date: Wed, 16 Apr 2014 18:26:34 +0800
- Subject: RE: [patch] Disable if_conversion2 for Og
- Authentication-results: sourceware.org; auth=none
- References: <000001cf584e$66102060$32306120$ at arm dot com> <534E50F2 dot 2000606 at arm dot com> <000401cf595a$ee875910$cb960b30$ at arm dot com> <534E558E dot 6010206 at arm dot com>
> -----Original Message-----
> From: Richard Earnshaw
> Sent: Wednesday, April 16, 2014 6:04 PM
> To: Joey Ye
> Cc: gcc-patches@gcc.gnu.org
> Subject: Re: [patch] Disable if_conversion2 for Og
>
> On 16/04/14 11:02, Joey Ye wrote:
> >
> >
> >> -----Original Message-----
> >> From: Richard Earnshaw
> >> Sent: Wednesday, April 16, 2014 5:44 PM
> >> To: Joey Ye
> >> Cc: gcc-patches@gcc.gnu.org
> >> Subject: Re: [patch] Disable if_conversion2 for Og
> >>
> >> Arguably, this is a bug in gdb. The debugger should understand when
> >> a breakpointed conditional instruction is not going to execute and
> >> silently continue. That preserves the illusion of not executing the
> >> code without requiring the compiler to de-optimize things.
> >>
> >> R.
> > Or compiler just optimizes it, and emits generic DWARFx information to
> > help GDB handle it in more target independently?
> >
> > - Joey
> >
>
> I'm not sure extra dwarf info would help much. The debugger still has to
> understand that the breakpoint has not really been hit.
>
> R.
Yes, it is inevitable. But without extra dwarf info it will be even more
painful: each time setting break-point or break-point hits it has to decode
the break-pointed instructions and its context to search for conditional
execution and IT blocks.
- Joey