------- Comment #3 from burnus at gcc dot gnu dot org  2008-10-11 11:11 -------
(In reply to comment #2)
> In the original post I wrote:
> > Between revisions 140923 and 140951 the following (invalid) code:

I had not read the mailing list when I reading this PR. (See:
http://gcc.gnu.org/ml/fortran/2008-10/msg00066.html ) And Thomas' bug report
gave a completely different impression.

> > Since the code is invalid (d = matmul...), gfortran is indeed allowed to do
> > whatever is happening, but I'ld like to understand the new behavior
> > and be sure that it cannot happen for valid codes.

I think it only gets triggered due to the overwritten memory.

> Note 1: I think the error message with -fbounds-check is misleading:
> Note3: I think the same misleading error message happens for mat-2.f90 in

OK. I changed the bug summary and reopened the bug.


-- 

burnus at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |UNCONFIRMED
           Keywords|                            |diagnostic
         Resolution|INVALID                     |
            Summary|[4.4 Regression] array      |Improve wording for matmul
                   |descriptors for matmul      |bound checking
                   |messed up?                  |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37802

Reply via email to