Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
openeuler
qemu
提交
f0f26a06
Q
qemu
项目概览
openeuler
/
qemu
通知
10
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
Q
qemu
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
提交
f0f26a06
编写于
5月 10, 2009
作者:
B
Blue Swirl
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Update docs on dynamic condition code calculation
Signed-off-by:
N
Blue Swirl
<
blauwirbel@gmail.com
>
上级
d084469c
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
5 addition
and
3 deletion
+5
-3
qemu-tech.texi
qemu-tech.texi
+5
-3
未找到文件。
qemu-tech.texi
浏览文件 @
f0f26a06
...
...
@@ -363,7 +363,9 @@ look at @code{tcg/README}.
Lazy evaluation of CPU condition codes (@code
{
EFLAGS
}
register on x86)
is important for CPUs where every instruction sets the condition
codes. It tends to be less important on conventional RISC systems
where condition codes are only updated when explicitly requested.
where condition codes are only updated when explicitly requested. On
Sparc64, costly update of both 32 and 64 bit condition codes can be
avoided with lazy evaluation.
Instead of computing the condition codes after each x86 instruction,
QEMU just stores one operand (called @code
{
CC
_
SRC
}
), the result
...
...
@@ -376,8 +378,8 @@ conditional branches.
@code
{
CC
_
OP
}
is almost never explicitly set in the generated code
because it is known at translation time.
The lazy condition code evaluation is used on x86, m68k
and cris. ARM
uses a simplified variant for the N and Z flags.
The lazy condition code evaluation is used on x86, m68k
, cris and
Sparc. ARM
uses a simplified variant for the N and Z flags.
@node CPU state optimisations
@section CPU state optimisations
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录