Buscar

Buscar resultados para:

Resultados de la búsqueda: 349

  1. runtime array bounds checking on allocated arrays

    https://software.intel.com/es-es/forums/intel-visual-fortran-compiler-for-windows/topic/337663

    ... code to the following program and got the same unwanted behaviour. With compiler flag set to check bounds I got no runtime error where one should be:

  2. array boundary check in ifort

    https://software.intel.com/es-es/forums/intel-fortran-compiler-for-linux-and-mac-os-x/topic/271337

    10 May 2012 ... Or, the programmer has to check manually. Thanks! ... All rights reserved.xwu@ xth3:~/tempcode> ifort -check bounds -O0 ex.f90 && ./a.out 10.1 ...

  3. ifort compilation error- failes to recognize MKL Lapack function ...

    https://software.intel.com/es-es/forums/intel-math-kernel-library/topic/520125

    8 Ago 2014 ... ifort -openmp -O0 -g -check bounds -traceback -heap-arrays -c /homes/srihari/ atomion/1Dho/source/Libs/mothpl.f90 ifort -openmp -O0 -g -check ...

  4. Array bound exceeded using higher compilers

    https://software.intel.com/es-es/forums/intel-c-compiler/topic/310859

    It's very hard to fix the array bounds exceeded errors. ... Note that array bound check is carried out only with the debug version of the program not the release ...

  5. Run-time error (Array bounds exceeded) with Compaq Visual Fortran

    https://software.intel.com/es-es/forums/intel-visual-fortran-compiler-for-windows/topic/272902

    3 Jul 2002 ... Sounds like one compiler is checking array bounds for you (with CVF ... error and prevent this from happening, or just do a /check:nobounds in ...

  6. Intel Fortran 15 compiler error -- pointer becomes unassociated ...

    https://software.intel.com/es-es/forums/intel-fortran-compiler-for-linux-and-mac-os-x/topic/585242

    21 Ago 2015 ... ... causes a pointer to become disassociated where it should not be. This error happens when compiling with --check bounds -O2, and -openmp.

  7. Always recompiling

    https://software.intel.com/es-es/forums/intel-visual-fortran-compiler-for-windows/topic/271560

    /QxW /fpp /define:IFORTWIN32 /free /fpconstant /iface:cvf /module:"Debug/" / object:"Debug/" /asmattr:source /asmfile:"Debug/" /traceback /check:bounds ...

  8. MPI_Allgatherv with large message sizes

    https://software.intel.com/es-es/forums/intel-clusters-and-hpc-technology/topic/505683

    20 Feb 2014 ... mpiifort -warn -O1 -g -traceback -check bounds -ilp64 gather.o -o gather.exe- ilp64. mpirun -ilp64 ./gather.exe-ilp64. I aborts with: Assertion ...

  9. inconsistent ACCESS VIOLATION

    https://software.intel.com/es-es/forums/intel-visual-fortran-compiler-for-windows/topic/401584

    I ran the code with bounds checking turned on (for this part I ran it with only this option in release mode because the code takes days to weeks to run normally ...

  10. Check of number of parameters

    https://software.intel.com/es-es/forums/intel-visual-fortran-compiler-for-windows/topic/299831

    One thing I miss in IVF is the automatic check of the numbers of parameters when calling ... /check:bounds /check:uninit /check:format /check:output_conversion

  11. run time error 157 in CVF

    https://software.intel.com/es-es/forums/intel-visual-fortran-compiler-for-windows/topic/273021

    I built the executable (TEST.exe) with check:all option (this include checking bounds). I have not been able to execute the program successfully so far.

  12. forrtl: severe (157): Program Exception - access violation

    https://software.intel.com/es-es/forums/intel-visual-fortran-compiler-for-windows/topic/301074

    Aug 14, 2008 ... If I remove /check:bounds then the code gets farther, then runs into the 157 ... if / check:bounds is used, and gives the 157 error if it is not used.

  13. PRJ0019

    https://software.intel.com/es-es/forums/intel-visual-fortran-compiler-for-windows/topic/288073

    ifort /nologo /debug:full /Od /gen-interfaces /warn:interfaces /module:"Debug\" / object:"Debug\" /traceback /check:bounds /libs:static /threads /dbglibs /c /Qvc9 ...

  14. Parameterized derived type with type-bound procedure: unexpected ...

    https://software.intel.com/es-es/forums/intel-visual-fortran-compiler-for-windows/topic/542381

    1 Mar 2015 ... Parameterized derived type with type-bound procedure: unexpected .... From what I can see, it's only the bounds checking error that is the ...

  15. Assumed shape arrays in the hierarchy (.hie) file of a COM DLL

    https://software.intel.com/es-es/forums/intel-visual-fortran-compiler-for-windows/topic/298384

    I had the switch "/check:bounds" added to my "Additional Options" in the Configuration ... Well, if you turn off bounds checking, then you get no bounds checking!

  16. skipping incompatible /usr/lib64/*

    https://software.intel.com/es-es/forums/intel-fortran-compiler-for-linux-and-mac-os-x/topic/385383

    5 Abr 2013 ... ifort -O0 -g -debug-parameters -auto -ansi_alias- -pad_source -warn -traceback - fltconsistency -fpconstant -nogen-interfaces -check bounds ...

  17. Debugging - "breakpoint will currently not be hit. invalid file line"

    https://software.intel.com/es-es/forums/intel-visual-fortran-compiler-for-windows/topic/294709

    ifort /nologo /debug:full /Od /gen-interfaces /warn:interfaces /module:"Debug" / object:"Debug" /traceback /check:bounds /libs:static /threads /dbglibs /c /Qvc8 ...

  18. 9.1.024 compile time

    https://software.intel.com/es-es/forums/intel-visual-fortran-compiler-for-windows/topic/275509

    11 May 2006 ... I use /check:uninit and /check:bounds compiler options. In previous versions (9.0. 029?) the default optimization would be /Od (no optimaiztion), ...

  19. idb cannot find function defined by preprocessor directive

    https://software.intel.com/es-es/forums/intel-fortran-compiler-for-linux-and-mac-os-x/topic/271199

    ifort -g -O0 -check bounds -warn all -traceback -align all -align rec8byte -o a.o -c a.f90 -I ifort -g -O0 -check bounds -warn all -traceback -align all -align rec8byte ...

  20. recursive subroutines and significant slow down

    https://software.intel.com/es-es/forums/intel-visual-fortran-compiler-for-windows/topic/534287

    check:all may incur more overhead than check bounds, which already is costly. ... Under Windows it does a lot of checking on allocations and deallocations.

Para obtener información más completa sobre las optimizaciones del compilador, consulte nuestro Aviso de optimización.