Re: [arch-dev-public] ON HOLD - RFC: Use x86_64-v2 architecture

2021-03-04 Thread Allan McRae via arch-dev-public
On 4/3/21 9:51 pm, Filipe Laíns wrote: > On Thu, 2021-03-04 at 21:33 +1000, Allan McRae via arch-dev-public wrote: >> On 3/3/21 10:54 am, Allan McRae via arch-dev-public wrote: >>> On 2/3/21 9:51 pm, Allan McRae wrote: Hi all, A new RFC has been opened here: https://gitlab.archl

Re: [arch-dev-public] ON HOLD - RFC: Use x86_64-v2 architecture

2021-03-04 Thread Filipe Laíns via arch-dev-public
On Thu, 2021-03-04 at 21:33 +1000, Allan McRae via arch-dev-public wrote: > On 3/3/21 10:54 am, Allan McRae via arch-dev-public wrote: > > On 2/3/21 9:51 pm, Allan McRae wrote: > > > Hi all, > > > > > > A new RFC has been opened here: > > > https://gitlab.archlinux.org/archlinux/rfcs/-/merge_reque

[arch-dev-public] RFC: Build using LTO by default

2021-03-04 Thread Allan McRae via arch-dev-public
Hi, When pacman-6.0 is release, makepkg will provide the option to build packages using Link Time Optimisation (LTO) by default. This provides smaller, faster executables/DSOs, and improves GCC diagnostics. SUSE saw an average 5% decrease in binary size. In short, makepkg.conf will have: OPTIO

[arch-dev-public] RFC: Buildflag updates

2021-03-04 Thread Allan McRae via arch-dev-public
Hi, Now we have had some controversy... lets look at some easier RFCs! The first is about additions to build flags. Specifically, our makepkg.conf would look like: #CPPFLAGS="" CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions \ -Wp,-D_FORTIFY_SOURCE=2,-D_GLIBCXX_ASS

[arch-dev-public] ON HOLD - RFC: Use x86_64-v2 architecture

2021-03-04 Thread Allan McRae via arch-dev-public
On 3/3/21 10:54 am, Allan McRae via arch-dev-public wrote: > On 2/3/21 9:51 pm, Allan McRae wrote: >> Hi all, >> >> A new RFC has been opened here: >> https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/2 >> >> Summary: >> Make -march=x86_64-v2 the default for our packages. This assumes t