On Mon, Dec 11, 2017 at 6:42 PM, Alexandre Oliva <aol...@redhat.com> wrote: > On Dec 7, 2017, Jeff Law <l...@redhat.com> wrote: > >> On 11/09/2017 07:34 PM, Alexandre Oliva wrote: >>> Introduce a command line option to enable statement frontiers, enabled >>> by default in optimized builds with DWARF2+ debug information. >> OK once all prereqs are ack'd. > > Thanks, here's what's installed, FTR: > > From aa2fd8850c18861c8e3811b9174b0b1667111783 Mon Sep 17 00:00:00 2001 > From: aoliva <aoliva@138bc75d-0d04-0410-961f-82ee72b054a4> > Date: Tue, 12 Dec 2017 02:16:31 +0000 > Subject: [PATCH 6/7] [SFN] Introduce -gstatement-frontiers option, enable > debug markers > > Introduce a command line option to enable statement frontiers, enabled > by default in optimized builds with DWARF2+ debug information. > > This patch depends on an earlier patch that completed the > infrastructure for debug markers, and on another patch that turns -g > into a negatable option prefix. > > for gcc/ChangeLog > > * common.opt (gstatement-frontiers): New, setting > debug_nonbind_markers_p. > * rtl.h (MAY_HAVE_DEBUG_MARKER_INSNS): Activate. > * toplev.c (process_options): Autodetect value for debug statement > frontiers option. > * tree.h (MAY_HAVE_DEBUG_MARKER_STMTS): Activate. > * doc/invoke.texi (gstatement-frontiers, gno-statement-frontiers): > New. >
This caused: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83728 H.J.
