Move known_callables from ASTBuilderBase to TargetBase (split into host/device variants)#989
Move known_callables from ASTBuilderBase to TargetBase (split into host/device variants)#989
known_callables from ASTBuilderBase to TargetBase (split into host/device variants)#989Conversation
Co-authored-by: inducer <352067+inducer@users.noreply.github.com>
known_callables from ASTBuilderBase to TargetBase
|
@copilot Note that there should be two versions of |
…ables on TargetBase Co-authored-by: inducer <352067+inducer@users.noreply.github.com>
Done in 91bbd26.
|
known_callables from ASTBuilderBase to TargetBaseknown_callables from ASTBuilderBase to TargetBase (split into host/device variants)
|
@copilot Why does |
Co-authored-by: inducer <352067+inducer@users.noreply.github.com>
|
known_callablesproperty toTargetBasereturning{}ASTBuilderBase.known_callablesto delegate toself.target.known_device_callablesknown_callablesoverride toDummyHostASTBuilderdelegating toself.target.known_host_callablesknown_callablesoverride toPythonASTBuilderBasedelegating toself.target.known_host_callablesCFamilyASTBuilder.known_callables→CFamilyTarget.known_device_callablesCUDACASTBuilder.known_callables→CudaTarget.known_device_callablesOpenCLCASTBuilder.known_callables→OpenCLTarget.known_device_callablesPyOpenCLCASTBuilder.known_callables→PyOpenCLTarget.known_device_callables; addPyOpenCLTarget.known_host_callablesreturning C callables for Python host builderCWithGNULibcASTBuilder.known_callables→CWithGNULibcTarget.known_device_callablesExecutableCWithGNULibcTargetto also overrideknown_device_callableswith GNU libc callables (fixestest_glibc_bessel_functions)translation_unit.pyto uset_unit.target.known_device_callablestools.pyto useself.target.known_device_callableslibrary/reduction.pyto usetarget.known_device_callables["max/min"]Original prompt
known_callablesintoTargetBase, fromASTBuilder#988✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.