Re: is re-running bootstrap after a change safe?

2019-04-08 Thread Jeff Law
On 4/8/19 3:19 AM, Richard Biener wrote: > On Sat, Apr 6, 2019 at 1:09 AM Martin Sebor wrote: >> >> On 4/5/19 4:02 PM, Jeff Law wrote: >>> On 4/5/19 3:37 PM, Martin Sebor wrote: On 4/5/19 3:29 PM, Jeff Law wrote: > On 4/5/19 2:50 PM, Eric Botcazou wrote: >>> Say if the first

Re: is re-running bootstrap after a change safe?

2019-04-08 Thread Richard Biener
On Sat, Apr 6, 2019 at 1:09 AM Martin Sebor wrote: > > On 4/5/19 4:02 PM, Jeff Law wrote: > > On 4/5/19 3:37 PM, Martin Sebor wrote: > >> On 4/5/19 3:29 PM, Jeff Law wrote: > >>> On 4/5/19 2:50 PM, Eric Botcazou wrote: > > Say if the first bootstrap succeeds and I then change a single > >

Re: is re-running bootstrap after a change safe?

2019-04-06 Thread Andreas Schwab
On Apr 05 2019, Martin Sebor wrote: > So to be clear: the safe and also most efficient to "rebootstrap" > GCC is to remove what exactly? (I don't see any stage2 or stage3 > directories in my build tree.) Is there a make target for this? make stage1-start; rm -rf stage[23]-* compare Andreas.

Re: is re-running bootstrap after a change safe?

2019-04-05 Thread Martin Sebor
On 4/5/19 4:02 PM, Jeff Law wrote: On 4/5/19 3:37 PM, Martin Sebor wrote: On 4/5/19 3:29 PM, Jeff Law wrote: On 4/5/19 2:50 PM, Eric Botcazou wrote: Say if the first bootstrap succeeds and I then change a single GCC .c file and rerun make bootstrap, am I guaranteed to see the same fallout of

Re: is re-running bootstrap after a change safe?

2019-04-05 Thread Jeff Law
On 4/5/19 3:37 PM, Martin Sebor wrote: > On 4/5/19 3:29 PM, Jeff Law wrote: >> On 4/5/19 2:50 PM, Eric Botcazou wrote: Say if the first bootstrap succeeds and I then change a single GCC .c file and rerun make bootstrap, am I guaranteed to see the same fallout of the change as I

Re: is re-running bootstrap after a change safe?

2019-04-05 Thread Martin Sebor
On 4/5/19 3:29 PM, Jeff Law wrote: On 4/5/19 2:50 PM, Eric Botcazou wrote: Say if the first bootstrap succeeds and I then change a single GCC .c file and rerun make bootstrap, am I guaranteed to see the same fallout of the change as I would if I did a pristine build in a clean directory? No,

Re: is re-running bootstrap after a change safe?

2019-04-05 Thread Jeff Law
On 4/5/19 2:50 PM, Eric Botcazou wrote: >> Say if the first bootstrap succeeds and I then change a single >> GCC .c file and rerun make bootstrap, am I guaranteed to see >> the same fallout of the change as I would if I did a pristine >> build in a clean directory? > > No, this would imply

Re: is re-running bootstrap after a change safe?

2019-04-05 Thread Eric Botcazou
> Say if the first bootstrap succeeds and I then change a single > GCC .c file and rerun make bootstrap, am I guaranteed to see > the same fallout of the change as I would if I did a pristine > build in a clean directory? No, this would imply deleting the stage2 and stage3 compilers and that

Re: is re-running bootstrap after a change safe?

2019-04-05 Thread H.J. Lu
On Fri, Apr 5, 2019 at 12:55 PM Martin Sebor wrote: > > Is it safe to rerun make bootstrap after changing GCC source? > > Say if the first bootstrap succeeds and I then change a single > GCC .c file and rerun make bootstrap, am I guaranteed to see > the same fallout of the change as I would if I

is re-running bootstrap after a change safe?

2019-04-05 Thread Martin Sebor
Is it safe to rerun make bootstrap after changing GCC source? Say if the first bootstrap succeeds and I then change a single GCC .c file and rerun make bootstrap, am I guaranteed to see the same fallout of the change as I would if I did a pristine build in a clean directory? I have been