Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Comunicados
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29283 Discussões

problems with parameters on ifort 11.1.059??

clabra
Novo colaborador I
718 Visualizações
Hi,

Yesterday I updated my version of the compiler, and I found a compilation problem of a code who run perfectly with the previous compiler version (11.1.056 intel64).

The error is:

test_materials.F90(186): error #7129: The case-value is out-of-range. [1]
case (curve_constant_type)
----------^
test_materials.F90(188): error #7129: The case-value is out-of-range. [2]
case (curve_linear_type)
----------^
test_materials.F90(190): error #7129: The case-value is out-of-range. [3]
case (curve_quadratic_type)
----------^
test_materials.F90(192): error #7129: The case-value is out-of-range. [4]
case (curve_segments_type)
----------^
test_materials.F90(208): error #7129: The case-value is out-of-range. [1]
case (curve_constant_type)
----------^
test_materials.F90(210): error #7129: The case-value is out-of-range. [2]
case (curve_linear_type)
----------^
test_materials.F90(212): error #7129: The case-value is out-of-range. [3]
case (curve_quadratic_type)
----------^
test_materials.F90(214): error #7129: The case-value is out-of-range. [4]
case (curve_segments_type)

where cure_*_type are parameters.
The code is attached.
I understand that the code it is ok, but if someone can make some comments about the problem or a possible error on the code...

thaks
0 Kudos
6 Respostas
Steven_L_Intel1
Funcionário
718 Visualizações
Thanks - we'll take a look.
Steven_L_Intel1
Funcionário
718 Visualizações
I have not yet been able to reproduce this. Would you please show me the exact compile command you used, as well as adding the -V switch and showing the compiler output?
clabra
Novo colaborador I
718 Visualizações
I have not yet been able to reproduce this. Would you please show me the exact compile command you used, as well as adding the -V switch and showing the compiler output?

Hi Steve,
The command is:

clabra@:function_pointers$ ifort -g -o test.exe -V test_materials.F90
Intel Fortran Intel 64 Compiler Professional for applications running on Intel 64, Version 11.1 Build 20091012 Package ID: l_cprof_p_11.1.059
Copyright (C) 1985-2009 Intel Corporation. All rights reserved.
FOR NON-COMMERCIAL USE ONLY

Intel Fortran 11.1-2620
test_materials.F90(186): error #7129: The case-value is out-of-range. [1]
case (curve_constant_type)
----------^
test_materials.F90(188): error #7129: The case-value is out-of-range. [2]
case (curve_linear_type)
----------^
test_materials.F90(190): error #7129: The case-value is out-of-range. [3]
case (curve_quadratic_type)
----------^
test_materials.F90(192): error #7129: The case-value is out-of-range. [4]
case (curve_segments_type)
----------^
test_materials.F90(208): error #7129: The case-value is out-of-range. [1]
case (curve_constant_type)
----------^
test_materials.F90(210): error #7129: The case-value is out-of-range. [2]
case (curve_linear_type)
----------^
test_materials.F90(212): error #7129: The case-value is out-of-range. [3]
case (curve_quadratic_type)
----------^
test_materials.F90(214): error #7129: The case-value is out-of-range. [4]
case (curve_segments_type)
----------^
compilation aborted for test_materials.F90 (code 1)

and the OS is ubuntu 9.04:

clabra@:function_pointers$ uname -a
Linux xxxx 2.6.27-15-generic #1 SMP Tue Oct 20 06:50:36 UTC 2009 x86_64 GNU/Linux

It is very strange. I hope you can reproduce the error.

Steven_L_Intel1
Funcionário
718 Visualizações
Thanks - I can reproduce it now. I have escalated this as issue DPD200141699. For now, I'll suggest that you stick with 11.1.056. We apologize for the inconvenience.
Steven_L_Intel1
Funcionário
718 Visualizações
This problem has been fixed in our sources. I expect the fix to be included in Update 5, scheduled for late January.
Steven_L_Intel1
Funcionário
718 Visualizações
This was fixed in Update 5.
Responder