Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
int
Rust
提交
9ca57868
R
Rust
项目概览
int
/
Rust
大约 1 年 前同步成功
通知
1
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
DevOps
流水线
流水线任务
计划
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
R
Rust
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
DevOps
DevOps
流水线
流水线任务
计划
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
流水线任务
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
9ca57868
编写于
9月 12, 2016
作者:
N
Niko Matsakis
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
check stack discipline of tasks
上级
c2ffa2f9
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
20 addition
and
8 deletion
+20
-8
src/librustc/dep_graph/shadow.rs
src/librustc/dep_graph/shadow.rs
+20
-8
未找到文件。
src/librustc/dep_graph/shadow.rs
浏览文件 @
9ca57868
...
...
@@ -17,8 +17,10 @@
//! runtime impact. Therefore, it is largely compiled out if
//! debug-assertions are not enabled.
//!
//! The basic sanity check, always enabled, is that there is always a
//! task (or ignore) on the stack when you do read/write.
//! The basic sanity check, enabled if you have debug assertions
//! enabled, is that there is always a task (or ignore) on the stack
//! when you do read/write, and that the tasks are pushed/popped
//! according to a proper stack discipline.
//!
//! Optionally, if you specify RUST_FORBID_DEP_GRAPH_EDGE, you can
//! specify an edge filter to be applied to each edge as it is
...
...
@@ -81,13 +83,23 @@ pub fn enqueue(&self, message: &DepMessage) {
DepMessage
::
Write
(
ref
n
)
=>
self
.check_edge
(
top
(
&
stack
),
Some
(
Some
(
n
))),
DepMessage
::
PushTask
(
ref
n
)
=>
stack
.push
(
Some
(
n
.clone
())),
DepMessage
::
PushIgnore
=>
stack
.push
(
None
),
DepMessage
::
PopTask
(
_
)
|
DepMessage
::
PopTask
(
ref
n
)
=>
{
match
stack
.pop
()
{
Some
(
Some
(
m
))
=>
{
if
*
n
!=
m
{
bug!
(
"stack mismatch: found {:?} expected {:?}"
,
m
,
n
)
}
}
Some
(
None
)
=>
bug!
(
"stack mismatch: found Ignore expected {:?}"
,
n
),
None
=>
bug!
(
"stack mismatch: found empty stack, expected {:?}"
,
n
),
}
}
DepMessage
::
PopIgnore
=>
{
// we could easily check that the stack is
// well-formed here, but since we use closures and
// RAII accessors, this bug basically never
// happens, so it seems not worth the overhead
stack
.pop
();
match
stack
.pop
()
{
Some
(
Some
(
m
))
=>
bug!
(
"stack mismatch: found {:?} expected ignore"
,
m
),
Some
(
None
)
=>
(),
None
=>
bug!
(
"stack mismatch: found empty stack, expected ignore"
),
}
}
DepMessage
::
Query
=>
(),
}
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录