[TIR] Merged kDeviceThreadAxis and kUseDynamicSharedMemoryTag #14495
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously,
kDeviceThreadAxisdefined the IterVar to be used for each thread/block axis, andkUseDynamicSharedMemoryTagdefined whether dynamic memory allocations exist, which are primarily used to produce a list of strings bytvm::codegen::ExtractFuncInfo. BecausekDeviceThreadAxisis aArray<IterVar>, the IterVar is used prior to its definition site attir::attr::thread_extent, which results in errors when attempting to round-trip through TVMScript.This commit replaces these attributes with
attr::kKernelLaunchParams, which directly contains the kernel launch parameters. These are expressed as anArray<String>, allowing the generated TVMScript to successfully round-trip.This is part of changes described in #14486, to improve round-trip TVMScript failures that occur in lowering.