On 08.01.26 14:06, Jonathan Wakely wrote: > On Thu, 8 Jan 2026 at 12:43, Frank Scheiner wrote: >> But if you tell me that this won't affect the GCC bootstraps, I could >> enable that for future builds, of course. Also to possibly solve the >> below issues because of missing LTO support. >> >> So, just to be sure: `--enable-lto` is enough to support this, or do I >> also need "lto" in `--enable-languages=`? > > Just remove --disable-lto > > It's enabled automatically, which adds it to --enable-languages > automatically, but the explicit --disable-lto overrides that default > behaviour. Ok, great, will do so. I was irritated because Slackware explicitly puts "lto" in `--enable-languages=` for their GCC builds, so I didn't know what effect that has or not. Cheers, Frank
- Re: gcc-16-20251214 testsuite results for ia6... Frank Scheiner via Gcc
- Re: gcc-16-20251214 testsuite results for ia6... Frank Scheiner via Gcc
- Re: gcc-16-20251214 testsuite results for... Jonathan Wakely via Gcc
- Re: gcc-16-20251214 testsuite results... Jonathan Wakely via Gcc
- Re: gcc-16-20251214 testsuite res... Frank Scheiner via Gcc
- Re: gcc-16-20251214 testsuit... Jonathan Wakely via Gcc
- Re: gcc-16-20251214 test... Frank Scheiner via Gcc
- Re: gcc-16-20251214 testsuite results for ia64 Sam James via Gcc
- Re: gcc-16-20251214 testsuite results for ia6... Frank Scheiner via Gcc
- Re: gcc-16-20251214 testsuite results for... Jonathan Wakely via Gcc
- Re: gcc-16-20251214 testsuite results... Frank Scheiner via Gcc
- Re: gcc-16-20251214 testsuite res... Jonathan Wakely via Gcc
- Re: gcc-16-20251214 testsuite results for ia6... Frank Scheiner via Gcc
