[Bug fortran/54405] New: bad debugging info which lead to a wrong behavior of reverse-next in gdb

2012-08-29 Thread Edouard.Canot at irisa dot fr
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54405

 Bug #: 54405
   Summary: bad debugging info which lead to a wrong behavior of
reverse-next in gdb
Classification: Unclassified
   Product: gcc
   Version: 4.6.3
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: fortran
AssignedTo: unassig...@gcc.gnu.org
ReportedBy: edouard.ca...@irisa.fr


Created attachment 28098
  -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=28098
short fortran source file used in the example

Reverse debugging works badly with the attached fortran source file, at least
when using GCC 4.6.3 and GCC 4.7.1.

More precisely, during debugging, the first use of the 'reverse-next' command
(after using record, of course), makes the debugger jump back the first line
where the 'record' command was applied; for example:

===

(gdb) break MAIN__
Breakpoint 1 at 0x402f87: file essai_1.f90, line 3.
(gdb) run
Starting program: .../essai_1 

Breakpoint 1, essai_1 () at essai_1.f90:3
3   x = 1.0
(gdb) record
(gdb) n
4   print *, x = , x
(gdb) n
 x =1.
6   x = 2.5
(gdb) n
7   print *, x = , x
(gdb) n
 x =2.5000
9   x = 3.14159265
(gdb) n
10   print *, x = , x
(gdb) n
 x =3.14159274
12end program
(gdb) reverse-next
4   print *, x = , x

==

The behavior is correct with GCC 4.5.4, so I think it is a regression problem.

The problem has been detected with gdb-7.4 and gdb-7.5.


[Bug fortran/52788] New: -fbounds-check fails for 2-rank allocatable arrays when reading

2012-03-30 Thread Edouard.Canot at irisa dot fr
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52788

 Bug #: 52788
   Summary: -fbounds-check fails for 2-rank allocatable arrays
when reading
Classification: Unclassified
   Product: gcc
   Version: 4.7.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: fortran
AssignedTo: unassig...@gcc.gnu.org
ReportedBy: edouard.ca...@irisa.fr


For the following code:


program test1

   implicit none

   double precision, allocatable :: C(:,:)
   integer :: i

   allocate( C(3,2) )
   open(10,file='C.dat')
   do i = 1, 4
  read(10,*) C(i,:) ! fbounds-check doesn't work
   end do
   close(10)

end program


gfortran doesn't catch at run-time the last data read using the first dimension
i=4

The data file 'C.dat' is not important, I have used:
$ cat C.dat
1.0 -1.0
2.0 -2.0
3.0 -3.0
4.0 -4.0

but it can contains any numerical data spread over two columns.


---
The previous code has been compiled with:

$ gfortran -fbounds-check -o test1 test1.f90

The failure occurs at least for the following version of gcc:
4.3.6, 4.4.7, 4.5.3, 4.6.3, 4.7.0
i.e. all known versions from 4.3


[Bug fortran/52788] -fbounds-check fails for 2-rank allocatable arrays when reading

2012-03-30 Thread Edouard.Canot at irisa dot fr
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52788

--- Comment #1 from Edouard.Canot at irisa dot fr 2012-03-30 07:11:41 UTC ---
For a one dimensional allocatable array, gfortran leads to a correct behavior
when reading, i.e. it detects the bounds overflow.


[Bug fortran/41359] Wrong line numbers for debugging/profiling

2011-02-22 Thread Edouard.Canot at irisa dot fr
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41359

--- Comment #12 from Edouard.Canot at irisa dot fr 2011-02-22 10:36:41 UTC ---
On Tuesday 22 February 2011 11:26:53 you wrote:
(quoting burnus at gcc dot gnu.org gcc-bugzi...@gcc.gnu.org)
 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41359
 
 Tobias Burnus burnus at gcc dot gnu.org changed:
 
What|Removed |Added
 
  Status|NEW |RESOLVED
  Resolution||FIXED
 
 --- Comment #11 from Tobias Burnus burnus at gcc dot gnu.org 2011-02-22 
 10:26:23 UTC ---
 FIXED on the trunk (4.6). Thanks for the report, Edouard, and sorry for 
 needing
 one and a half years for fixing it.
 

Thanks for you, too. You are welcome.
Regards,
Édouard Canot