8000 [Windows XPU] Fix MSVC ambiguous symbol error by ratnampa · Pull Request #138727 · pytorch/pytorch · GitHub
[go: up one dir, main page]

Skip to content

[Windows XPU] Fix MSVC ambiguous symbol error #138727

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from

Conversation

ratnampa
Copy link
Contributor
@ratnampa ratnampa commented Oct 23, 2024

PT master build with XPU will fail due to MSVC issue of ambiguous symbol error 'std', previously fixed it with MSVC flag in torch-xpu-ops https://github.com/intel/torch-xpu-ops/pull/946/files, but the error is observed in PT master too after 2.5 and oneAPI update.

Copy link
pytorch-bot bot commented Oct 23, 2024

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/138727

Note: Links to docs will display an error until the docs builds have been completed.

❌ 2 New Failures

As of commit 31a8915 with merge base bf1b8ad (image):

NEW FAILURES - The following jobs have failed:

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@pytorch-bot pytorch-bot bot added the topic: not user facing topic category label Oct 23, 2024
@ratnampa ratnampa changed the title [Windows][XPU] Fix MSVC ambiguous symbol error [Windows XPU] Fix MSVC ambiguous symbol error Oct 23, 2024
@colesbury colesbury requested a review from EikanWang October 23, 2024 20:02
@colesbury colesbury added the triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module label Oct 23, 2024
@EikanWang EikanWang requested a review from atalman October 30, 2024 04:20
@EikanWang EikanWang added this to the 2.6.0 milestone Oct 30, 2024
@EikanWang EikanWang added the ciflow/xpu Run XPU CI tasks label Oct 30, 2024
@EikanWang
Copy link
Collaborator

@pytorchbot rebase

@pytorchmergebot
Copy link
Collaborator

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

@pytorchmergebot
Copy link
Collaborator

Successfully rebased ratnampa/msvc_wa_xpu onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via git checkout ratnampa/msvc_wa_xpu && git pull --rebase)

@EikanWang EikanWang removed the request for review from atalman October 30, 2024 12:54
@EikanWang EikanWang marked this pull request as draft October 30, 2024 12:54
Copy link
Collaborator
@EikanWang EikanWang left a comment

Choose a reason for hiding this comment

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

Pls. fix ci failures

@guangyey
Copy link
Collaborator
guangyey commented Nov 5, 2024

@pytorchbot rebase -b main

@pytorchmergebot
Copy link
Collaborator

@pytorchbot started a rebase job onto refs/remotes/origin/main. Check the current status here

@pytorchmergebot
Copy link
Collaborator

Successfully rebased ratnampa/msvc_wa_xpu onto refs/remotes/origin/main, please pull locally before adding more changes (for example, via git checkout ratnampa/msvc_wa_xpu && git pull --rebase)

@EikanWang
Copy link
Collaborator

@ratnampa , pls. fix the lint issue ASAP.

@ratnampa
Copy link
Contributor Author
ratnampa commented Nov 5, 2024

Done

@guangyey
Copy link
Collaborator
guangyey commented Nov 7, 2024

@pytorchbot rebase -b main

@guangyey guangyey marked this pull request as ready for review November 7, 2024 05:49
@pytorchmergebot
Copy link
Collaborator

@pytorchbot started a rebase job onto refs/remotes/origin/main. Check the current status here

@pytorchmergebot
Copy link
Collaborator

Successfully rebased ratnampa/msvc_wa_xpu onto refs/remotes/origin/main, please pull locally before adding more changes (for example, via git checkout ratnampa/msvc_wa_xpu && git pull --rebase)

@@ -1044,6 +1044,9 @@ if(USE_XPU)
add_library(torch_xpu ${Caffe2_XPU_SRCS})
torch_compile_options(torch_xpu) # see cmake/public/utils.cmake
target_compile_definitions(torch_xpu PRIVATE USE_XPU)
if(WIN32)
target_compile_options(torch_xpu PRIVATE /permissive-)
Copy link
Collaborator

Choose a reason for hiding this comment

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

