This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/27874] Bad interaction between bounds checking, forall and derived types
- From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 3 Jun 2006 11:41:16 -0000
- Subject: [Bug fortran/27874] Bad interaction between bounds checking, forall and derived types
- References: <bug-27874-10259@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #2 from fxcoudert at gcc dot gnu dot org 2006-06-03 11:41 -------
Created an attachment (id=11588)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11588&action=view)
Code generated for testcase
See the code generated for this testcase (with my recent patch for improved
out-of-bounds messages). In order to create a temporary, we first run the i=1:1
loop once, without the conditionnal mask (which in this case is .false.), to
count the total length needed for the temporary (variable num.5). When doing
this, we perform bounds checking on elements that will not be used in the final
loop.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27874