Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
H
hpvm-release
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
llvm
hpvm-release
Commits
305da94f
Commit
305da94f
authored
3 years ago
by
Yifan Zhao
Browse files
Options
Downloads
Patches
Plain Diff
Fixed some links in documentation
parent
600e53b6
No related branches found
No related tags found
No related merge requests found
Changes
4
Hide whitespace changes
Inline
Side-by-side
Showing
4 changed files
hpvm/docs/getting-started.rst
+4
-4
4 additions, 4 deletions
hpvm/docs/getting-started.rst
hpvm/docs/install.rst
+1
-1
1 addition, 1 deletion
hpvm/docs/install.rst
hpvm/projects/predtuner
+1
-1
1 addition, 1 deletion
hpvm/projects/predtuner
hpvm/test/README.rst
+0
-6
0 additions, 6 deletions
hpvm/test/README.rst
with
6 additions
and
12 deletions
hpvm/docs/getting-started.rst
+
4
−
4
View file @
305da94f
...
...
@@ -63,8 +63,8 @@ Create a DNN `module` and load the checkpoint:
Any `torch.nn.Module` can be similarly used,
as long as they only contain the tensor operators supported in HPVM.
See "Supported Operators" in :doc:`PyTorch frontend <components/torch2hpvm>`
and :doc:`Keras frontend <components/keras-frontend>`.
See "Supported Operators" in :doc:`PyTorch frontend <
/
components/torch2hpvm>`
and :doc:`Keras frontend <
/
components/keras-frontend>`.
Now we are ready to export the model. The main functioning class of `torch2hpvm` is `ModelExporter`:
...
...
@@ -183,7 +183,7 @@ After the tuning finishes, the tuner will
* save the HPVM config format (write-only) at ``./hpvm_confs.txt``.
It is also possible to save the configuration in other formats
(see the :doc:`predtuner documentation <components/predtuner>`).
(see the :doc:`predtuner documentation <
/
components/predtuner>`).
Profiling the Configurations
----------------------------
...
...
@@ -228,4 +228,4 @@ An example of ``configs_profiled.png`` looks like this (proportion of your image
This concludes the whole workflow of HPVM.
For more detailed usages, check out the documentation of each component listed
:doc:`here <components/index>`.
:doc:`here <
/
components/index>`.
This diff is collapsed.
Click to expand it.
hpvm/docs/install.rst
+
1
−
1
View file @
305da94f
...
...
@@ -161,4 +161,4 @@ You can run tests similarly as how ``approxhpvm.py`` is compiled: for example,
make -j<number of threads> check-hpvm-pass
runs ``check-hpvm-pass`` tests. See
TODO
for details on benchmarks and test cases.
runs ``check-hpvm-pass`` tests. See
:doc:`/tests`
for details on benchmarks and test cases.
This diff is collapsed.
Click to expand it.
predtuner
@
a149e365
Compare
aa28a41c
...
a149e365
Subproject commit a
a28a41ca12b15af31e1d15b687367e27cde3878
Subproject commit a
149e365170263666db764664ad8ed6b03f258d3
This diff is collapsed.
Click to expand it.
hpvm/test/README.rst
+
0
−
6
View file @
305da94f
...
...
@@ -120,9 +120,3 @@ Currently, there are 20 of them. These are:
``_cudnn`` suffix indicates the code is generated onto cuDNN functions.
Otherwise they are generated to ``tensor_runtime`` DNN functions which are hand-written in CUDA.
TODO: figure out how to
^^^^^^^^^^^^^^^^^^^^^^^
#. Auto run Keras and PyTorch tests (generating, compiling and running all DNNs)
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment