Re: [PATCH v4 00/11] remove component-specific logic for AVX builds

2025-03-27 Thread David Marchand
On Wed, Mar 19, 2025 at 6:30 PM Bruce Richardson wrote: > > A number of libs and drivers had special optimized AVX2 and AVX512 code > paths for performance reasons, and these tended to have copy-pasted > logic to build those files. Centralise that logic in the main > drivers/ and lib/ meson.build

Re: [PATCH v4 00/11] remove component-specific logic for AVX builds

2025-03-25 Thread Bruce Richardson
On Tue, Mar 25, 2025 at 08:46:35AM +0100, David Marchand wrote: > Hello Bruce, > > On Wed, Mar 19, 2025 at 7:09 PM Bruce Richardson > wrote: > > > > On Wed, Mar 19, 2025 at 05:29:30PM +, Bruce Richardson wrote: > > > A number of libs and drivers had special optimized AVX2 and AVX512 code > >

Re: [PATCH v4 00/11] remove component-specific logic for AVX builds

2025-03-25 Thread David Marchand
Hello Bruce, On Wed, Mar 19, 2025 at 7:09 PM Bruce Richardson wrote: > > On Wed, Mar 19, 2025 at 05:29:30PM +, Bruce Richardson wrote: > > A number of libs and drivers had special optimized AVX2 and AVX512 code > > paths for performance reasons, and these tended to have copy-pasted > > logic

Re: [PATCH v4 00/11] remove component-specific logic for AVX builds

2025-03-19 Thread Bruce Richardson
On Wed, Mar 19, 2025 at 05:29:30PM +, Bruce Richardson wrote: > A number of libs and drivers had special optimized AVX2 and AVX512 code > paths for performance reasons, and these tended to have copy-pasted > logic to build those files. Centralise that logic in the main > drivers/ and lib/ meson

[PATCH v4 00/11] remove component-specific logic for AVX builds

2025-03-19 Thread Bruce Richardson
A number of libs and drivers had special optimized AVX2 and AVX512 code paths for performance reasons, and these tended to have copy-pasted logic to build those files. Centralise that logic in the main drivers/ and lib/ meson.build files to avoid duplication. v4: rebase on latest main branch m