I use the FORTRAN_WINPRINT.F90 to print from my applications, but the print window (the one that allows you to select your printer) opens almost always behind my applications window. Not every time, but more probably more than 70% of the time. So users think the program has stopped when it is actually waiting for input. How do I get this Print window to always come up in front of my applications window?
I'm new to using the IPP library and I'm having trouble converting from pixel order YCbCr411 data to BGR format. From reading the documentation, I know that I first need to convert the pixel order to planar format first before calling the the library function ippiYCbCr411ToBGR_8u_P3C4R to convert planar YCbCr411 data to BGR format. I see that I can probably use the ippiCopy_8u_C3P3R call to convert my image buffer from pixel order to planar order.
For example, is this the following the correct approach?
Currently, I'm running analysis on the executable file generated from the compilation of C source code.
However, at the Summary window, certain OpenMP regions' CPU Usage Histograms are not displayed at the GUI, and some of them do.
Attached is the screenshot of Summary window. Hope it'll help to clarify my statement above.
Is there any solution to this problem?
My builds previously worked, but after updating with the latest Intel Fortran tools, I no longer have a libmmt.lib and my build has a fatal error:
Error 9 fatal error LNK1104: cannot open file 'libmmt.lib' LINK
My update database shows that libmmt.lib DID previously exist in e.g. Program Files (x86)/Intel/Composer XE 2015/Compiler/lib/intel64
but it is gone after the update. Other tools (Intel Software Manager) seem to be gone, too.
Is this change expected and what can I do about it?
similar to this issue back then with Linux 3.0 https://software.intel.com/en-us/forums/topic/282300 I'm now greeted by the annoying error message that "4.0 is not a supported linux release". The differences to the last 3.x release are not large, so this restriction is rather annoying. Is there a way to bypass it? Or is there a beta release ready to be tested to circumvent this issue? I've tried with the latest VTune Amplifier XE 2015 Update 3 release to no avail.
This is mostly an FYI on a follow up to the locked post: https://software.intel.com/en-us/forums/topic/515943
I had the same x64 debugging problem (watch variables show up with undefined addresses), so I updated to the latest ver of Fortran composer (Intel(R) Visual Fortran Compiler XE 220.127.116.11), which is update 5, but this did not fix the problem (the problem only occurs with VS2013, but not VS2010).
I just got a notice to get the new Intel System Studio Beta. I have to choose between "Windows Host" and "Windows Target." What is the difference?
I have recently run into an internal compiler error with ifort 15.0, for a piece of code that works just fine with Ifort 14.0. I think this is a regression bug.
The catastrophic error shows up when I create a polymorphic pointer to an extended type with a long name, which is defined within a module that also has a long name. I see the error whenever the sum of the two names (module + type) is equal to or larger than 110 characters.
Please consider the following code:
in my company we have some IF Studio 2013 and some IF Composer 2013 installed.
I've updated the Composers XE 2013 to SP1.5.239
Now I'm searching for SP1 Update 5 for the Studio-versions, but in the Intel-download-area I can only find SP1 update 3.
I assume the the Studio-Update is just a bundling of the updates of the tools it consists of.
Question: is it save to update a Studio-installation with the Composer-Update?
Hi. I was wondering if someone can clarify what wait_for_all does, and why it does not behave the way I expected: