Intel® C++ Composer XE

Оптимизировали, оптимизировали, да не выоптимизировали!

Оптимизация? Конечно, каждый сталкивался с данной задачей при разработке своих, сколь-нибудь значительных, требующих определённых вычислений, приложений. При этом способов оптимизировать код существует огромное множество, и, как следствие, различных путей сделать это в автоматическом режиме с помощью опций компилятора. Вот здесь и возникает проблема – как выбрать то, что нужно нам и не запутаться?

Problem in Cilkview and Cilkscreen 4225


I am new in Cilk plus. I am facing problem in Cilkview and Cilkscreen 4225. Please help/ guide me ...

I am working on Ubuntu 14.04 LTS with GCC 4.9.2. I install Intel Cilk Plus SDK by synaptic manager.

=> libcilkrts5, libcilkrts5-dbg, libx32cilkrts5, libx32cilkrts5-dbg

I wrote the following code


#include <iostream>
#include <cilk/cilk.h>

using namespace std;

How is the user worker thread returned when returning from cilk runtime?


In the Binary Interface Specification, it says when the last user thread calls __cilkrts_leave_frame() with a __cilkrts_stack_frame which has CILK_FRAME_LAST set in the flags field, the runtime will suspend all of the worker threads it created."

I have a question about when the stack frame set as CILK_FRAME_LAST gets stolen by the system worker.

gcc 5.1 -mfpmath=387 Floating point exception

It appears that the compiler option -mfpmath=387 immediately causes floating point exceptions on Intel architecture processors in cilk_spawn routines compiled with gcc-5.1 cilk.  This seems to be a regression as gcc-4.9 with the cilk patches works fine.  Note that -mfpmath=sse works on 64-bit machines, however, this option is not available for 32-bit Intel machines.  As far as I can tell, most floating point code is affected.  Does anyone know of patches or workarounds for this, especially as this appears to be a show-stopper on 32-bit Intel.

Suscribirse a Intel® C++ Composer XE