Skip to content

Conversation

guangyey
Copy link
Contributor

Motivation

To resolve #2034, expose all xpu internal headers to PyTorch.

@Copilot Copilot AI review requested due to automatic review settings September 25, 2025 03:00
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR exposes all XPU internal headers to PyTorch by installing them to the PyTorch include directory, addressing issue #2034 in torch-xpu-ops. The changes replace specific header installation logic with a more comprehensive approach that covers all XPU-related header directories.

  • Replaced hardcoded header patterns with a macro-based approach for installing headers
  • Added installation of internal XPU headers from multiple subdirectories (native/xpu, nested, quantized, sparse, transformers)
  • Added conditional check for generated headers installation

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

@guangyey guangyey added the windows_ci Only for Windows CI trigger label Sep 25, 2025
@guangyey guangyey added this pull request to the merge queue Sep 26, 2025
Merged via the queue into main with commit 26ae9e7 Sep 26, 2025
133 of 150 checks passed
@guangyey guangyey deleted the guangyey/header branch September 26, 2025 02:50
mengfei25 pushed a commit to mengfei25/torch-xpu-ops that referenced this pull request Sep 29, 2025
# Motivation
To resolve intel#2034, expose
all xpu internal headers to PyTorch.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

windows_ci Only for Windows CI trigger

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Are header files exposed in torch ?

2 participants