Skip to content

Conversation

@echeresh
Copy link
Contributor

This is to allow using a standalone (or third-party) gemmstone repository for building.

@echeresh echeresh requested a review from a team as a code owner October 28, 2025 17:36
@echeresh echeresh added the platform:gpu-intel Codeowner: @oneapi-src/onednn-gpu-intel label Oct 28, 2025
@echeresh
Copy link
Contributor Author

make test
disable device_cpu


#include "common/utils.hpp"
#include "gpu/intel/gemm/jit/generator/pieces/copy_plan.hpp"
#include "gemmstone/../../generator/pieces/copy_plan.hpp"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How much work would it be to move the necessary interfaces from copy_plan.hpp into the external headers? Relying on the internal headers like this is not a good design choice.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think @atkassen can comment better. Yes, without a proper interface this is not aligned with the current design.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we're happy with #include "gemmstone/generator.hpp" instead, I think it should suffice:

#include "generator/pieces/copy_plan.hpp"

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, looks like this just snowballs, so we can leave it as is. This definitely needs reworked at some point, gemmstone/generator.hpp shouldn't have includes outside of the include directory either.

@echeresh
Copy link
Contributor Author

make test
disable device_cpu

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

platform:gpu-intel Codeowner: @oneapi-src/onednn-gpu-intel

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants