Skip to content
项目
群组
代码片段
帮助
当前项目
正在载入...
登录 / 注册
切换导航面板
P
pytensor
项目
项目
详情
活动
周期分析
仓库
仓库
文件
提交
分支
标签
贡献者
图表
比较
统计图
议题
0
议题
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
CI / CD
CI / CD
流水线
作业
日程
统计图
Wiki
Wiki
代码片段
代码片段
成员
成员
折叠边栏
关闭边栏
活动
图像
聊天
创建新问题
作业
提交
问题看板
Open sidebar
testgroup
pytensor
Commits
06471dbf
提交
06471dbf
authored
11月 09, 2011
作者:
nouiz
浏览文件
操作
浏览文件
下载
差异文件
Merge pull request #10 from delallea/nouiz-doc
Clarified when to register a type with OutputGuard
上级
94e3863f
cd5cca74
隐藏空白字符变更
内嵌
并排
正在显示
1 个修改的文件
包含
13 行增加
和
5 行删除
+13
-5
ctype.txt
doc/extending/ctype.txt
+13
-5
没有找到文件。
doc/extending/ctype.txt
浏览文件 @
06471dbf
...
...
@@ -486,12 +486,20 @@ Output Guard
============
We have an internal Op called OutputGuard. It is used for some
verification of inplace/view Ops. It has a C implementation that
increments/decrements Python reference counts. If your type represents a
Python object, OutputGuard C code should work with your type. You must
tell OutputGuard to generate C code when working with your
type, as otherwise it will use Python code. You can achieve this with:
verification of inplace/view Ops. Its C implementation increments and
decrements Python reference counts, and thus only works with Python
objects. If your new type represents Python objects, you should tell
OutputGuard to generate C code when working with this type, as
otherwise it will use Python code instead. This is achieved by
calling:
.. code-block:: python
theano.compile.mode.register_OutputGuard_c_code(YOUR_TYPE_CLASS)
Note that you should not call ``register_OutputGuard_c_code`` with your
new type if this type is not associated to Python objects in the C code,
as otherwise the reference count mechanism will crash. For instance,
the ``Double`` type described here is associated to ``double`` objects
in the C code, and consequently this type should not be registered in
OutputGuard.
编写
预览
Markdown
格式
0%
重试
或
添加新文件
添加附件
取消
您添加了
0
人
到此讨论。请谨慎行事。
请先完成此评论的编辑!
取消
请
注册
或者
登录
后发表评论