commit | 23250f59cfc89673b7efe1d8f13192ed8381824d | [log] [tgz] |
---|---|---|
author | Mark Shields <87091372+mbs-octoml@users.noreply.github.com> | Fri Apr 01 11:50:58 2022 -0700 |
committer | GitHub <noreply@github.com> | Fri Apr 01 11:50:58 2022 -0700 |
tree | 679244fb3e35fde4531023f47d25b65e1fdf7ad9 | |
parent | 540c1f80631b5d9ee2ae9ff827edc73240fe1b09 [diff] |
Collage RFC (#62) * Collage RFC * - Add some FAQ entries. Make the partition_for_x preamble issue more explict. * - Clarify pass ordering issue. * - Strawman for moving CollageFuseOps early. * - Switch from 'fusion' to 'partition' focus, matched prototype again. * - Err, three advantages, not four. * - minor clarrification * - some more clarifications based on github comments * - expand on PartitionRule * - Manupa's comments * - Remainder of Manupa's comments (oops) - Add some pictures
An RFC is a “Request for Change” to the TVM project. It is a design document that describes a new feature, enhancement, or process to the TVM project. RFCs should be the primary mechanism for proposing major features and changes. The author of the RFC is responsible for the discussion of the change, and for organizing the work around it. RFCs are text files, stored in the Apache TVM RFC repository, that serve as history and documentation of TVM features.
The primary audience of RFCs is the TVM development community. RFCs serve as a guide for the design and implementation of features during and after their development. A secondary audience is general users and developers who are interested in how and why a feature was designed and implemented.
To work on a major feature within the TVM project, an RFC must first be merged into the TVM RFC repository as a markdown file. Once merged, the RFC is considered to be “active” and may be implemented, with the goal of merging the implementation into the TVM project. These are steps that should be taken in the RFC process:
tvm-rfcs
repository. To allocate a new RFC number, open a PR against tvm-rfcs
(initially, you might need to use a dummy number in the filename for the RFC content; this can be updated after the RFC PR is created).L
to indicate it is a legacy RFC. For example, L0001
.Apache TVM is a compiler stack for deep learning systems. It is designed to close the gap between the productivity-focused deep learning frameworks, and the performance- and efficiency-focused hardware backends. TVM works with deep learning frameworks to provide end to end compilation to different backends.
© Contributors Licensed under an Apache-2.0 license.
TVM adopts Apache committer model. We aim to create an open source project that is maintained and owned by the community. Check out the Contributor Guide.