Re: [Mesa-dev] [PATCH 2/3] swr: allow a single swr architecture to be builtin

2018-01-18 Thread Chuck Atkins
Since there's been some churn on this, I'll try to post the updated patches in a new thread (provided my git config is set right that is) - Chuck On Wed, Jan 17, 2018 at 8:56 AM, Chuck Atkins wrote: > I wasn't happy with the redundancy either but at the time just didn't see > how to refactor it

Re: [Mesa-dev] [PATCH 2/3] swr: allow a single swr architecture to be builtin

2018-01-17 Thread Chuck Atkins
I wasn't happy with the redundancy either but at the time just didn't see how to refactor it more cleanly. I'll take a second pass to consolidate and remove duplication. - Chuck On Tue, Jan 16, 2018 at 5:03 PM, Cherniak, Bruce wrote: > > > On Jan 16, 2018, at 1:59 PM, Chuck Atkins > wrote: >

Re: [Mesa-dev] [PATCH 2/3] swr: allow a single swr architecture to be builtin

2018-01-16 Thread Cherniak, Bruce
> On Jan 16, 2018, at 1:59 PM, Chuck Atkins wrote: > > Part 2 of 2 (part 1 is autoconf changes, part 2 is C++ changes) > > When only a single SWR architecture is being used, this allows that > architecture to be builtin rather than as a separate libswrARCH.so that > gets loaded via dlopen. Sin

[Mesa-dev] [PATCH 2/3] swr: allow a single swr architecture to be builtin

2018-01-16 Thread Chuck Atkins
Part 2 of 2 (part 1 is autoconf changes, part 2 is C++ changes) When only a single SWR architecture is being used, this allows that architecture to be builtin rather than as a separate libswrARCH.so that gets loaded via dlopen. Since there are now several different code paths for each detected CP