o h@sUddlZddlZddlZddlZddlZddlZddlZddlZddlZddl Z ddl Z ddl Z ddl Z ddl Z ddlmZddlZddlZddlZddlmZddlmZddlmZddlmZddlmZmZdd lmZm Z dd l!m"Z"e j#d kZ$e j#%d Z&e j#%d Z'e$rdndZ(e$rdndZ)e$rdndZ*e$rdndZ+e$rdndZ,ej-.e/Z0ej-1ej-1e0Z2ej-3e2dZ4e$rdndZ5dZ6dZ7e8e8e9dfe8e9dffZ:e;ee=e?d<d Z@e@dfe@d!fe@d!fe@d"fe@d"fe@d#fe@d#fd$ZAe=e?d%<gd&ZBd'eeCe<d(eCe<fd)d*ZDd(ee<fd+d,ZEd(ee<fd-d.ZFd(ee<fd/d0ZGd(eejQjRUd?dd@DZTejVWreEndZXejYZdApejYZdBZ[ej\WreGndZ]e^dCZ_gdDZ`gdEZagdFZbgdGZcgdHZddIdJgZedKdLZfgeedMdNdOefdPZgeZhdQdRdSZidTZjdUdVZkd(elfdWdXZmd(eCe<fdYdZZnd[d\Zod(e[s$z"_nt_quote_args..r)r8rrr>_nt_quote_argsRsr@cCstjdp tjd}|durCtd}|dur$tjtj|}ntr9td}t |dkr4d}n|d}nd}tj |sCd}|rUt j sUtd |d tjd |S) zFind the CUDA install path. CUDA_HOME CUDA_PATHNnvccz7C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v*.*rrz/usr/local/cudaz+No CUDA runtime is found, using CUDA_HOME=''file)osenvirongetshutilwhichpathdirname IS_WINDOWSgloblenexiststorchcuda is_availableprintsysstderr) cuda_home nvcc_path cuda_homesrrr>_find_cuda_home]s(     r[cCstjdp tjd}|dur@td}|dur6tjtjtj|}tj|dkr5tj|}n d}tj |r@|}|rSt j j durSt d|dtjd |S) zFind the ROCm install path. ROCM_HOME ROCM_PATHNhipcchipz /opt/rocmz+No ROCm runtime is found, using ROCM_HOME='rDrE)rGrHrIrJrKrLrMrealpathbasenamerQrRversionr_rUrVrW) rocm_home hipcc_path fallback_pathrrr>_find_rocm_homexs$      rfcCsd}td}|durtjtjtj|}|Sz&tjdp#g}|D]}|j dkr>tjt | j }W|Sq&W|StjjyTtdtjdY|Sw)Nicpxz intel-sycl-rtz libsycl.sozMTrying to find SYCL_HOME from intel-sycl-rt package, but it is not installed.rE)rJrKrGrLrMr` importlibmetadatafilesnamerlocateparentresolvePackageNotFoundErrorrUrVrW) sycl_home icpx_pathrjfrrr>_find_sycl_homes.    rscGs0tdurtdtrtdtjjtg|RS)z Join paths with ROCM_HOME, or raises an error if it ROCM_HOME is not set. This is basically a lazy way of raising an error for missing $ROCM_HOME only once we need to get any ROCm-specific path. NzSROCM_HOME environment variable is not set. Please set it to your ROCm install root.zDBuilding PyTorch extensions using ROCm and Windows is not supported.)r\OSErrorrNrGrLjoinpathsrrr>_join_rocm_homes rxcG$tdurtdtjjtg|RS)z Join paths with SYCL_HOME, or raises an error if it SYCL_HOME is not found. This is basically a lazy way of raising an error for missing SYCL_HOME only once we need to get any SYCL-specific path. NzSYCL runtime is not dected. Please setup the pytorch prerequisites for Intel GPU following the instruction in https://github.com/pytorch/pytorch?tab=readme-ov-file#intel-gpu-support or install intel-sycl-rt via pip.) SYCL_HOMErtrGrLrurvrrr>_join_sycl_homesr{a8 !! WARNING !! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Your compiler ({}) may be ABI-incompatible with PyTorch! Please use a compiler that is ABI-compatible with GCC 5.0 and above. See https://gcc.gnu.org/onlinedocs/libstdc++/manual/abi.html. See https://gist.github.com/goldsborough/d466f43e8ffc948ff92de7486c5216d6 for instructions on how to install GCC 5 or higher. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !! WARNING !! a !! WARNING !! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Your compiler ({user_compiler}) is not compatible with the compiler Pytorch was built with for this platform, which is {pytorch_compiler} on {platform}. Please use {pytorch_compiler} to to compile your extension. Alternatively, you may compile PyTorch from source using {user_compiler}, and then you can also use {user_compiler} to compile your extension. See https://github.com/pytorch/pytorch/blob/master/CONTRIBUTING.md for help with compiling PyTorch from source. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !! WARNING !! z The detected CUDA version ({0}) mismatches the version that was used to compile PyTorch ({1}). Please make sure to use the same CUDA versions. zThe detected CUDA version ({0}) has a minor version mismatch with the version that was used to compile PyTorch ({1}). Most likely this shouldn't be a problem.z CUDA was not found on the system, please set the CUDA_HOME or the CUDA_PATH environment variable or add NVCC to your system PATH. The extension compilation will fail. r_TFccs|]}t|VqdSN)int)r<vrrr> r. CUDNN_HOME CUDNN_PATHz\d+\.\d+\.\d+\w+\+\w+) z/MDz/wd4819z/wd4251z/wd4244z/wd4267z/wd4275z/wd4018z/wd4190z/wd4624z/wd4067z/wd4068z/EHsc)&base_class_has_different_dll_interfacefield_without_dll_interface#dll_interface_conflict_none_assumed(dll_interface_conflict_dllexport_assumed)z-D__CUDA_NO_HALF_OPERATORS__z-D__CUDA_NO_HALF_CONVERSIONS__z"-D__CUDA_NO_BFLOAT16_CONVERSIONS__z-D__CUDA_NO_HALF2_OPERATORS__z--expt-relaxed-constexpr)-fPICz-D__HIP_PLATFORM_AMD__=1z -DUSE_ROCM=1z -DHIPBLAS_V2)z-DCUDA_HAS_FP16=1z-D__HIP_NO_HALF_OPERATORS__=1z-D__HIP_NO_HALF_CONVERSIONS__=1z-fsyclz -fsycl-targets=spir64_gen,spir64cCs8dtjvr tjdStj}dd|D}d|S)NTORCH_XPU_ARCH_LISTcSsg|] }|ds|qS)zdg2- startswithr<xrrr>r?)z'_get_sycl_arch_list..,)rGrHrIrRxpu get_arch_listru) arch_listrrr>_get_sycl_arch_list"s    rz -fsycl-linkz--offload-compressz -Xs "-device r;x86 x86_amd64)r z win-amd64 0x03090000cCs(tr tjdd}|Stjdd}|S)NCXXclc++)rNrGrHrI)compilerrrr>r6<s r6cCsttjj Sr|)!BUILT_FROM_SOURCE_VERSION_PATTERNmatchrRrb __version__rrrr>_is_binary_buildCsrcCstrddgSgdS)Nclang++clang)zg++gcczgnu-c++zgnu-ccrr)IS_MACOSrrrr> _accepted_compilers_for_platformGsrcCstj|r$t| }|}Wdn1swY||kr$dSt|d}||WddS1s:wYdS)z Equivalent to writing the content into the file but will not touch the file if it already had the right content (to avoid triggering recompile). Nw)rGrLrQopenreadwrite)filename new_contentrrcontent source_filerrr> _maybe_writeKs     "rcCstjtjjddS)a Return the path to the root folder under which extensions will built. For each extension module built, there will be one folder underneath the folder returned by this function. For example, if ``p`` is the path returned by this function and ``ext`` the name of an extension, the build folder for the extension will be ``p/ext``. This directory is **user-specific** so that multiple users on the same machine won't meet permission issues. torch_extensions)appname)rGrLr`rR_appdirsuser_cache_dirrrrr>r([s r(rcstrdSt|durdStjtfddtDr#dStj }d|d<t j |dgt j |d j t}trwtd tj}t||}t|d krSd |vStj|d tjdkrkd|vrkdStfddtDStr~|dSdS)a Verify that the compiler is the expected one for the current platform. Args: compiler (str): The compiler executable to check. Returns: True if the compiler is gcc/g++ on Linux or clang/clang++ on macOS, and always True for Windows. TNFc3|]}|vVqdSr|rr<rk compiler_pathrr>r}rz1check_compiler_ok_for_platform..CLC_ALL-vrWenv^COLLECT_GCC=(.*)$rz clang versionrr gcc versionc3rr|rrrrr>rrz Apple clang)rNrJrKrGrLr`anyrrHcopy subprocess check_outputSTDOUTdecodeSUBPROCESS_DECODE_ARGSIS_LINUXrecompile MULTILINEfindallrPstriprarr)rrversion_stringpatternresultsrrr>r)js.       r)c Csts dtdfStjddvrdtdfSt|s0ttj |t dt j ddtdfSt r8dtdfSzr*sB     r* compiler_namecompiler_versioncCststttjtdd}t|dgj t }t d|}|dur&dS| d}t|}tjjdur7dSttjj}||krht|dddurMtd|j|jkr]tt|tjjtt|tjjtjdrytjd d vryts{dS|d rt nt!}||vrtd |d |dS||\} } d|vr|t!krd} dt"t#| } dt"t#| } d| d| } |t$| krtd|d|d|d| d|d| d |t$| krtd|d|d|d|d| d dS)NbinrC --versionzrelease (\d+[.]\d+)rmajorzsetuptools>=49.4.0 is requiredrrrrz There are no z) version bounds defined for CUDA version zV11.4.48rrz>=z, _check_cuda_versionsn         rcCs$tdd|Ds|ddSdS)Ncs|]}|dVqdS)z -sycl-std=Nrr<flagrrr>rz5_append_sycl_std_if_no_std_present..z-sycl-std=2020)rappendcflagsrrr>"_append_sycl_std_if_no_std_presentsr cCs$t}d|td|g}|S)Nz-fsycl-host-compiler=z-fsycl-host-compiler-options=)r6shlexquote)r host_cxx host_cflagsrrr>_wrap_sycl_host_flagss rcseZdZdZeddZdfdd Zdfdd Zdd d Zfd d Z de e e ffddZ ddZddZddZddZZS)r+a A custom :mod:`setuptools` build extension . This :class:`setuptools.build_ext` subclass takes care of passing the minimum required compiler flags (e.g. ``-std=c++17``) as well as mixed C++/CUDA/SYCL compilation (and support for CUDA/SYCL files in general). When using :class:`BuildExtension`, it is allowed to supply a dictionary for ``extra_compile_args`` (rather than the usual list) that maps from languages/compilers (the only expected values are ``cxx``, ``nvcc`` or ``sycl``) to a list of additional compiler flags to supply to the compiler. This makes it possible to supply different flags to the C++, CUDA and SYCL compiler during mixed compilation. ``use_ninja`` (bool): If ``use_ninja`` is ``True`` (default), then we attempt to build using the Ninja backend. Ninja greatly speeds up compilation compared to the standard ``setuptools.build_ext``. Fallbacks to the standard distutils backend if Ninja is not available. .. note:: By default, the Ninja backend uses #CPUS + 2 workers to build the extension. This may use up too many resources on some systems. One can control the number of workers by setting the `MAX_JOBS` environment variable to a non-negative number. c sGfddd|}|S)zReturn a subclass with alternative constructor that extends any original keyword arguments to the original constructor with the given options.cseZdZfddZZS)z5BuildExtension.with_options..cls_with_optionscs |tj|i|dSr|)updatesuper__init__)selfr8kwargs) __class__optionsrr>r0s z>BuildExtension.with_options..cls_with_options.__init__)__name__ __module__ __qualname__r __classcell__rrrr>cls_with_options/sr r)clsrr rrr> with_options,szBuildExtension.with_optionsr9Ncs`tj|i||dd|_|dd|_|jr,d}ts.t|dd|_dSdSdS)Nno_python_abi_suffixF use_ninjaTznAttempted to use ninja as the BuildExtension backend but {}. Falling back to using the slow distutils backend.zwe could not find ninja.) rrrIr#r$r3rrr)rr8rmsgrrr>r6s zBuildExtension.__init__cst|jr d|_dSdS)NT)rfinalize_optionsr$forcerrrr>r&Cs  zBuildExtension.finalize_optionsc s\}}d}d}tj}t|d}|r|sF|rF|jD]}tj|\}} | dkr.d}n| dkr4d}|r:|r:nqt|d}|rD|sF|s|rOjsOJd|rXt sXt ||jD]m}t |j t rrdD] } | |j vrqg|j | <qe|dt r||jr|dtn!d D]} ttjd | } | durts|d | d | d q||d|j vrȈjsJd|jdq[jjgd7_tjjrjjdg7_jjdkrjjddg7_jj jj!njj"d'fdd ddddd'fdd }  d(fdd } d!d"  d(fd#d$ }  d(fd%d& }jjdkrejr`|j_ n|j_ n jrn| j_ n| j_"t#$dS))NF.cuT.syclz+ninja is required to build sycl extensions.)cxxrCsycl-DTORCH_API_INCLUDE_EXTENSION_Hz-DPy_LIMITED_API= COMPILER_TYPESTDLIB BUILD_ABI _PYBIND11_ -DPYBIND11_z="r; nvcc_dlinkz;With dlink=True, ninja is required to build cuda extension r)r).cuh.hipr*z.mmmsvcr5r9csNjjdkrdnd}|dd}tfdd|Ds%||dSdS)Nr7z/{}:z-{}=stdzc++17c3s|]}|VqdSr|rrcpp_flag_prefixrr>rr zZBuildExtension.build_extensions..append_std17_if_no_std_present..)r compiler_typerrr )r cpp_format_prefixcpp_flagr(r9r>append_std17_if_no_std_presents  zGBuildExtension.build_extensions..append_std17_if_no_std_presentcSsNtddg|t|}td}|dur%tdd|Ds%|d|g|S)N--compiler-options'-fPIC'CCcsr))-ccbinz--compiler-bindirNrrrrr>rr zKBuildExtension.build_extensions..unix_cuda_flags..rB)COMMON_NVCC_FLAGS_get_cuda_arch_flagsrGgetenvrextend)r _ccbinrrr>unix_cuda_flagss z8BuildExtension.build_extensions..unix_cuda_flagscSsF|durtt|D]}tj||stj||||<q dSdSr|)rangerPrGrLisabsabspath)rwirrr>!convert_to_absolute_paths_inplaceszJBuildExtension.build_extensions..convert_to_absolute_paths_inplacec st|}z[jj}t|r;trtddntddg}jd|t |t r+|d}tr6t |t |}n|}n t |t rD|d}trJt |}|||||||Wjd|dSjd|w)Nrr^rC compiler_sor+)rdeepcopyrrN _is_cuda_fileIS_HIP_EXTENSIONrx_join_cuda_homeset_executable isinstancedictCOMMON_HIPCC_FLAGS_get_rocm_arch_flagsCOMMON_HIP_FLAGS) objsrcextcc_argsextra_postargspp_optsr original_compilerrC)r>original_compilerrHrr>unix_wrap_single_compiles$    "zABuildExtension.build_extensions..unix_wrap_single_compilercstj|}jjj||||||\}} }} }j| ||} jjdd} tt t |} tt t |}t |t rD|d}nt|}trNt|}|d}d}| r| }t |t rd|d}nt|}trw|t|}tt|}n|}|dd|D}dd|D}t |t rd|vr|d}nd}d}d}d}|r| | t}t |t r|d }nt|}|t|| | |}|d d|D}d |}d d|D}|t|7}t}d d|D}t|| dd| | Ddd|D|||||||d| |d| S)z;Compiles sources by outputting a ninja file and running it.rNr+rCcSg|]}t|qSrrrr<rrrrr>r?zTBuildExtension.build_extensions..unix_wrap_ninja_compile..cSrbrrcrdrrr>r?rer4r,cSg|]}|ddqS)r;\\"replacer<itemrrr>r?%r:cSrbrrcrdrrr>r?*recSrbrrcrdrrr>r?-recSrbrrcrdrrr>r?2recSrbrrcrdrrr>r?3reTsourcesobjectsr  post_cflags cuda_cflagscuda_post_cflagscuda_dlink_post_cflags sycl_cflagssycl_post_cflagssycl_dlink_post_cflagsbuild_directoryverbose with_cuda with_sycl)rGrLrKr include_dirs_setup_compile _get_cc_argsrNrrrP _is_sycl_filerTrUrrQrXrWrV_COMMON_SYCL_FLAGSr rur_SYCL_DLINK_FLAGS%_write_ninja_file_and_compile_objects)rn output_dirmacrosr{debug extra_preargsr]dependsrror^ common_cflagsextra_cc_cflagsryrzrprrrqrsrurtrvr)r>rMrrHrr>unix_wrap_ninja_compiles                z@BuildExtension.build_extensions..unix_wrap_ninja_compilecSst|t|Sr|)rCrDr rrr>win_cuda_flagsBs z7BuildExtension.build_extensions..win_cuda_flagsc sVt|_d}fdd}z|j_||||||||Wj_Sj_w)Nc stdddfdd|DD}tdddfdd|DD}td d dfd d|DD}t|d krt|d kr|d }|d }t|rtdd}tjtrbjd}n tjtrlj}ng}|ddg}t D]}d|g|}qxt D] } dd| g|}q|d|d|g||}|Stjtrt jd}|||7}|Stjtrt j}|||7}|S)Nz /T(p|c)(.*)cSg|] }|r|dqS)rrr<mrrr>r?U zcBuildExtension.build_extensions..win_wrap_single_compile..spawn..c3|]}|VqdSr|rr<elem) src_regexrr>rVr zbBuildExtension.build_extensions..win_wrap_single_compile..spawn..z/Fo(.*)cSrrrrrrr>r?[rc3rr|rr) obj_regexrr>r\r z ((\-|\/)I.*)cSrrrrrrr>r?as c3rr|rr) include_regexrr>rcr rrrrC -std=c++17--use-local-env -Xcompiler-Xcudafe--diag_suppress=z-cz-or+) rrrPrPrRrTr rUrCOMMON_MSVC_FLAGSMSVC_IGNORE_CUDAFE_WARNINGS) cmdsrc_listobj_list include_listrZrYrCr rignore_warning)r>original_spawnrr)rrrr>spawnRsN         zOBuildExtension.build_extensions..win_wrap_single_compile..spawn)rrOr rr) rnrrr{rrr]rr)r>r`rrrrr>win_wrap_single_compileFs 1z@BuildExtension.build_extensions..win_wrap_single_compilecsjjs jtj|}jjj||||||\}} }} }|p(g} g} |r5| jj n| jj | t | | | } t t t|} t|trX|d}nt|}|d}d}| rddg}| D] }|d||qltD]}|d|d|q{|| t|tr|d}nt|}|}t| } t|}| rt|}t|}t|trd|vrÈ|d}nd}t|| | ||||ddd|d | d d | S) Nr+rrrrrrCr4TFrm)r initialized initializerGrLrKr{r|rFcompile_options_debugcompile_optionsrrrrPrTrUrr rr@r)rnrrr{rrr]rrror^rr ryrprrrq common_cflagrrs)r>rMrrrr>win_wrap_ninja_compilesz               z?BuildExtension.build_extensions..win_wrap_ninja_compiler9N)NNNrNNN)% _check_abiiter extensionsnextrnrGrLsplitextr$rQrrTextra_compile_argsrU_add_compile_flag_hipify_compile_flagspy_limited_apimin_supported_cpythonrrR_CrN_define_torch_extension_name_add_gnu_cpp_abi_flagrkrsrc_extensionsbackendsmpsis_builtr;_cpp_extensionsrr_compiler build_extensions)rrrcuda_extsycl_extextension_iter extensionsourcerr[rkvalrarrrr)r>rMr`rrrHrr>rHs                      nF\   zBuildExtension.build_extensionscsBt|}|jr|d}|dd|dd}d|}|S)Nr)rget_ext_filenamer#rru)rext_name ext_filenameext_filename_parts without_abirrr>rs   zBuildExtension.get_ext_filenamecCsXt|jdr |jjd}nt}t|\}}tr(dtjvr(dtjvr(d}t|||fS)N compiler_cxxrVSCMD_ARG_TGT_ARCHDISTUTILS_USE_SDKzIt seems that the VC environment is activated but DISTUTILS_USE_SDK is not set.This may lead to multiple activations of the VC env.Please set `DISTUTILS_USE_SDK=1` and try again.) hasattrrrr6r*rNrGrH UserWarning)rrrrbr%rrr>rs  zBuildExtension._check_abicCsHt|j|_t|jtr|jD]}||qdS|j|dSr|)rrOrrTrUvaluesr )rrrr8rrr>rs   z BuildExtension._add_compile_flagc Cst|jtrhd|jvrjg}|jdD]N}|dr[d|vr[|ds[|dd}t|dkrA|\}}|ddd}|d|}n|ddd}||td |d |t j d q||q||jd<dSdSdS) NrC-CUDA-I=rrHIPzModified flag: z -> rE) rTrrUrrrPrir rUrVrW) rrmodified_flagsrparts flag_part value_partmodified_flag_part modified_flagrrr>rs    z$BuildExtension._hipify_compile_flagscCs.|jd}|d}d|}|||dS)Nrr-DTORCH_EXTENSION_NAME=)rkrr)rrnamesrkdefinerrr>r2s  z+BuildExtension._define_torch_extension_namecCs ||dtttjjdSNz-D_GLIBCXX_USE_CXX11_ABI=)rrr}rRr_GLIBCXX_USE_CXX11_ABI)rrrrr>r<s z$BuildExtension._add_gnu_cpp_abi_flagr)rrr__doc__ classmethodr"rr&rrrrr rrrrrrrrrr>r+s     /  r+cOs|dg}|t7}||d<|dg}|t7}||d<|dg}|d|d|d|dds>|d trE|d ||d<d |d <tj||g|Ri|S) aM Create a :class:`setuptools.Extension` for C++. Convenience method that creates a :class:`setuptools.Extension` with the bare minimum (but often sufficient) arguments to build a C++ extension. All arguments are forwarded to the :class:`setuptools.Extension` constructor. Full list arguments can be found at https://setuptools.pypa.io/en/latest/userguide/ext_modules.html#extension-api-reference .. warning:: The PyTorch python API (as provided in libtorch_python) cannot be built with the flag ``py_limited_api=True``. When this flag is passed, it is the user's responsibility in their library to not use APIs from libtorch_python (in particular pytorch/python bindings) and to only use APIs from libtorch (aten objects, operators and the dispatcher). For example, to give access to custom ops from python, the library should register the ops through the dispatcher. Contrary to CPython setuptools, who does not define -DPy_LIMITED_API as a compile flag when py_limited_api is specified as an option for the "bdist_wheel" command in ``setup``, PyTorch does! We will specify -DPy_LIMITED_API=min_supported_cpython to best enforce consistency, safety, and sanity in order to encourage best practices. To target a different version, set min_supported_cpython to the hexcode of the CPython version of choice. Example: >>> # xdoctest: +SKIP >>> # xdoctest: +REQUIRES(env:TORCH_DOCTEST_CPP_EXT) >>> from setuptools import setup >>> from torch.utils.cpp_extension import BuildExtension, CppExtension >>> setup( ... name='extension', ... ext_modules=[ ... CppExtension( ... name='extension', ... sources=['extension.cpp'], ... extra_compile_args=['-g'], ... extra_link_args=['-Wl,--no-as-needed', '-lm']) ... ], ... cmdclass={ ... 'build_ext': BuildExtension ... }) r{ library_dirs librariesc10rR torch_cpurF torch_pythonsleefrlanguage)rIr/r0r rN setuptools Extension)rkrnr8rr{rrrrr>r,As" .          r,c Os&|dg}|tdd7}||d<|dg}|d|d|d|dd s1|d trC|d |d |d n|d|d|d||d<|dg}trt}tj|||tj |dgdd|Ddddd}t } |D]$} tj | } | |vr|| j dur|| j n| } | tj| |qt| }|tdd7}||d<d|d<|dg} |dd p| }|r|di}|dg}|dg7}|dd|D7}|d d| D7}tjjdurttjjd!kr|d"g7}||d<||d<tj||g|Ri|S)#a Create a :class:`setuptools.Extension` for CUDA/C++. Convenience method that creates a :class:`setuptools.Extension` with the bare minimum (but often sufficient) arguments to build a CUDA/C++ extension. This includes the CUDA include path, library path and runtime library. All arguments are forwarded to the :class:`setuptools.Extension` constructor. Full list arguments can be found at https://setuptools.pypa.io/en/latest/userguide/ext_modules.html#extension-api-reference .. warning:: The PyTorch python API (as provided in libtorch_python) cannot be built with the flag ``py_limited_api=True``. When this flag is passed, it is the user's responsibility in their library to not use APIs from libtorch_python (in particular pytorch/python bindings) and to only use APIs from libtorch (aten objects, operators and the dispatcher). For example, to give access to custom ops from python, the library should register the ops through the dispatcher. Contrary to CPython setuptools, who does not define -DPy_LIMITED_API as a compile flag when py_limited_api is specified as an option for the "bdist_wheel" command in ``setup``, PyTorch does! We will specify -DPy_LIMITED_API=min_supported_cpython to best enforce consistency, safety, and sanity in order to encourage best practices. To target a different version, set min_supported_cpython to the hexcode of the CPython version of choice. Example: >>> # xdoctest: +SKIP >>> # xdoctest: +REQUIRES(env:TORCH_DOCTEST_CPP_EXT) >>> from setuptools import setup >>> from torch.utils.cpp_extension import BuildExtension, CUDAExtension >>> setup( ... name='cuda_extension', ... ext_modules=[ ... CUDAExtension( ... name='cuda_extension', ... sources=['extension.cpp', 'extension_kernel.cu'], ... extra_compile_args={'cxx': ['-g'], ... 'nvcc': ['-O2']}, ... extra_link_args=['-Wl,--no-as-needed', '-lcuda']) ... ], ... cmdclass={ ... 'build_ext': BuildExtension ... }) Compute capabilities: By default the extension will be compiled to run on all archs of the cards visible during the building process of the extension, plus PTX. If down the road a new card is installed the extension may need to be recompiled. If a visible card has a compute capability (CC) that's newer than the newest version for which your nvcc can build fully-compiled binaries, PyTorch will make nvcc fall back to building kernels with the newest version of PTX your nvcc does support (see below for details on PTX). You can override the default behavior using `TORCH_CUDA_ARCH_LIST` to explicitly specify which CCs you want the extension to support: ``TORCH_CUDA_ARCH_LIST="6.1 8.6" python build_my_extension.py`` ``TORCH_CUDA_ARCH_LIST="5.2 6.0 6.1 7.0 7.5 8.0 8.6+PTX" python build_my_extension.py`` The +PTX option causes extension kernel binaries to include PTX instructions for the specified CC. PTX is an intermediate representation that allows kernels to runtime-compile for any CC >= the specified CC (for example, 8.6+PTX generates PTX that can runtime-compile for any GPU with CC >= 8.6). This improves your binary's forward compatibility. However, relying on older PTX to provide forward compat by runtime-compiling for newer CCs can modestly reduce performance on those newer CCs. If you know exact CC(s) of the GPUs you want to target, you're always better off specifying them individually. For example, if you want your extension to run on 8.0 and 8.6, "8.0+PTX" would work functionally because it includes PTX that can runtime-compile for 8.6, but "8.0 8.6" would be better. Note that while it's possible to include all supported archs, the more archs get included the slower the building process will be, as it will build a separate kernel image for each arch. Note that CUDA-11.5 nvcc will hit internal compiler error while parsing torch/extension.h on Windows. To workaround the issue, move python binding logic to pure C++ file. Example use: #include at::Tensor SigmoidAlphaBlendForwardCuda(....) Instead of: #include torch::Tensor SigmoidAlphaBlendForwardCuda(...) Currently open issue for nvcc bug: https://github.com/pytorch/pytorch/issues/69460 Complete workaround code example: https://github.com/facebookresearch/pytorch3d/commit/cb170ac024a949f1f9614ffe6af1c38d972f7d48 Relocatable device code linking: If you want to reference device symbols across compilation units (across object files), the object files need to be built with `relocatable device code` (-rdc=true or -dc). An exception to this rule is "dynamic parallelism" (nested kernel launches) which is not used a lot anymore. `Relocatable device code` is less optimized so it needs to be used only on object files that need it. Using `-dlto` (Device Link Time Optimization) at the device code compilation step and `dlink` step helps reduce the protentional perf degradation of `-rdc`. Note that it needs to be used at both steps to be useful. If you have `rdc` objects you need to have an extra `-dlink` (device linking) step before the CPU symbol linking step. There is also a case where `-dlink` is used without `-rdc`: when an extension is linked against a static lib containing rdc-compiled objects like the [NVSHMEM library](https://developer.nvidia.com/nvshmem). Note: Ninja is required to build a CUDA Extension with RDC linking. Example: >>> # xdoctest: +SKIP >>> # xdoctest: +REQUIRES(env:TORCH_DOCTEST_CPP_EXT) >>> CUDAExtension( ... name='cuda_extension', ... sources=['extension.cpp', 'extension_kernel.cu'], ... dlink=True, ... dlink_libraries=["dlink_lib"], ... extra_compile_args={'cxx': ['-g'], ... 'nvcc': ['-O2', '-rdc=true']}) rrS) device_typerrrRrrFramdhip64c10_hip torch_hipcudartc10_cuda torch_cudar{*cSg|]}tj|qSrrGrLrKr<srrr>r?rlz!CUDAExtension..T)project_directoryoutput_directoryheader_include_dirsincludes extra_files show_detailedis_pytorch_extensionhipify_extra_files_onlyNrrdlink_librariesdlinkrr4z-dlinkcSg|]}d|qS)-Lrrrrr>r?9recSr)z-lrrrrr>r?:rerz-dlto)rIr0r rQrGgetcwdrhipifyrLrusetrK hipified_pathaddrelpathrr/rRrbrSr rr)rkrnr8rrrr{ build_dir hipify_resulthipified_sourcesrs_abshipified_s_absrrrextra_compile_args_dlinkrrr>r-sp w                      r-cOs|dg}|t7}||d<|dg}|d|d|d|d|dds4|d |d ||d<|d g}|t7}||d <d |d <tj||g|Ri|S)at Creates a :class:`setuptools.Extension` for SYCL/C++. Convenience method that creates a :class:`setuptools.Extension` with the bare minimum (but often sufficient) arguments to build a SYCL/C++ extension. All arguments are forwarded to the :class:`setuptools.Extension` constructor. .. warning:: The PyTorch python API (as provided in libtorch_python) cannot be built with the flag ``py_limited_api=True``. When this flag is passed, it is the user's responsibility in their library to not use APIs from libtorch_python (in particular pytorch/python bindings) and to only use APIs from libtorch (aten objects, operators and the dispatcher). For example, to give access to custom ops from python, the library should register the ops through the dispatcher. Contrary to CPython setuptools, who does not define -DPy_LIMITED_API as a compile flag when py_limited_api is specified as an option for the "bdist_wheel" command in ``setup``, PyTorch does! We will specify -DPy_LIMITED_API=min_supported_cpython to best enforce consistency, safety, and sanity in order to encourage best practices. To target a different version, set min_supported_cpython to the hexcode of the CPython version of choice. Example: >>> # xdoctest: +SKIP >>> # xdoctest: +REQUIRES(env:TORCH_DOCTEST_CPP_EXT) >>> from torch.utils.cpp_extension import BuildExtension, SyclExtension >>> setup( ... name='xpu_extension', ... ext_modules=[ ... SyclExtension( ... name='xpu_extension', ... sources=['extension.cpp', 'extension_kernel.cpp'], ... extra_compile_args={'cxx': ['-g', '-std=c++20', '-fPIC']}) ... ], ... cmdclass={ ... 'build_ext': BuildExtension ... }) By default the extension will be compiled to run on all archs of the cards visible during the building process of the extension. If down the road a new card is installed the extension may need to be recompiled. You can override the default behavior using `TORCH_XPU_ARCH_LIST` to explicitly specify which device architectures you want the extension to support: ``TORCH_XPU_ARCH_LIST="pvc,xe-lpg" python build_my_extension.py`` Note that while it's possible to include all supported archs, the more archs get included the slower the building process will be, as it will build a separate kernel image for each arch. Note: Ninja is required to build SyclExtension. rrrc10_xpurRrrFr torch_xpur{rr)rIr0r r/rr)rkrnr8rrrr{rrr>r.Fs" 9           r.cpurcCstjtd}|tj|ddddg}|dkr,tr,|tj|d|td|S|dkr_td}|dkr=||tj dd }rO|dkrO||t d ur]|tjt d|S|d krr|t d|t dd |S) z Get the include paths required to build a C++ or CUDA or SYCL extension. Args: device_type: Defaults to "cpu". Returns: A list of include path strings. includerRcsrcapirSTHHz /usr/include CUDA_INC_PATHNrr,) rGrLru _TORCH_PATHrQr rxrRrHrIrr{)r lib_includerwcuda_home_include cuda_inc_pathrrr>r/s,    r/cCs tg}|dkr"tr"d}|t|tdur |tjtd|S|dkr[tr0tjdd}nd}tj t |sDtj t drDd}|t |t durY|tjt ||S|dkrtritjdd}nd}tj t |s}tj t dr}d}|t ||S)z Get the library paths required to build a C++ or CUDA extension. Args: device_type: Defaults to "cpu". Returns: A list of library path strings. rSrNx64lib64r) TORCH_LIB_PATHrQr rxHIP_HOMErGrLrurNrQrRrr{)rrwlib_dirrrr>r0s:  r0rnryrzcCs>t|t|tr |gn|||||||pt|||| | | | | dS)aG Load a PyTorch C++ extension just-in-time (JIT). To load an extension, a Ninja build file is emitted, which is used to compile the given sources into a dynamic library. This library is subsequently loaded into the current Python process as a module and returned from this function, ready for use. By default, the directory to which the build file is emitted and the resulting library compiled to is ``/torch_extensions/``, where ```` is the temporary folder on the current platform and ```` the name of the extension. This location can be overridden in two ways. First, if the ``TORCH_EXTENSIONS_DIR`` environment variable is set, it replaces ``/torch_extensions`` and all extensions will be compiled into subfolders of this directory. Second, if the ``build_directory`` argument to this function is supplied, it overrides the entire path, i.e. the library will be compiled into that folder directly. To compile the sources, the default system compiler (``c++``) is used, which can be overridden by setting the ``CXX`` environment variable. To pass additional arguments to the compilation process, ``extra_cflags`` or ``extra_ldflags`` can be provided. For example, to compile your extension with optimizations, pass ``extra_cflags=['-O3']``. You can also use ``extra_cflags`` to pass further include directories. CUDA support with mixed compilation is provided. Simply pass CUDA source files (``.cu`` or ``.cuh``) along with other sources. Such files will be detected and compiled with nvcc rather than the C++ compiler. This includes passing the CUDA lib64 directory as a library directory, and linking ``cudart``. You can pass additional flags to nvcc via ``extra_cuda_cflags``, just like with ``extra_cflags`` for C++. Various heuristics for finding the CUDA install directory are used, which usually work fine. If not, setting the ``CUDA_HOME`` environment variable is the safest option. SYCL support with mixed compilation is provided. Simply pass SYCL source files (``.sycl``) along with other sources. Such files will be detected and compiled with SYCL compiler (such as Intel DPC++ Compiler) rather than the C++ compiler. You can pass additional flags to SYCL compiler via ``extra_sycl_cflags``, just like with ``extra_cflags`` for C++. SYCL compiler is expected to be found via system PATH environment variable. Args: name: The name of the extension to build. This MUST be the same as the name of the pybind11 module! sources: A list of relative or absolute paths to C++ source files. extra_cflags: optional list of compiler flags to forward to the build. extra_cuda_cflags: optional list of compiler flags to forward to nvcc when building CUDA sources. extra_sycl_cflags: optional list of compiler flags to forward to SYCL compiler when building SYCL sources. extra_ldflags: optional list of linker flags to forward to the build. extra_include_paths: optional list of include directories to forward to the build. build_directory: optional path to use as build workspace. verbose: If ``True``, turns on verbose logging of load steps. with_cuda: Determines whether CUDA headers and libraries are added to the build. If set to ``None`` (default), this value is automatically determined based on the existence of ``.cu`` or ``.cuh`` in ``sources``. Set it to `True`` to force CUDA headers and libraries to be included. with_sycl: Determines whether SYCL headers and libraries are added to the build. If set to ``None`` (default), this value is automatically determined based on the existence of ``.sycl`` in ``sources``. Set it to `True`` to force SYCL headers and libraries to be included. is_python_module: If ``True`` (default), imports the produced shared library as a Python module. If ``False``, behavior depends on ``is_standalone``. is_standalone: If ``False`` (default) loads the constructed extension into the process as a plain dynamic library. If ``True``, build a standalone executable. Returns: If ``is_python_module`` is ``True``: Returns the loaded PyTorch extension as a Python module. If ``is_python_module`` is ``False`` and ``is_standalone`` is ``False``: Returns nothing. (The shared library is loaded into the process as a side effect.) If ``is_standalone`` is ``True``. Return the path to the executable. (On Windows, TORCH_LIB_PATH is added to the PATH environment variable as a side effect.) Example: >>> # xdoctest: +SKIP >>> from torch.utils.cpp_extension import load >>> module = load( ... name='extension', ... sources=['extension.cpp', 'extension_kernel.cu'], ... extra_cflags=['-O2'], ... verbose=True) keep_intermediates) _jit_compilerTr_get_build_directory)rkrn extra_cflagsextra_cuda_cflagsextra_sycl_cflags extra_ldflagsextra_include_pathsrwrxryrzis_python_module is_standaloner&rrr>r1s m r1cCsHg}dD]}ttjd|}|dur!ts!|d|d|dq|S)Nr.r2r3z=\"\")rrRrrNr ) abi_cflagspnamepvalrrr>_get_pybind11_abi_build_flagsgs  r4cCsdtttjjg}|Sr)rr}rRrr)glibcxx_abi_cflagsrrr>_get_glibcxx_abi_build_flags{sr6c CstsdStj}d|d<ztj|dgtj|djt}Wn%t yBztj|dgtj|djt}Wn t y?YYdSwYnwt dt j }t ||}t|dkrXdStj|d }tj|d krpd |vrpd SdS) NFrrrrrrrrrrT)rrGrHrrrrrrrrrrrrPrLr`rra)rrrrrrrrr>r7s,       r7c stsdSt}t|}|durdStjtddd}tjtddd}tjtddd}dd }d d } d d } dd} ddfdd} dd} ||}d|rYdd|Dng}tjtd}d|dt ddtj|ddddg}||}g}|s|dg7}|ddg7}|d dt D7}|d!dt D7}||}| |||||||}| |}tj |d"ur| || ||dS| ||}|dur| || ||dSdS)#aP Precompiled Headers(PCH) can pre-build the same headers and reduce build time for pytorch load_inline modules. GCC offical manual: https://gcc.gnu.org/onlinedocs/gcc-4.0.4/gcc/Precompiled-Headers.html PCH only works when built pch file(header.h.gch) and build target have the same build parameters. So, We need add a signature file to record PCH file parameters. If the build parameters(signature) changed, it should rebuild PCH file. Note: 1. Windows and MacOS have different PCH mechanism. We only support Linux currently. 2. It only works on GCC/G++. NFrrRz extension.hextension.h.gchextension.h.signcSs*d}|dur|S|D]}||d7}q |S)Nrr:r)rstringelementrrr> listToStrings zF_check_and_build_extension_h_precompiler_headers..listToStringcSs>tddd|d|d|d|d|d|d|dS)Nz[ \n]+r:z z -x c++-header z -o z )rsubr)r head_file head_file_pchrtorch_include_dirsr)r-rrr>format_precompiler_header_cmds*zW_check_and_build_extension_h_precompiler_headers..format_precompiler_header_cmdcSs|dd}|S)Nr:rrh)r signaturerrr>command_to_signatures zN_check_and_build_extension_h_precompiler_headers..command_to_signaturecSsTtj|}|dur dSt|}|}||kWdS1s#wYdS)NF)rGrLisfilerr) file_pathrAb_existrFrrrr>check_pch_signature_in_files  $zU_check_and_build_extension_h_precompiler_headers..check_pch_signature_in_filec Ssltj|s4z t|jdddWdSty3}z|jtjkr(td||WYd}~dSd}~wwdS)NT)parentsexist_okzFail to create path ) rGrLrQrmkdirrterrnoEEXISTr)path_direxcrrr>_create_if_not_exists  zN_check_and_build_extension_h_precompiler_headers.._create_if_not_existcsRtj|t|d}|||WddS1s"wYdS)Nr)rGrLrMrrclose)rDpch_signrrrNrr>write_pch_signature_to_files    "zU_check_and_build_extension_h_precompiler_headers..write_pch_signature_to_filec SsDz tj|dtjdWdStjy!}ztd||d}~ww)NT)shellrWz)Compile PreCompile Header fail, command: )rrrCalledProcessErrorr)pch_cmderrr>build_precompile_headers zQ_check_and_build_extension_h_precompiler_headers..build_precompile_headerr:cSrrrr<rrrr>r?rezD_check_and_build_extension_h_precompiler_headers..z-I z-I {}rrr-rrcSg|]}|qSrrrrrr>r?cSrZrrrrrr>r?r[T) rr6r7rGrLrurr sysconfigget_pathr4r6rC)r)r-r/rb_is_gccr=r>head_file_signaturer;r@rBrFrRrWextra_cflags_strextra_include_paths_strrr?torch_include_dirs_strrcommon_cflags_strrUrP b_same_signrrQr>0_check_and_build_extension_h_precompiler_headerssV      recCs@dd}tjtddd}tjtddd}||||dS)NcSstj|r t|dSdSr|)rGrLrQremove) path_filerrr>_remove_if_file_existss zFremove_extension_h_precompiler_headers.._remove_if_file_existsrrRr7r8)rGrLrur)rhr>r_rrr>r5s  r5cCs| pt|| } t|tr|g}|pg}t|tr|g}|pg}t|tr'|g}|dd|dur7t|| nt|durg}|dt|trM|g}t|trZdd|D}nt|tsht dt || D]%\}}|r|d |d |d |d ql|d |d |d|d ql|d||7}t j | d}t|d||g}|r|dd|dd|ddt j | d}t|d||||r|dd|ddt j | d}t|d|||t||||||| | | | | |d|dS)a  Load a PyTorch C++ extension just-in-time (JIT) from string sources. This function behaves exactly like :func:`load`, but takes its sources as strings rather than filenames. These strings are stored to files in the build directory, after which the behavior of :func:`load_inline` is identical to :func:`load`. See `the tests `_ for good examples of using this function. Sources may omit two required parts of a typical non-inline C++ extension: the necessary header includes, as well as the (pybind11) binding code. More precisely, strings passed to ``cpp_sources`` are first concatenated into a single ``.cpp`` file. This file is then prepended with ``#include ``. Furthermore, if the ``functions`` argument is supplied, bindings will be automatically generated for each function specified. ``functions`` can either be a list of function names, or a dictionary mapping from function names to docstrings. If a list is given, the name of each function is used as its docstring. The sources in ``cuda_sources`` are concatenated into a separate ``.cu`` file and prepended with ``torch/types.h``, ``cuda.h`` and ``cuda_runtime.h`` includes. The ``.cpp`` and ``.cu`` files are compiled separately, but ultimately linked into a single library. Note that no bindings are generated for functions in ``cuda_sources`` per se. To bind to a CUDA kernel, you must create a C++ function that calls it, and either declare or define this C++ function in one of the ``cpp_sources`` (and include its name in ``functions``). The sources in ``sycl_sources`` are concatenated into a separate ``.sycl`` file and prepended with ``torch/types.h``, ``sycl/sycl.hpp`` includes. The ``.cpp`` and ``.sycl`` files are compiled separately, but ultimately linked into a single library. Note that no bindings are generated for functions in ``sycl_sources`` per se. To bind to a SYCL kernel, you must create a C++ function that calls it, and either declare or define this C++ function in one of the ``cpp_sources`` (and include its name in ``functions``). See :func:`load` for a description of arguments omitted below. Args: cpp_sources: A string, or list of strings, containing C++ source code. cuda_sources: A string, or list of strings, containing CUDA source code. sycl_sources: A string, or list of strings, containing SYCL source code. functions: A list of function names for which to generate function bindings. If a dictionary is given, it should map function names to docstrings (which are otherwise just the function names). with_cuda: Determines whether CUDA headers and libraries are added to the build. If set to ``None`` (default), this value is automatically determined based on whether ``cuda_sources`` is provided. Set it to ``True`` to force CUDA headers and libraries to be included. with_sycl: Determines whether SYCL headers and libraries are added to the build. If set to ``None`` (default), this value is automatically determined based on whether ``sycl_sources`` is provided. Set it to ``True`` to force SYCL headers and libraries to be included. with_pytorch_error_handling: Determines whether pytorch error and warning macros are handled by pytorch instead of pybind. To do this, each function ``foo`` is called via an intermediary ``_safe_foo`` function. This redirection might cause issues in obscure cases of cpp. This flag should be set to ``False`` when this redirect causes issues. Example: >>> # xdoctest: +REQUIRES(env:TORCH_DOCTEST_CPP_EXT) >>> from torch.utils.cpp_extension import load_inline >>> source = """ at::Tensor sin_add(at::Tensor x, at::Tensor y) { return x.sin() + y.sin(); } """ >>> module = load_inline(name='inline_extension', ... cpp_sources=[source], ... functions=['sin_add']) .. note:: Since load_inline will just-in-time compile the source code, please ensure that you have the right toolchains installed in the runtime. For example, when loading C++, make sure a C++ compiler is available. If you're loading a CUDA extension, you will need to additionally install the corresponding CUDA toolkit (nvcc and any other dependencies your code has). Compiling toolchains are not included when you install torch and must be additionally installed. During compiling, by default, the Ninja backend uses #CPUS + 2 workers to build the extension. This may use up too many resources on some systems. One can control the number of workers by setting the `MAX_JOBS` environment variable to a non-negative number. rz#include TNz*PYBIND11_MODULE(TORCH_EXTENSION_NAME, m) {cSsi|]}||qSrrrdrrr> r[zload_inline..z3Expected 'functions' to be a list or dict, but was zm.def("z", torch::wrap_pybind_function(z), "z");z", z, "}zmain.cpp z#include rz#include rz#include zcuda.cuz#include z sycl.syclF)r/r&)r(rTrinsertrer5r rrUrtypeitemsrGrLrurr')rk cpp_sources cuda_sources sycl_sources functionsr)r*r+r,r-rwrxryrzr.with_pytorch_error_handlingr&use_pch module_def function_name docstringcpp_source_pathrncuda_source_pathsycl_source_pathrrr>r2sxo                   r2rwrxcCsT| r| rtd| durttt|} tdd|pgD}| dur)ttt|} t|}tj||||||g|| | | | d}|dkrg||kr`|r`td|dd|d |d |d t j d |d |}t t j |d }|r z||krt| dj}tr| s|rtj|||dur|ngdd|Dtdt j tdg||d|d }t}|D]}t j |}|||vr||jn|qt|}t|||pg|pg|pg|pg|pg||| | | d Wdn1swYn |rtd|dt j d W|n |w||rtd|d t j d | r$t||St||| S)Nz>`is_python_module` and `is_standalone` are mutually exclusive.css|]}d|vVqdS)cudnnNrrdrrr>rrz_jit_compile..)build_argumentsrwryrzr.r/rz*The input conditions for extension module z have changed. zBumping to version z and re-building as _v...rElockr%cSrrrrrrr>r? rlz _jit_compile..rT) rrrrignoresr show_progressr clean_ctx) rkrnr)r*r+r,r-rwrxryrzr/z9No modifications detected for re-loaded extension module z, skipping build step...zLoading extension module ) rrrrPr~JIT_EXTENSION_VERSIONER get_versionbump_version_if_changedrUrVrWrrGrLru try_acquirerrQrr rxrr rKr r r#_write_ninja_file_and_build_libraryreleasewait_get_exec_path_import_module_from_library)rkrnr)r*r+r,r-rwrxryrzr.r/r& with_cudnn old_versionrbbatonrrrrrrrr>r's          "  r'cCstt}t|| durttt|} | dur ttt|} tj | d}| r4t d|dt j dtj | sN| rGt d| dt j dtj| ddt||||||||| ||dd| | d| rjt d t j dt| | d d dS) N build.ninjaEmitting ninja build file r~rECreating directory TrHrLr rprqrrrsrtrurvrnroldflagslibrary_targetryrzzCompiling objects...z%Error compiling objects for extension error_prefix)r4r6r*rrrPr~rGrLrurUrVrWrQmakedirs_write_ninja_file_run_ninja_build)rnror rprqrrrsrtrurvrwrxryrzrbuild_file_pathrrr>r:sL  rr/c  Cstt} t| | durttt|} | dur ttt|} t|p$g| || }tj |d} |r=t d| dt j dtj |sW|rPt d|dt j dtj|ddt| |||p^g|pag|pdg|pgg|pjg| | | d |r}t d |dt j dt||d |d d dS) Nrrr~rErTr) rLrkrnr)r*r+r,r-ryrzr/zBuilding extension module zError building extension 'rDr)r4r6r*rrrPr~_prepare_ldflagsrGrLrurUrVrWrQr"_write_ninja_file_to_build_libraryr)rkrnr)r*r+r,r-rwrxryrzr/rrrrr>rwsP     rcCs*z tdWdStyYdSw)zxReturn ``True`` if the `ninja `_ build system is available on the system, ``False`` otherwise.zninja --versionFT)rrrrrrrr>r3s  r3cCststddS)zRaise ``RuntimeError`` if `ninja `_ build system is not available on the system, does nothing otherwise.z(Ninja is required to load C++ extensionsN)r3rrrrr>r4sr4cCstrDtjtjd}|d|r|d|d|r'|d|d|d|dt|sC|d |d|n>|d t|d |r\|trYd nd |d|rl|tridnd|d|sx|d|r|dt|r|rt dtj dtr|dt dd|dt dur|dtjt dd|Stsd}tj t |stj t drd}|d t ||dt dur|d tjt d|Str|d td|d|S)Nlibszc10.libz c10_cuda.libz torch_cpu.libztorch_cuda.libz"-INCLUDE:?warp_size@cuda@at@@YAHXZz torch.libz /LIBPATH:ztorch_python.librz-lc10z -lc10_hipz -lc10_cudaz -ltorch_cpuz -ltorch_hipz -ltorch_cudaz-ltorchz-ltorch_pythonz -Wl,-rpath,z%Detected CUDA files, patching ldflagsrErr z cudart.libr!z-lcudartz -lamdhip64)rNrGrLrurVbase_exec_prefixr r"rQrUrWrRrrQrx)r,ryrxr/python_lib_path extra_lib_dirrrr>rsf              rr cCs|dur|D]}d|vr qd|vrgSqtgd}gd}|dd|D}tjdd}|std g}ttj D]4}tj |}d dtj D} t d d | D} t| |}|d d|d} | |vru|| qAt|}|dd7<n|dd}|D] \} } || | }q|d}g}|D]=} | |vrtd| d| dd }|d\}}||}|d|d|| dr|d|d|qtt|S)ad Determine CUDA arch flags to use. For an arch, say "6.1", the added compile flag will be ``-gencode=arch=compute_61,code=sm_61``. For an added "+PTX", an additional ``-gencode=arch=compute_xx,code=compute_xx`` is added. See select_compute_arch.cmake for corresponding named and supported arches when building with CMake. NTORCH_EXTENSION_NAMEarch))z Kepler+Tesla3.7)Keplerz3.5+PTX)z Maxwell+Tegra5.3)Maxwellz 5.0;5.2+PTX)Pascalz 6.0;6.1+PTX)z Volta+Tegra7.2)Voltaz7.0+PTX)Turingz7.5+PTX)z Ampere+Tegra8.7)Amperez 8.0;8.6+PTX)Adaz8.9+PTX)Hopperz9.0+PTX)zBlackwell+Tegra10.1) Blackwellz 10.0;12.0+PTX)z3.5rz5.0z5.2rz6.0z6.1z6.2z7.0rz7.5z8.0z8.6rz8.9z9.0z9.0az10.0z10.0arz10.1az12.0z12.0acSsg|]}|dqS)+PTXrrrrr>r?* z(_get_cuda_arch_flags..TORCH_CUDA_ARCH_LISTzTORCH_CUDA_ARCH_LIST is not set, all archs for visible cards are included for compilation. If this is not desired, please set os.environ['TORCH_CUDA_ARCH_LIST'].c Ss4g|]}d|vrtdtd|ddqS)sm_rz\d+rr)r}rurrrr<rrrr>r?< s css |] }|d|dfVqdS)rNr)r<smrrr>r> sz'_get_cuda_arch_flags..rrrrrr:;zUnknown CUDA arch (z) or GPU not supported+z-gencode=arch=compute_z ,code=sm_z,code=compute_) collections OrderedDictrGrHrIrrrIrRrS device_countget_device_capabilityrmaxminr sortedrirnrrendswithr )r r named_archessupported_archesvalid_arch_strings _arch_listrrL capability supported_smmax_supported_smr named_archarchvalflagsrbrminornumrrr>rDsZ        rDcCs|dur|D]}d|vsd|vrdgSqtjdd}|s.tj}|r+|}n g}n |ddd}dd|D}|dg7}|S) Nz amdgpu-targetz offload-archz -fno-gpu-rdcPYTORCH_ROCM_ARCHr:rcSr)z--offload-arch=rrrrr>r?t rez(_get_rocm_arch_flags..)rGrHrIrRr_cuda_getArchFlagsrri)r r_archs archFlagsarchsrrrr>rWb s    rWrkcCstjd}|dur?t}tjjdurdn dtjjdd}dtj j tj j t tdd}|d|}tj ||}|rLtd |d tjd tj ||}tj |sm|rftd |d tjd tj|dd|S)NTORCH_EXTENSIONS_DIRrcurrpyabiflagsrzUsing z as PyTorch extensions root...rEzCreating extension directory r~Tr)rGrHrIr(rRrbrSrirV version_inforrrrLrurUrWrQr)rkrxroot_extensions_directorycu_strpython_version build_folderrwrrr>r(x s& " r(cCsTtjd}|dur|r|rtd|dtjdt|S|r(tdtjddS)NMAX_JOBSzUsing envvar MAX_JOBS (z) as the number of workers...rEzqAllowing ninja to set a default number of workers... (overridable by setting the environment variable MAX_JOBS=N))rGrHrIisdigitrUrVrWr})rxmax_jobsrrr>_get_num_workers s  rvc_archcCsDz ddlm}|j|WSty!ddlm}||YSw)Nr distutils) _msvccompiler)rrr _get_vc_envAttributeErrorsetuptools._distutils)rrrrrr>r s   rrc Cs@ddg}t|}|dur|dt|gtj}trQd|vrQddlm}|j }t |}ddt | D} | D]\} } | } | | vrN| | | <q>| }z tjtjd } tj||re| ntjtj|d |d WdStjy}z!t\}}}|}t|d r|jr|d |jjt7}t||d}~ww)Nninjarz-jrrrcSsi|] \}}||qSr)upper)r<kr~rrr>ri rz$_run_ninja_build..rT)stdoutrWcwdcheckroutputr)rrFrrGrHrrNrrutil get_platformPLAT_TO_VCVARSrrnrrVrflushrWrrunPIPErrTrrrrrr)rwrxrcommand num_workersrr plat_name plat_specvc_envrr~uk stdout_filenorVrrmessagerrr>r sH          rcCsptr-ttdddvr-tddtdddD}|s-tdtddtjd<tj||t S)NPATHrrcss*|]}tj|otj|tVqdSr|)rGrLrQsamefiler")r<prrr>r s  z!_get_exec_path..) rNr"rGrErrrHrLruEXEC_EXT) module_namerLtorch_lib_in_pathrrr>r srcCsttj||t}|r2tj||}|dusJtj|}t|j tj j s*J|j ||St j||Sr|)rGrLruLIB_EXTrhrspec_from_file_locationmodule_from_specrTloaderabcLoader exec_modulerRops load_library)rrLr.filepathspecmodulerrr>r s    rc s2dd|D}dd|D}dd|D}dd|D}dd|D}dd|D} r1td} ntd } tjd trr? rz6_write_ninja_file_to_build_library..cSrrrrrrr>r? rcSrrrrrrr>r? rcSrrrrrrr>r? rcSrrrrrrr>r? rcSrrrr<rFrrr>r? rlrSrrnt posix_prefix)schemerr-cSrZrrrrrr>r? r[cSrrXrrYrrr>r?" recSg|] }dt|qSrXrcrYrrr>r?$ cSr)z -isystem rcrYrrr>r?% rcSrZrrrrrr>r?' r[z /std:c++17rrz -DWITH_HIPrrrr?r@csr)z-std=Nrrrrr>r@ r z5_write_ninja_file_to_build_library..rArBcSrf)r0rgrhrjrrr>r?N rlr:rr9csZtjtj|d}t|rr|d}|St|r&r&|d}|S|d}|S)Nrz.cuda.oz.sycl.oz.o)rGrLrrarPr~)r file_nametarget)ryrzrr>object_file_pathV s    z<_write_ninja_file_to_build_library..object_file_pathcsg|]}|qSrr)r<rZ)rrr>r?c rz-undefined dynamic_lookupr)r/r\r]rNr r4r6rr@rQrXrVrWrCrDrrrGrErr rurrr SHARED_FLAGrrrr)rLrkrnr)r*r+r,r-ryrzr/ user_includessystem_includespython_include_pathrr  cuda_flagsrrcc_envrtrrvrorr[rr)rryrzr>r s                 rc, Csdd}||}||}||}||}||}||}||}||}|| } t| t| ks2Jt| dks:Jt}dg}|d|| sL|rldtjvrWtd}n tr_tdd}ntdd }|d ||sp|r~t rtd nd }|d |trt |}dd |g}|dd || r|dd ||dd ||dd ||r|dd ||dd ||dd ||dd | dd| D} dg}t r|d|dn|d|d|d| r=d g}d!}t j jd"ur4td#d$d%kr4|d|dd&}|d'|d(|rHd)g}|d*g}t| | D]J\}}t|oY| }t|o`|}|rgd+}n|rmd,}nd-}t r~|d.d/}|d.d/}|dd0}|dd0}|d1|d2|d|qO|rtj tj| dd3}d4g} | d5d1|d6d | g}!| |g7} ngg} }!|rtj tj| dd7}"d8g}#|#d9d1|"d:d | g}$| |"g7} ngg}#}$| d"urJd;g}%t r2td}&t|&d?kr$tj|&dd.d/}'ntd@|%dA|'dBn|%dCd1| dDd | g}(dE| g})nggg}%}(})|||g}*| r_|*||rg|*||*| |#|%||!|$|(|)g7}*dF dGdH|*D}+|+dI7}+t||+d"S)JakWrite a ninja file that does the desired compiling and linking. `path`: Where to write this file `cflags`: list of flags to pass to $cxx. Can be None. `post_cflags`: list of flags to append to the $cxx invocation. Can be None. `cuda_cflags`: list of flags to pass to $nvcc. Can be None. `cuda_post_cflags`: list of flags to append to the $nvcc invocation. Can be None. `cuda_dlink_post_cflags`: list of flags to append to the $nvcc device code link invocation. Can be None. `sycl_cflags`: list of flags to pass to SYCL compiler. Can be None. `sycl_post_cflags`: list of flags to append to the SYCL compiler invocation. Can be None. `sycl_dlink_post_cflags`: list of flags to append to the SYCL compiler device code link invocation. Can be None. e. `sources`: list of paths to source files `objects`: list of desired paths to objects, one per source. `ldflags`: list of flags to pass to linker. Can be None. `library_target`: Name of the output library. Can be None; in that case, we do no linking. `with_cuda`: If we should be compiling with CUDA. cSs|durgSdd|DS)NcSrrrrrrr>r? rz=_write_ninja_file..sanitize_flags..r)rrrr>sanitize_flags sz)_write_ninja_file..sanitize_flagsrzninja_required_version = 1.3zcxx = PYTORCH_NVCCrr^rCznvcc = icxrgzsycl = z cflags = r:zpost_cflags = zcuda_cflags = zcuda_post_cflags = zcuda_dlink_post_cflags = zsycl_cflags = zsycl_post_cflags = zsycl_dlink_post_cflags = z ldflags = cSrrrrrrr>r? rlz%_write_ninja_file..z rule compilez@ command = cl /showIncludes $cflags -c $in /Fo$out $post_cflagsz deps = msvczD command = $cxx -MMD -MF $out.d $cflags -c $in -o $out $post_cflagsz depfile = $out.dz deps = gcczrule cuda_compilerN*TORCH_EXTENSION_SKIP_NVCC_GEN_DEPENDENCIESrrz?--generate-dependencies-with-compile --dependency-output $out.dz command = $nvcc z. $cuda_cflags -c $in -o $out $cuda_post_cflagszrule sycl_compilezF command = $sycl $sycl_cflags -c -x c++ $in -o $out $sycl_post_cflags cuda_compile sycl_compiler:z$:z$ zbuild rzdlink.ozrule cuda_devlinkz5 command = $nvcc $in -o $out $cuda_dlink_post_cflagsz: cuda_devlink z sycl_dlink.ozrule sycl_devlinkz5 command = $sycl $in -o $out $sycl_dlink_post_cflagsz: sycl_devlink z rule linkwhererz rz'MSVC is required to load C++ extensionsz command = "z)/link.exe" $in /nologo $ldflags /out:$outz% command = $cxx $in $ldflags -o $outz: link zdefault z css|]}d|VqdS)rkN)ru)r<brrr>r< r z$_write_ninja_file..rk)rPr6r rGrHrErQrxrRrNrXrurRrbrSziprPr~rirLrMrrrrrrr),rLr rprqrrrsrtrurvrnrorrryrzrrconfigrCr,r compile_rulecuda_compile_rule nvcc_gendepssycl_compile_rulebuildr object_fileis_cuda_sourceis_sycl_sourcerulecuda_devlink_outcuda_devlink_rule cuda_devlinksycl_devlink_outsycl_devlink_rule sycl_devlink link_rulecl_pathscl_pathlinkdefaultblocksrrrr>r s"                            rcGry)z Join paths with CUDA_HOME, or raises an error if it CUDA_HOME is not set. This is basically a lazy way of raising an error for missing $CUDA_HOME only once we need to get any CUDA-specific path. NzSCUDA_HOME environment variable is not set. Please set it to your CUDA install root.)rArtrGrLrurvrrr>rRA srRrLcCs*ddg}tr |dtj|d|vS)Nr)r5r6r)rQr rGrLrrL valid_extrrr>rPN s rPcCsdg}tj|d|vS)Nr*r)rGrLrr?rrr>r~T sr~)r) NNNNNNFNNTFT)F)NNNNNNNNNFNNTTTF)Tr|r)rrOrh importlib.abcrGrrrJrrrVr\rrpathlibrrJrRtorch._appdirs file_batonr_cpp_extension_versionerrr rhipify.hipify_pythonrtypingrr torch.torch_versionr r setuptools.command.build_extr rrNrrrrr CLIB_PREFIXCLIB_EXTrrLrK__file___HERErMrrur"rrrrr} VersionRangerUr VersionMapr#__annotations__MINIMUM_CLANG_VERSIONr'__all__rr@r[rfrsrxr{rrrrrr\r#rbr_rQ ROCM_VERSIONrrS _is_compiledrArHrIrrrzrrrrrCrXrVrrrrrrr6boolrrrr(r)r*rr rr+r,r-r.r/r0r1r4r6r7rer5r2r'rrr3r4rrDrWr(rrrrrrrrRrPr~rrrr>s                      $   ,49 4F@P%1  } y  N   _    I     =  ; c 5    A