Re: PING^1: [PATCH] Set start_location to 0 if we ran out of line map space

2018-08-24 Thread H.J. Lu
>> From: H.J. Lu >> Date: Wed, Aug 15, 2018 at 4:33 AM >> Subject: [PATCH] Set start_location to 0 if we ran out of line map >> space >> To: gcc-patches@gcc.gnu.org >> >> >> With profiledbootstrap and --with-build-config=bootstrap-lto, >>

Re: PING^1: [PATCH] Set start_location to 0 if we ran out of line map space

2018-08-24 Thread David Malcolm
ocation to 0 if we ran out of line map > space > To: gcc-patches@gcc.gnu.org > > > With profiledbootstrap and --with-build-config=bootstrap-lto, > linemap_add > may create a macro map when we run out of line map space. This patch > changes start_location to UNKNOWN_LOCA

PING^1: [PATCH] Set start_location to 0 if we ran out of line map space

2018-08-22 Thread H.J. Lu
PING. -- Forwarded message -- From: H.J. Lu Date: Wed, Aug 15, 2018 at 4:33 AM Subject: [PATCH] Set start_location to 0 if we ran out of line map space To: gcc-patches@gcc.gnu.org With profiledbootstrap and --with-build-config=bootstrap-lto, linemap_add may create a macro map

[PATCH] Set start_location to 0 if we ran out of line map space

2018-08-15 Thread H.J. Lu
With profiledbootstrap and --with-build-config=bootstrap-lto, linemap_add may create a macro map when we run out of line map space. This patch changes start_location to UNKNOWN_LOCATION (0) in this case. Tested with profiledbootstrap and --with-build-config=bootstrap-lto on Linux/x86-64.