This thread has been illuminating for me because apparently my understanding was incomplete.
Chakra issue: Enable LTO (Link Time Optimization) by default for GCC for smaller and faster binaries
Started thinking about this earlier because the new lto option will allow me to greatly reduce the amount of lines I have of different CFLAGS/CXXFLAGS for LTO/GCC/Clang/AOCC but I think I might have to keep a few different LDFLAGS lines.
Hmmm so Pacman version 6 hit stable the other day for Arch Linux users such as myself and while I'm greatly enjoying it I am also finding myself wondering if the "lto" option in makepkg.conf goes far enough at least for GCC since docs don't say it adds the -flto linker flag.
AFAIK Clang doesn't need any linker opts passed but with GCC builds if you compile with LTO but don't use the LTO linker opts I thought the LTO stuff basically went to waste and was unused.
It should be a lot easier on Arch Linux but here on Fedora I'm not really sure what the best way to set custom compiler flags would be. Probably simple enough but I'm spoiled by things like makepkg and Portage that have a standard documented location for custom flags.
I wanted to try going balls to the wall with enabling all of this Polly stuff I just found out about but unfortunately I'm too much of a n00b to understand where to insert custom compiler flags into the build script.
Every note is a betrayal yet nostalgic.
Got this on discount RIP me
Stillhouse Original Whiskey
Fashawn & Exile "Hey Young World (feat Aloe Blacc & Devoya)"
Geek extraordinaire. I want meaningful change, for both life & software. I frequently tell myself how problematic I am.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!