Re: how to debug go build errors

2018-02-08 Thread Martin Sebor
On 02/08/2018 05:39 PM, Ian Lance Taylor wrote: On Thu, Feb 8, 2018 at 3:24 PM, Martin Sebor wrote: While testing what should be an innocuous patch to add LTO to a bunch of middle-end warning options https://gcc.gnu.org/ml/gcc-patches/2018-02/msg00381.html I get Go errors during ordinary b

Re: how to debug go build errors

2018-02-08 Thread Martin Sebor
Never mind. I see the problem. I overlooked a few failures in the preprocessor test suite. Turns out the patch accidentally deletes the -d option from the .opt file. I didn't notice it in the diff because the "-d" at the beginning of the line looks just like the option is still there! @@ -118

Re: how to debug go build errors

2018-02-08 Thread Ian Lance Taylor
On Thu, Feb 8, 2018 at 3:24 PM, Martin Sebor wrote: > > While testing what should be an innocuous patch to add LTO > to a bunch of middle-end warning options > > https://gcc.gnu.org/ml/gcc-patches/2018-02/msg00381.html > > I get Go errors during ordinary bootstrap about undefined names > for err