《不语者》(Unspoken* ) 是一款由 Insomniac Games* 公司开发的第一人称魔咒虚拟现实游戏,采用了 Oculus Touch* 控制器。 Insomniac Games 是一家经验丰富的家用游戏机开发公司,他们的内部引擎经过扩展后可以支持虚拟现实。 从帧速率为 30 fps 的家用游戏机,到高端虚拟现实设备上的 90 fps,帧速率的大幅提升要求更好的性能感知设计,以及引擎性能改善,以实现最大程度地利用系统资源。 本文介绍了如何检测系统级别的引擎中所存在的技术瓶颈,其背后的原因是什么?以及如何消除这些瓶颈以提升性能。
Authored by Raja B. (Intel) Last updated on 03/29/2017 - 23:59
Forum topic

Issues running DAAL example on Linux

Hello everyone,

Authored by Daniel W. Last updated on 03/29/2017 - 23:43
Forum topic

Compiling with O3 giving segmentation fault

I am getting a segmentation fault while executing a MPI+OpneMP program compiled with O3 flag. Sample program structure is given below

int main()


//MPI init

Authored by Ashutosh L. Last updated on 03/29/2017 - 23:38
Responsive Landing Page

主板比较 | 物联网

Authored by Horta, Areli Last updated on 03/29/2017 - 23:20
Forum topic

Intel C++ compiler for academic non-commercial use


Authored by José Luis G. Last updated on 03/29/2017 - 23:10
Forum topic

Calling convention (codegen) bug when returning packed struct

There seems to be a bug related to a wrong assumption of calling convention of a function returning a packed struct. The generated function's code writes the full 5-byte struct to the RAX register but the calling code tries to pass a return address through the RCX register and then reads from the passed address on the stack (while overwriting the real result in RAX). When the returned struct...

Authored by Andrey Glebov Last updated on 03/29/2017 - 23:08
Forum topic

Issue with O2/O3 optimisation using Intel compiler 2017 update 2


Authored by Arthur P. Last updated on 03/29/2017 - 23:07
Forum topic

internal error: 010101_14277


Attached is a (preprocessed) source file that triggers the error.

Authored by Matthias H. Last updated on 03/29/2017 - 23:06
Forum topic

omp_get_num_procs() doesn't returns all processor

Hi, I have an application in c++ that is using Qt libraries.

Authored by Leonardo H. Last updated on 03/29/2017 - 22:58
For more complete information about compiler optimizations, see our Optimization Notice.