From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4344 invoked by alias); 4 Apr 2008 14:15:26 -0000 Received: (qmail 3655 invoked by uid 48); 4 Apr 2008 14:14:38 -0000 Date: Fri, 04 Apr 2008 14:15:00 -0000 Message-ID: <20080404141438.3654.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug fortran/35824] Overloading problems with derived type with allocatable array 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: 2008-04/txt/msg00356.txt.bz2 ------- Comment #2 from burnus at gcc dot gnu dot org 2008-04-04 14:14 ------- > Confirmed on powerpc-apple-darwin9 (but not on i686-apple-darwin9). The bus > error comes from the statement 'b%b=-a%b' in function 'neg_at'. If I insert > 'print *, allocated(a%b)' in the function, I get .false. on powerpc (but .true. > for i686) for 't1=-t1'. Also confirmed on x86-64-linux. I always get non allocated before and allocated after the allocation statement, which looks OK. I have to admit, I did not quickly see in the dump (-fdump-tree-original) why it is failing; at a glance, both calling "neg_at" in MAIN__ and the assignment in "neg_at" itself look ok; and "t2 = -t1" also works. Side question: Why do we initialize b.b.data with NULL 3 times? b.b.data = 0B; b.b.data = 0B; { struct alltype alltype.0; alltype.0.b.data = 0B; b = alltype.0; } -- burnus at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Keywords| |wrong-code Last reconfirmed|0000-00-00 00:00:00 |2008-04-04 14:14:38 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35824