<div dir="ltr"><span style="font-family:arial,sans-serif;font-size:13px">> So, I don't suppose it is possible to have multiple side-by-side </span><span style="font-family:arial,sans-serif;font-size:13px">llvm's? </span><div> <span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px">They each go in their own subdirectory, with the version number in the path.</span></div> <div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><font face="arial, sans-serif">> </font><span style="font-family:arial,sans-serif;font-size:13px">I don't really look </span><span style="font-family:arial,sans-serif;font-size:13px">forward to having to recompile llvm when switching between branches.</span></div> <div><br></div><div>LLVM would sit next to mesa, fully compiled, as many versions as you want, waiting for anything else to link against it. Changes in other projects in other locations has no effect on the already compiled LLVM directories.</div> <div><br></div><div>Different versions of Mesa can point at different LLVM paths, to pick up which ever already compiled version of LLVM that version wants to pick up. Should just be a natural part of the re-link you do when switching between branches.</div> <div><br></div><div>JohnK</div><div><br><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Aug 27, 2014 at 1:57 PM, Rob Clark <span dir="ltr"><<a href="mailto:robdclark@gmail.com" target="_blank">robdclark@gmail.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On Wed, Aug 27, 2014 at 2:26 PM, John Kessenich <<a href="mailto:johnk@lunarg.com">johnk@lunarg.com</a>> wrote:<br> > Hi,<br> ><br> > If Mesa used an LLVM IR for it's shader compiler stack, it would most likely<br> ><br> > Pick a specific shipped version. Shipped versions are stable and<br> > unchanging. Upgrading to a newer version would be done only by choice, on<br> > Mesa's schedule.<br> > Not bring the source into mesa: it works perfectly well sitting next to<br> > Mesa.<br> > Link it in statically so there are no distro/versioning issues and no<br> > interactions with other components of the system that independently use LLVM<br> > however they wish. This is also quite small compared to other uses of LLVM<br> > people sometimes discuss.<br> ><br> > Externally, no one could even tell some helper functions within the compiler<br> > stack came from LLVM or a specific version of LLVM.<br> ><br> </div>>> Packaging and ABI stability...<br> ><br> > These don't even exist with linking statically to a chosen version.<br> <br> So, I don't suppose it is possible to have multiple side-by-side<br> llvm's? Ie. I wonder what happens when I'm switching back and forth<br> between latest stable mesa branch, vs master which has moved on to<br> llvm n+1?<br> <br> I guess that is less of packaging issue.. but I don't really look<br> forward to having to recompile llvm when switching between branches.<br> <br> BR,<br> -R<br> <br> <br> > JohnK<br> ><br> ><br> ><br> > On Tue, Aug 26, 2014 at 10:25 PM, Greg Fischer <<a href="mailto:greg@lunarg.com">greg@lunarg.com</a>> wrote:<br> >><br> >> My apologies for a too-brief response to this question.<br> >><br> >> GlassyMesa links LLVM statically into Mesa. I believe that previous<br> >> posters to this thread have already done a pretty good job of arguing that<br> >> this is at least a workable approach.<br> >><br> >> Best regards,<br> >> Greg<br> >><br> >><br> >><br> >> On Tue, Aug 26, 2014 at 7:14 PM, Kenneth Graunke <<a href="mailto:kenneth@whitecape.org">kenneth@whitecape.org</a>><br> >> wrote:<br> >>><br> >>> On Tuesday, August 26, 2014 06:45:42 PM Greg Fischer wrote:<br> >>> > The GlassyMesa effort is ongoing despite the lack of recent activity.<br> >>> > We<br> >>> > continue to embrace LLVM as a basis for shader compilation in Mesa and<br> >>> > elsewhere.<br> >>> ><br> >>> > We agree that translating from LLVM back "up" to GLSL IR is problematic<br> >>> > and<br> >>> > that an architecture that supports LLVM backends would be desirable.<br> >>> ><br> >>> > The current published code is a work-in-progress. We are currently<br> >>> > working<br> >>> > on tuning of compilation time and code generation quality, and some of<br> >>> > that<br> >>> > work will likely be appearing soon. There have also been recent<br> >>> > improvements in glslang, the parser for this stack.<br> >>> ><br> >>> > Packaging and ABI stability have not been an issue for us.<br> >>><br> >>> As far as I know, you haven't actually shipped your software in any Linux<br> >>> distribution yet, so a lack of packaging problems sort of goes without<br> >>> saying...<br> >>><br> >>> --Ken<br> <div class="HOEnZb"><div class="h5">>><br> >><br> >><br> >> _______________________________________________<br> >> mesa-dev mailing list<br> >> <a href="mailto:mesa-dev@lists.freedesktop.org">mesa-dev@lists.freedesktop.org</a><br> >> <a href="http://lists.freedesktop.org/mailman/listinfo/mesa-dev" target="_blank">http://lists.freedesktop.org/mailman/listinfo/mesa-dev</a><br> >><br> ><br> ><br> > _______________________________________________<br> > mesa-dev mailing list<br> > <a href="mailto:mesa-dev@lists.freedesktop.org">mesa-dev@lists.freedesktop.org</a><br> > <a href="http://lists.freedesktop.org/mailman/listinfo/mesa-dev" target="_blank">http://lists.freedesktop.org/mailman/listinfo/mesa-dev</a><br> ><br> </div></div></blockquote></div><br></div>