public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "terry at chem dot gu dot se" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/36683] New: -fbounds-check failure for allocated array and spread Date: Tue, 01 Jul 2008 05:22:00 -0000 [thread overview] Message-ID: <bug-36683-14178@http.gcc.gnu.org/bugzilla/> (raw) Unconformable array operations are not being picked up in the following: [tjf@rscpc28 Stoopid]$ cat badness.f90 program fred implicit none real,dimension(:,:),allocatable::A real,dimension(5)::v allocate(A(5,5)) A=5 v=5 A=A/spread(v,2,3) write(*,*)A(1,:) write(*,*)A(2,:) write(*,*)A(3,:) write(*,*)A(4,:) write(*,*)A(5,:) end [tjf@rscpc28 Stoopid]$ gfortran -Wall -O0 -W -Wtabs -g -fbounds-check -o badness badness.f90 [tjf@rscpc28 Stoopid]$ ./badness 1.00000000 1.00000000 1.00000000 5.0000000 5.0000000 1.00000000 1.00000000 1.00000000 5.0000000 5.0000000 1.00000000 1.00000000 1.00000000 5.0000000 5.0000000 1.00000000 1.00000000 1.00000000 5.0000000 5.0000000 1.00000000 1.00000000 1.00000000 5.0000000 5.0000000 [tjf@rscpc28 Stoopid]$ gfortran -v Using built-in specs. Target: i686-pc-linux-gnu Configured with: ../gcc-4.3-20080522/configure --disable-multilib --enable-languages=c,c++,fortran Thread model: posix gcc version 4.3.1 20080522 (prerelease) (GCC) Making the spread array too big [spread(v,2,13)] is not detected either. My quick attempts to do both in a single code caused glibc to freak out with "double free or corruption" detection. -- Summary: -fbounds-check failure for allocated array and spread Product: gcc Version: 4.3.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: terry at chem dot gu dot se GCC host triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36683
next reply other threads:[~2008-07-01 5:22 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-07-01 5:22 terry at chem dot gu dot se [this message] 2008-07-01 19:22 ` [Bug fortran/36683] " tkoenig at gcc dot gnu dot org 2008-10-12 12:11 ` tkoenig at gcc dot gnu dot org 2009-04-29 14:20 ` dominiq at lps dot ens dot fr
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-36683-14178@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).