[Bug fortran/31269] short-circuit in -fbounds-check

2007-03-20 Thread mimo2 at free dot fr
--- Comment #11 from mimo2 at free dot fr 2007-03-20 20:12 --- hi tobi, may-be they have strong arguments as you say, but I've not catched them. And I still believe that if there is an ambiguity in the standard, the solution is to have a -fshort-circuit to let the user decide wh

[Bug fortran/31269] short-circuit in -fbounds-check

2007-03-20 Thread mimo2 at free dot fr
--- Comment #8 from mimo2 at free dot fr 2007-03-20 18:52 --- Why do you say the code is undefined. The last version (comment #5) is totally valid, but possible side effects in the function k could lead to different results depending on the fact that the -fbounds-check is set or no

[Bug fortran/31269] short-circuit in -fbounds-check

2007-03-20 Thread mimo2 at free dot fr
--- Comment #5 from mimo2 at free dot fr 2007-03-20 08:56 --- OK but in the present situation, the execution could be different wether you have -fbounds-check or not. Let's change the code by program toto implicit none real:: a(100) integer :: i, k a(:) = 1. do i=1,100

[Bug fortran/31269] New: short-circuit in -fbounds-check

2007-03-19 Thread mimo2 at free dot fr
t: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: mimo2 at free dot fr http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31269

[Bug fortran/23091] ICE in gfc_trans_auto_array_allocation

2006-01-05 Thread mimo2 at free dot fr
--- Comment #6 from mimo2 at free dot fr 2006-01-05 13:41 --- same (?) bug on GNU Fortran 95 (GCC) 4.2.0 20060104 program test call toto(4) end subroutine toto(n) integer, intent(in) :: n real :: tab(n) tab(1:n) = 4. end this code compiles when no option, but fails when -fno

[Bug fortran/18379] New: gfortran : array assignation gives internal compiler error

2004-11-08 Thread mimo2 at free dot fr
: unknown Status: UNCONFIRMED Severity: normal Priority: P2 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: mimo2 at free dot fr CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla

[Bug libfortran/18297] gfortran : file opening fails if only read access

2004-11-05 Thread mimo2 at free dot fr
--- Additional Comments From mimo2 at free dot fr 2004-11-05 17:51 --- I forgot to reopen the bug after my last comment. -- What|Removed |Added Status|RESOLVED

[Bug libfortran/18297] gfortran : file opening fails if only read access

2004-11-05 Thread mimo2 at free dot fr
--- Additional Comments From mimo2 at free dot fr 2004-11-05 09:15 --- I don't know what is the "true" fortran convention, but this code program test open(unit=10,file='test.txt',status='old') write(*,*) ' file is read

[Bug fortran/18297] New: gfortran : file opening fails if only read access

2004-11-04 Thread mimo2 at free dot fr
: gfortran : file opening fails if only read access Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P2 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: mimo2 at f

[Bug fortran/17708] New: gfortran problem with goto inside loop

2004-09-28 Thread mimo2 at free dot fr
op Product: gcc Version: unknown Status: UNCONFIRMED Severity: critical Priority: P2 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: mimo2 at free dot fr CC: gcc-bugs at gcc