Search

Search Results for:

Search Results: 119

  1. Search | Intel® Software

    https://software.intel.com/en-us/search/gss/intel%20fortran%20compiler%20character%20comparison%20bug

    There is an insidious optimizer bug in Intel Fortran compilers, version 8 and ... DPD200141539, C, slower performance comparing to Microsoft Visual Studio 2008*. ... The array BUFFER stores first all of the character strings (4 bytes, * of them, .

  2. Intel® Composer XE 2013 Compilers Fixes List | Intel® Software

    https://software.intel.com/en-us/articles/intel-composer-xe-2013-compilers-fixes-list

    Jul 24, 2012 ... DPD200241351, Fortran, Internal Compiler Error for nested openmp loop .... DPD200238626, C++, A possible bug in __intel_sse2_strspn ... DPD200240638, Fortran, getenv returns string terminated incorrectly, causes user ...

  3. get different result from intel fortran compiler and pgi fortran compiler

    https://software.intel.com/pt-br/search/gss/intel%20fortran%20compiler%20character%20comparison%20bug

    bug or not in fortran compiler under linux 64 bits - Intel® Developer . ... Are you able to compare the signon string above with the one that you .

  4. Buscar | Zona para desarrolladores Intel®

    https://software.intel.com/es-es/search/gss/intel%20fortran%20compiler%20character%20comparison%20bug

    There is an insidious optimizer bug in Intel Fortran compilers, version 8 and later, ... Are you able to compare the signon string above with the one that you .

  5. NaN with -O2 and above, expected results with -O1 and below

    https://software.intel.com/en-us/forums/intel-fortran-compiler-for-linux-and-mac-os-x/topic/405706

    Aug 8, 2013 ... However, when I compile my code with -O2 and above something ... and will evaluate to this, otherwise it will evalute to the empty string. ... and higher is a compiler bug, because this behavior is associated with a "new" language feature. .... This error occurs on all versions of ifort that I have tested on Linux ...

  6. Serious optimizer bug in current Intel Fortran compilers

    https://software.intel.com/en-us/forums/intel-fortran-compiler-for-linux-and-mac-os-x/topic/270147

    Apr 16, 2010 ... There is an insidious optimizer bug in Intel Fortran compilers, version 8 and later, including the current ones. The bug is sensitive in that moving ...

  7. Case-sensitivity in the Fortran compiler

    https://software.intel.com/en-us/forums/intel-visual-fortran-compiler-for-windows/topic/285064

    Feb 22, 2011 ... I have just installed Intel Visual Fortran Composer XE 2011 and ... So, is there any way to toggle the case sensitivity on/off in the Intel Fortran Compiler? ... the BIND(C,NAME="string") attribute, is the preferred choice for this. ... We have had bugs in the Win32 API modules and we fix them when we can.

  8. Debugger problem with assumed-length CHARACTER dummy ...

    https://software.intel.com/en-us/forums/intel-visual-fortran-compiler-for-windows/topic/535663

    Nov 17, 2014 ... I'm using Intel Fortran Compiler 15, Update 1. ... you now acknowledge as a bug and you can follow up on that with the development team? ... I tried both variants where all foo routines used the symbol String and where each ...

  9. Intel Compiler version numbers to Intel Parallel Studio XE ...

    https://software.intel.com/en-us/articles/intel-compiler-and-composer-update-version-numbers-to-compiler-version-number-mapping

    May 5, 2014 ... Maps Intel Compiler Update Versions to their official version numbers. ... removed from downloads due to bug - upgrade U4 or greater. 13.1.1.163 ... Intel Compiler Professional Editions / Intel Visual Fortran editions mappings ...

  10. Intel® Parallel Studio XE 2016 Composer Edition Compilers Fixes List

    https://software.intel.com/en-us/articles/intel-parallel-studio-xe-2016-composer-edition-compilers-fixes-list

    Aug 21, 2015 ... DPD200377478, Fortran, ifort 16.0 : Vectorizer : Internal Compiler Error with O2 on .... DPD200574412, Fortran, String evaluation shows garbled value ... DPD200365974, C++, constexpr bug with std::is_same array to pointer ..... DPD200359245, C++, Comparing pointer-to-member functions to the same ...

  11. Intel® Parallel Studio XE 2015 Composer Edition Compilers Fixes List

    https://software.intel.com/en-us/articles/intel-composer-xe-2015-compilers-fixes-list

    Aug 8, 2014 ... DPD200371086, Fortran, ifort 15.0/16.0 Internal Compiler Error .... DPD200368969, C++, Compiler bug when using C++11 inherited constructors ... DPD200249634, C, UTF-8 raw string literals gives incorrect result on Windows ..... DPD200141539, C, slower performance comparing to Microsoft Visual ...

  12. Consistency of Floating-Point Results using the Intel® Compiler ...

    https://software.intel.com/en-us/articles/consistency-of-floating-point-results-using-the-intel-compiler

    Aug 2, 2012 ... See here for a comparison to Intel® MIC Architecture. ... Intel(R) Fortran Compiler Integration for Microsoft Visual Studio 2005, 10.1.3885.2005 .... Some applications may allocate a variable length string containing the directory ...

  13. Converting c-string to Fortran string

    https://software.intel.com/en-us/forums/intel-visual-fortran-compiler-for-windows/topic/392505

    May 13, 2013 ... So to use them in a Fortran program and array of characters has to be ... The code I posted has nothing to do with avoiding compiler bugs and ... Perhaps there is an Intel intrinsic that does the job, something like QQCTOFSTR.

  14. String Comparisons

    https://software.intel.com/en-us/forums/intel-visual-fortran-compiler-for-windows/topic/275823

    Aug 15, 2006 ... When comparing two character strings of different lengths with ... does the Fortran standardcall for comparing the the shorter string as if it were ... For more complete information about compiler optimizations, see our Optimization Notice. ... (which in Intel Fortran is the one used for kind "default character".

  15. Compilation error #6866: Dotted string is neither a defined operator ...

    https://software.intel.com/en-us/forums/intel-fortran-compiler-for-linux-and-mac-os-x/topic/607373

    Jan 24, 2016 ... First off, my compiler and some platform details: view sourceprint? 1, $ ifort -- version. 2, ifort (IFORT) 16.0.1 20151021 ... Compare .... Obviously I would still like the compiler bug to be fixed, but thanks to FortranFan for the ...

  16. Intel® Professional Edition Compilers 11.1 Fixes List | Intel® Software

    https://software.intel.com/en-us/articles/intel-professional-edition-compilers-111-fixes-list

    Aug 2, 2012 ... DPD200153347, Fortran, Compiler optimization bug on nested if ... DPD200008231, Fortran, IA64 -O3 cause slowdown when comparing serial run to ...... DPD200137735, C++, C, String layout on Mac OS X* Leopard/Snow ...

  17. How about a warning??

    https://software.intel.com/en-us/forums/intel-visual-fortran-compiler-for-windows/topic/402433

    Jul 24, 2013 ... I still don't see an example of a "bug" that Intel Fortran failed to warn you about. .... Of necessity, these articles that undertake a comparison of two ... char*, strcmp and other C style constructs instead of std::string and the STL? ... No word from your compiler, a warning from gfortran thanks to -Wuninitialized.

  18. index() broken in ifort 8.0

    https://software.intel.com/en-us/forums/intel-fortran-compiler-for-linux-and-mac-os-x/topic/267606

    Dec 16, 2003 ... By comparison, this code on DEC/Compaq/HP Fortran gives 0 and 13 which seems correct. ... Don't know why, but maybe this can help you track down the bug. ... with the Windows and linux compilers, with no change in decoration, with ... less performance, as the string comparison is not expanded in line.

  19. Fortran Compiler Options ifort(1)

    https://software.intel.com/sites/default/files/m/f/8/5/8/0/6366-ifort.txt

    DESCRIPTION The ifort command invokes the Intel(R) Fortran Compiler that is .... -assume writeable-strings Tells the compiler to put character constants into ..... Unfortunately, the overflow point can be far away from the point of the actual bug.

For more complete information about compiler optimizations, see our Optimization Notice.