提交 d159fec3 authored 作者: Ian Goodfellow's avatar Ian Goodfellow

fixed doc changes following James' github comments

上级 c91ff192
......@@ -142,15 +142,11 @@ def function(inputs, outputs=None, mode=None, updates=None, givens=None,
The linker uses a python loop to execute the code associated
with all the Apply nodes in the graph in the correct order.
the cvm is a linker that replaces this python loop with a c
loop to avoid continuously changing between python and c.
(It's
currently
a matter of disagreement as to whether there is a cost of
changing
between
python and C, or whether the cvm is faster only because C code is
faster
than python code)
loop to avoid continuously changing between python and c.
(It's currently a matter of disagreement as to whether there
is a cost of changing between
python and C, or whether the cvm is faster only because C code
is faster than python code)
the vm is a linker that was developed to prototype the cvm. it
was easier to develop the vm in python then translate it to c instead
of just writing it in c from scratch
......
......@@ -33,17 +33,11 @@ class VM(object):
The Stack should be considered the reference VM/Linker implementation.
It can correctly evaluate all graphs and is the easiest to read. The CVM
is a port of Stack, and should have the same behavior, but run faster.
Its code is harder to read though.
The CVM's code is harder to read though.
The other python VMs are maybe not necessary anymore, and don't take
advantage of lazy computation, though they still produce the correct
output for lazy nodes It can correctly evaluate all graphs and is the easiest to read. The CVM
is a port of Stack, and should have the same behavior, but run faster.
Its code is harder to read though.
The other python VMs are maybe not necessary anymore, and don't take
advantage of lazy computation, though they still produce the correct
output for lazy nodes.
output for lazy nodes.
Attributes:
......
Markdown 格式
0%
您添加了 0 到此讨论。请谨慎行事。
请先完成此评论的编辑!
注册 或者 后发表评论