[Mesa-dev] [PATCH 0/9] Move nir/glsl to src/compiler
Emil Velikov
emil.l.velikov at gmail.com
Fri Nov 27 10:16:19 PST 2015
On 27 November 2015 at 17:54, Jason Ekstrand <jason at jlekstrand.net> wrote:
>
> On Nov 25, 2015 1:27 PM, "Emil Velikov" <emil.l.velikov at gmail.com> wrote:
>>
>> Hello all,
>>
>> Some of us have been thinking about moving nir out of glsl, and fleshing
>> out some common helper (static library) that is use by both. So here it
>> is - src/compiler.
>>
>> The modules (libcompiler, libnir and libglsl) are unfortunately not
>> really independent.
>> - libcompiler - compile time (mesa ir, glsl ir, util), link - util
>> - libglsl - compile (compiler, mesa ir, util), link - compiler, util
>> - libnir - compile (compiler, mesa ir, glsl ir, util), link - compiler,
>> util
>
> Thanks for working on this! Before I make comments, its worth noting that
> the biggest churn is just moving files. If we don't have the linking
> details figured out, that shouldn't block landing the file churn.
>
> I was kind of hoping that we could have a libnir that doesn't require glsl.
> It would be good for freedreno and vc4 among other things. Maybe split
> things up differently?
>
One of us is getting confused here.
NIR does _not_ depend during link time on glsl and vice-versa (as per
above list).
To remove the compile-time dependency, I've spent a fair bit of time
trying to flesh things out. Yet that's not possible without rewriting
substantial hunks of glsl, nir and mesa.
> - libcompilerutil: just glsl_types and shader_enums
> - libglsl
> - libnir
> - libcompiler
>
> Neither libglsl nor libnir should depend on the other. If you want
> everything, you use libcompiler which would depend on both libglsl and
> libnir and also bring in glsl_to_nir.
>
> Would that be practical? (I don't know autotools or libtool all that well.)
>
With the above said I'm not sure how I can comment on this. Sorry :-(
Thanks
Emil
More information about the mesa-dev
mailing list