From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14569 invoked by alias); 1 Jul 2009 07:52:22 -0000 Received: (qmail 14491 invoked by uid 48); 1 Jul 2009 07:51:59 -0000 Date: Wed, 01 Jul 2009 07:52:00 -0000 Message-ID: <20090701075159.14490.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug fortran/40598] Some missed optimizations in array assignment In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "burnus at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2009-07/txt/msg00013.txt.bz2 ------- Comment #5 from burnus at gcc dot gnu dot org 2009-07-01 07:51 ------- (In reply to comment #4) Here, I do not get any segfault/problem with valgrind (for gfortran and a.out). > tmp = build4 (ARRAY_RANGE_REF, TREE_TYPE (dest), dest, > build_int_cst (gfc_array_index_type, 3), I actually do not understand why "3" works. If I read gccint (cf. comment 2) correctly I would have expect that one needs to passe the byte size. But it seems to work as the dump / a.out indicates. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40598