This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/35820] internal compiler error with nested FORALL
- From: "pault at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 22 Oct 2008 15:30:50 -0000
- Subject: [Bug fortran/35820] internal compiler error with nested FORALL
- References: <bug-35820-15620@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #7 from pault at gcc dot gnu dot org 2008-10-22 15:30 -------
(In reply to comment #3)
> Confirm. While I do not get any crash like Dominique, valgrind shows that that
> there is a problem:
>
> ==20532== Invalid write of size 8
> ==20532== at 0x463933: resolve_code (resolve.c:5902)
> ==20532== by 0x4661DB: gfc_resolve_blocks (resolve.c:5988)
>
> ==20532== Invalid read of size 8
> ==20532== at 0x45B12E: gfc_resolve_assign_in_forall (resolve.c:5744)
> ==20532== by 0x463A5C: resolve_code (resolve.c:5833)
>
> I cannot look at the source as the computer where I've build gfortran is
> currently off.
Tobias,
How do you extract this diagnostic from valgrind? I have never used it before
but found it rolled into FC9.
Cheers
Paul
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35820