From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18402 invoked by alias); 28 Jun 2010 08:48:18 -0000 Received: (qmail 18359 invoked by uid 48); 28 Jun 2010 08:48:05 -0000 Date: Mon, 28 Jun 2010 08:48:00 -0000 Message-ID: <20100628084805.18358.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug fortran/44662] unitialized memory on testcases abstract_type_6.f03 and typebound_call_4.f03 In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "dominiq at lps dot ens dot fr" 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: 2010-06/txt/msg02681.txt.bz2 ------- Comment #3 from dominiq at lps dot ens dot fr 2010-06-28 08:48 ------- This is likely the cause of recent failures for gfortran on ppc, see http://gcc.gnu.org/ml/gcc-testresults/2010-06/msg02876.html http://gcc.gnu.org/ml/gcc-testresults/2010-06/msg02871.html The patch in comment #2 fixes the regression for gfortran.dg/typebound_call_4.f03 on powerpc-apple-darwin9 without new failure. Is not the patch qualifying for "obvious"? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44662