We added the option /permissive- to ask the compiler to disable permissive behaviors and execute strict conformance to avoid ambiguous symbol error on Windows. Please refer to /permissive- for more details.

@ezyang
Copy link
Contributor
ezyang commented Nov 7, 2024

seems like it failing tho

@guangyey
Copy link
Collaborator
guangyey commented Nov 8, 2024

@pytorchbot rebase -b main

@pytorchmergebot
Copy link
Collaborator

@pytorchbot started a rebase job onto refs/remotes/origin/main. Check the current status here

@pytorchmergebot
Copy link
Collaborator

Successfully rebased ratnampa/msvc_wa_xpu onto refs/remotes/origin/main, please pull locally before adding more changes (for example, via git checkout ratnampa/msvc_wa_xpu && git pull --rebase)

@guangyey guangyey added the ciflow/trunk Trigger trunk jobs on your pull request label Nov 8, 2024
@guangyey
Copy link
Collaborator
guangyey commented Nov 8, 2024

seems like it failing tho

Thanks, the failure is related to #140095, introduced by inductor UT and irrelevant to this PR.

@guangyey
Copy link
Collaborator
guangyey commented Nov 8, 2024

"failure is related to Linux inductor UT, irrelevant to this PR"
@pytorchbot merge -i

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged while ignoring the following 2 checks: xpu / linux-jammy-xpu-py3.9 / test (default, 1, 4, linux.idc.xpu), xpu / linux-jammy-xpu-py3.9 / test (default, 2, 4, linux.idc.xpu)

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

pytorch-bot bot pushed a commit that referenced this pull request Nov 11, 2024
PT master build with XPU will fail due to MSVC issue of ambiguous symbol error 'std', previously fixed it with MSVC flag in torch-xpu-ops https://github.com/intel/torch-xpu-ops/pull/946/files, but the error is observed in PT master too after 2.5 and oneAPI update.

Pull Request resolved: #138727
Approved by: https://github.com/guangyey, https://github.com/ezyang
zero000064 pushed a commit to zero000064/pytorch that referenced this pull request Nov 14, 2024
PT master build with XPU will fail due to MSVC issue of ambiguous symbol error 'std', previously fixed it with MSVC flag in torch-xpu-ops https://github.com/intel/torch-xpu-ops/pull/946/files, but the error is observed in PT master too after 2.5 and oneAPI update.

Pull Request resolved: pytorch#138727
Approved by: https://github.com/guangyey, https://github.com/ezyang
Ryo-not-rio pushed a commit to Ryo-not-rio/pytorch that referenced this pull request Dec 2, 2024
PT master build with XPU will fail due to MSVC issue of ambiguous symbol error 'std', previously fixed it with MSVC flag in torch-xpu-ops https://github.com/intel/torch-xpu-ops/pull/946/files, but the error is observed in PT master too after 2.5 and oneAPI update.

Pull Request resolved: pytorch#138727
Approved by: https://github.com/guangyey, https://github.com/ezyang
pobin6 pushed a commit to pobin6/pytorch that referenced this pull request Dec 5, 2024
PT master build with XPU will fail due to MSVC issue of ambiguous symbol error 'std', previously fixed it with MSVC flag in torch-xpu-ops https://github.com/intel/torch-xpu-ops/pull/946/files, but the error is observed in PT master too after 2.5 and oneAPI update.

Pull Request resolved: pytorch#138727
Approved by: https://github.com/guangyey, https://github.com/ezyang
fmo-mt pushed a commit to fmo-mt/pytorch that referenced this pull request Dec 11, 2024
PT master build with XPU will fail due to MSVC issue of ambiguous symbol error 'std', previously fixed it with MSVC flag in torch-xpu-ops https://github.com/intel/torch-xpu-ops/pull/946/files, but the error is observed in PT master too after 2.5 and oneAPI update.

Pull Request resolved: pytorch#138727
Approved by: https://github.com/guangyey, https://github.com/ezyang
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ciflow/trunk Trigger trunk jobs on your pull request ciflow/xpu Run XPU CI tasks Merged open source topic: not user facing topic category triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

7 participants
0