On 10/31/2016 01:04 PM, Jakub Jelinek wrote:
On Mon, Oct 31, 2016 at 12:58:23PM -0400, Jason Merrill wrote:
On 10/14/2016 03:41 PM, Jakub Jelinek wrote:
Another set of GNU extensions that were accepted into DWARF5, so we should
emit them even for -gstrict-dwarf -gdwarf-5, and for -gdwarf-5 shou
On Mon, Oct 31, 2016 at 12:58:23PM -0400, Jason Merrill wrote:
> On 10/14/2016 03:41 PM, Jakub Jelinek wrote:
> >Another set of GNU extensions that were accepted into DWARF5, so we should
> >emit them even for -gstrict-dwarf -gdwarf-5, and for -gdwarf-5 should use
> >the accepted standard opcodes i
On 10/14/2016 03:41 PM, Jakub Jelinek wrote:
Another set of GNU extensions that were accepted into DWARF5, so we should
emit them even for -gstrict-dwarf -gdwarf-5, and for -gdwarf-5 should use
the accepted standard opcodes instead of the corresponding GNU ones.
Hmm, I wonder if we also want to
Hi!
Another set of GNU extensions that were accepted into DWARF5, so we should
emit them even for -gstrict-dwarf -gdwarf-5, and for -gdwarf-5 should use
the accepted standard opcodes instead of the corresponding GNU ones.
Bootstrapped/regtested on x86_64-linux and i686-linux on top of the
dwarf2.