Linux*

What collateral/documentation do you want to see?

Do you have questions that you are not finding the answers for in our documentation?  Need more training, source code examples, on what specifically?   Help us understand what's missing so that we can make sure we develop documentation you care about (what is important, and what is nice to have)!   Thank you

FAQS: Compilers, Libraries, Performance, Profiling and Optimization.

In the period prior to the launch of Intel® Xeon Phi™ coprocessor, Intel collected questions from developers who had been involved in pilot testing. This document contains some of the most common questions asked. Additional information and Best-Known-Methods for the Intel Xeon Phi coprocessor can be found here.

The Intel® Compiler reference guides can be found at:

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

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

Feature request: Compiler Version Notes

ifort currently generates comment sections in compiler-generated assembler files (built with "-s") that contain a lot of useful information, such as the compiler version and flags used when compiling; however, since these are comments, they do not find their way into the compiled object files.  Would it be possible to have the compiler mimic gcc's behavior and put this information instead in a ".note" section?  GCC uses ".note.GNU-stack" and places just the compiler version, which alone would be nice, but if there are no restrictions on data length, the compile flags would be nice too.  Or

Cycling block-do-construct with inner block-construct

Hi, I'm wondering if there exists a way (other than branching) for exiting or cycling within a inner block in a do block:

...
do i=1,10
    block
        integer :: k
        ...
        if (...) then
            ...
            cycle !not possible
        end if
        ...
    end block
end do

More general, the question is, if its possible to terminate the execution of a block-construct without using IF/GOTO? I've looked into the standard but I've found no other possibilities...

Suscribirse a Linux*