[Intel-gfx] [PATCH gen4asm 1/3] build: Don't use automake's maintainer modey

Beauchesne, Gwenole gwenole.beauchesne at intel.com
Thu Jan 17 11:56:28 CET 2013


Hi,

> On Fri, Jan 11, 2013 at 09:41:05AM +0100, Daniel Vetter wrote:
> > What about moving gen4asm into a subdir of i-g-t? With git
> > filter-branch we could even retain the entire history ....
> > -Daniel
> 
> I'm not against doing that, it'll shed more light/review/etc on the assembler (I
> assume patches would have to hit this list first).
> 
> Xiang, Homer, Gwenole, what do you think of that idea?

I think distributions would prefer smaller self-contained projects, that don't need too many dependencies. If we make intel-gen4asm into i-g-t, we'd need additional configure options to enable/disable certain components, e.g. testdisplay with cairo/libudev deps.

While we are at re-organizing intel-gen4asm, I would also suggest to think about using Chris' libbrw as the actual backend to the GenX assembler. There is a need to generate code both at run-time and build-time, and it would be better to use the same assembler back-end, so that to simplify validation and enablement of future generations. IMHO, that'd a more sensible move than deciding on where to host intel-gen4asm. :)

Thanks,
Gwenole.



More information about the Intel-gfx mailing list