Skip to content

Add initial configurations for the fbgemm-xpu package#70

Open
flezaalv wants to merge 30 commits into
intel:mainfrom
aagalleg:flezaalv/feat/update-build-files-to-toml-and-cmake
Open

Add initial configurations for the fbgemm-xpu package#70
flezaalv wants to merge 30 commits into
intel:mainfrom
aagalleg:flezaalv/feat/update-build-files-to-toml-and-cmake

Conversation

@flezaalv

@flezaalv flezaalv commented Jun 9, 2026

Copy link
Copy Markdown

This PR updates the fbgemm-xpu build and packaging foundation to use a pyproject.toml + CMake setup.
It also adds/updates package metadata (README, license, manifest, versioning, and third-party notices), introduces an initial operator template, and updates dependencies and installation instructions on XPU environments.

Follow the README instructions to build fbgemm-xpu package.

CC: @aagalleg @manuelhsantana

aagalleg and others added 17 commits May 27, 2026 22:07
Adds BSD 3-Clause license (Copyright 2026 Intel Corporation) for the
fbgemm-xpu package and third-party-programs.txt documenting the
original FBGEMM software license from Meta Platforms, Inc. Ensures
proper legal attribution for derivative work.
- Implements setuptools configuration for building fbgemm XPU operators
with Intel SYCL backend.
- NOTE: setup.py will be replaced by toml build system for torchlib-xpu integration in a future PR. So far setup.py is needed to build fbgemm-xpu independently to run tests.
Comment thread packages/fbgemm-xpu/pyproject.toml Outdated
Comment thread packages/fbgemm-xpu/pyproject.toml Outdated
Comment thread packages/fbgemm-xpu/pyproject.toml Outdated
Comment thread packages/fbgemm-xpu/pyproject.toml
Comment thread packages/fbgemm-xpu/third-party-programs.txt Outdated
@flezaalv flezaalv marked this pull request as ready for review June 10, 2026 17:55
Comment thread packages/fbgemm-xpu/pyproject.toml Outdated
Comment thread packages/fbgemm-xpu/pyproject.toml Outdated
Comment thread packages/fbgemm-xpu/MANIFEST.in Outdated
Comment thread packages/fbgemm-xpu/src/fbgemm_xpu/ops_registry.cpp
Comment thread packages/fbgemm-xpu/src/fbgemm_xpu/ops.py
Comment thread packages/fbgemm-xpu/src/fbgemm_xpu/CMakeLists.txt Outdated
Comment thread packages/fbgemm-xpu/src/fbgemm_xpu/CMakeLists.txt Outdated
Comment thread packages/fbgemm-xpu/src/fbgemm_xpu/CMakeLists.txt

target_compile_options(_C PRIVATE
-fdiagnostics-color=always
-Wno-c++11-narrowing

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

-Wno-c++11-narrowing - why? I would prefer to add any warning suppressions in the PR which actually adds the code.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

Removed.

Comment thread packages/fbgemm-xpu/README.md Outdated
Comment thread packages/fbgemm-xpu/pyproject.toml
flezaalv and others added 3 commits June 15, 2026 11:29
Co-authored-by: Dmitry Rogozhkin <dmitry.v.rogozhkin@intel.com>
Co-authored-by: Dmitry Rogozhkin <dmitry.v.rogozhkin@intel.com>
Co-authored-by: Dmitry Rogozhkin <dmitry.v.rogozhkin@intel.com>
@flezaalv flezaalv requested a review from dvrogozh June 16, 2026 17:48
Comment thread packages/fbgemm-xpu/version.txt Outdated
fbgemm_utils/*.cpp
)

# CMake does not recognize the .sycl extension as a C++ source. Mirror every

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Maybe we will just implement sycl kernels in the *.cpp files? We can separate them out into the sycl/ folder if needed to avoid intermix with the regular *.cpp files.

Comment thread packages/fbgemm-xpu/src/fbgemm_xpu/CMakeLists.txt Outdated
# --------------------------------------------------------------------------
# Auto-include all host C++ sources in this directory.
file(GLOB host_sources CONFIGURE_DEPENDS
*.cpp

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

To be honest I would prefer to have explicit list of files to build rather than wildcards. That's current consensus across the ecosystem that explicit is always better.

flezaalv and others added 2 commits June 16, 2026 16:27
Co-authored-by: Dmitry Rogozhkin <dmitry.v.rogozhkin@intel.com>
Co-authored-by: Dmitry Rogozhkin <dmitry.v.rogozhkin@intel.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants