@All
So, recompiled some stuff with LTO and compare with the same bulids but with no LTO.

Quake3 (plain C): give +1.5fps everywhere with lto.
Foobillard++:(plain C) as i say before give +8fps (about 12-13% speed increase)

FrickingShark (c++/c): no changes
Barony (c++/c): no changes
Prototype (c++/c): no changes

Dunno if it can be something about c++ code only , or just it some luck that those 3 which have no differences when compiled with lto are c++ ones, while those which have differences are plain c ones.

@kas1e

Now that it has been successfullya tested, could you try to add it to the adtools daily builds (or bleeding edge or whatever), so people can pick it up from there?

@Raziel
Its a matter of Sebastian's wish, its only about adding --enable-lto to one place. I can write in your ticket that it tested and works, but don't hold your hope he will add it, as it will mean some extra support later if anything will going wrong.

@kas1e

Just seen it, thank you

@Raziel
Sba added that switch, so probably next autobuilds will contain it

@all
Native amigaos4 version with enabled lto as well as it also gcc 8.3.0 now can be taken as usual from https://dl.bintray.com/sba1/adtools-native/

There is direct link:

https://dl.bintray.com/sba1/adtools-na ... ls-os4-8-20190301-697.lha

I want advice the clib2 links are broken and you have to fix it manually. There’s a semicolon to be removed in the file path..

Also gcc version are you sure it’s the 8.3.0? I read 8.1.0 in cc1 binary.

@flash
As Sba say that ":" thing in the urls probably come from bintray.com itself

As for gcc 8.1.0 instead of 8.3.0 there was issue he fix today, check new build, should be ok:

https://dl.bintray.com/sba1/adtools-na ... ls-os4-8-20190304-698.lha

@kas1e

I have installed the -699 daily build now, but it still doesn't seem to get picked up, it still refuses to find a gcc, c++ compiler.

This is with the apps configure script

@kas1e

Do you maybe have some short code to test the lto flag?
Just to make sure it's picked up correctly?

@Raziel
You can do what i do in post #15 for brief check

@kas1e

I tried that and it builds, but fist i get an error on linking

Quote:
adding -shared to the line makes it build, but my binaries WITH -flto in place are still bigger in size than without (6250 bytes with lto, compared to 6213 without lto).
Even removing -shared from the non-lto build makes it only 3 bytes smaller, so i'm not sure what's going (still suspecting that -flto isn't picked up and used et al).

@Raziel
Maybe something with your adtools installation ? I for sure didn't use -shared and it works. Maybe still old gcc is used ? Check via gcc -v if it says that it 8.3.0 and lto enabled

@kas1e

15.System:> gcc -v
Using built-in specs.
COLLECT_GCC=/Development/Coding/SDK/gcc/bin/gcc
COLLECT_LTO_WRAPPER=/Development/Coding/SDK/gcc/bin/../libexec/gcc/ppc-amigaos/8.3.0/lto-wrapper
Target: ppc-amigaos
Configured with: /var/lib/jenkins/workspace/native-gcc-8/gcc/repo/configure --with-bugurl=https://github.com/sba1/adtools/issues --with-pkgversion='adtools build 8.3.0' --host=ppc-amigaos --target=ppc-amigaos --disable-nls --prefix=/gcc --with-gmp=/var/lib/jenkins/workspace/native-gcc-8/native-build/root-cross --with-mpfr=/var/lib/jenkins/workspace/native-gcc-8/native-build/root-cross --with-mpc=/var/lib/jenkins/workspace/native-gcc-8/native-build/root-cross --enable-languages=c,c++ --enable-haifa --enable-sjlj-exceptions --disable-libstdcxx-pch --disable-tls --enable-threads=amigaos --enable-lto
Thread model: amigaos
gcc version 8.3.0 (adtools build 8.3.0)

@Raziel
Dunno then, i for sure didn't use any -shared thing on my cygwin build, and lto for sure works for me.

@kas1e

Maybe because you use it to cross compile while i do native builds?
Maybe you use a slightly different toolchain than me?

@all

Can someone shed some light please.

I have broswed the GNU linker manual and stumbled over this:
Quote:

Since i'm trying to avoid shared/dynamic builds, what does that mean regarding the usage of -flto?