public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/28174]  New: Corruption of multiple character arrays when passing array sections
@ 2006-06-26 20:58 anlauf at gmx dot de
  2006-06-26 21:01 ` [Bug fortran/28174] " anlauf at gmx dot de
                   ` (8 more replies)
  0 siblings, 9 replies; 10+ messages in thread
From: anlauf at gmx dot de @ 2006-06-26 20:58 UTC (permalink / raw)
  To: gcc-bugs

Here's a very strange example of data corruption when passing
a character array section in the form

  call foo (a(:)(7:11))

to a subroutine even if the parameter is declared as INTENT(IN).
Furthermore, even another array gets corrupted which is intended
to hold a copy.

See testcase for details.

Cheers,
-ha


-- 
           Summary: Corruption of multiple character arrays when passing
                    array sections
           Product: gcc
           Version: 4.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: anlauf at gmx dot de
  GCC host triplet: i686-pc-linux-gnu


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


^ permalink raw reply	[flat|nested] 10+ messages in thread

end of thread, other threads:[~2006-07-13  5:07 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-06-26 20:58 [Bug fortran/28174] New: Corruption of multiple character arrays when passing array sections anlauf at gmx dot de
2006-06-26 21:01 ` [Bug fortran/28174] " anlauf at gmx dot de
2006-06-27 20:13 ` pault at gcc dot gnu dot org
2006-06-29 22:14 ` patchapp at dberlin dot org
2006-06-30  0:08 ` pault at gcc dot gnu dot org
2006-07-04 20:16 ` pault at gcc dot gnu dot org
2006-07-04 20:36 ` pault at gcc dot gnu dot org
2006-07-06 15:35 ` pault at gcc dot gnu dot org
2006-07-06 15:37 ` pault at gcc dot gnu dot org
2006-07-13  5:07 ` pault at gcc dot gnu dot org

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).