Re: Problem with continue/halt

> Date: Thu, 26 Jun 2014 17:38:56 +0200
> From: Freddie Chopin <[email protected]>
> 
> W dniu 2014-06-26 17:24, Eli Zaretskii pisze:
> > Are you per chance compiling with LTO?  If so, don't.
> 
> I'm using the same command as the one which worked fine previously:
> 
> > $SRCDIR/$BINUTILS_GDB/configure --build=$BUILD \
> >     --host=$HOST_MINGW \
> >     --target=$TARGET \
> >     --prefix=$INSTALLDIR_MINGW \
> >     --infodir=$INSTALLDIR_MINGW_DOC/info \
> >     --mandir=$INSTALLDIR_MINGW_DOC/man \
> >     --htmldir=$INSTALLDIR_MINGW_DOC/html \
> >     --pdfdir=$INSTALLDIR_MINGW_DOC/pdf \
> >     --disable-nls \
> >     --enable-plugins \
> >     --with-sysroot=$INSTALLDIR_MINGW/arm-none-eabi \
> >     --disable-sim \
> >     --with-python=no \
> >     --with-lzma=no \
> >     --with-libexpat=$BUILDDIR_MINGW/host-libs/usr \
> >     --with-libiconv-prefix=$BUILDDIR_MINGW/host-libs/usr \
> >     --with-system-gdbinit=$INSTALLDIR_MINGW/$HOST_MINGW/arm-none-eabi/lib/gdbinit \
> >     '--with-gdb-datadir='\''${prefix}'\''/arm-none-eabi/share/gdb' \
> >     "--with-pkgversion=$PKGVERSION"
> >
> >     make -j$JOBS
> 
> So I'm not enabling LTO explicitly, maybe that's enabled by default somehow?

If you add -v to the GCC command line, it will show you what it is
doing.

> BTW - do you mean LTO is the cause for the continue/halt problem or the 
> issue of building older versions?

The former, I think.