From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4231 invoked by alias); 6 Apr 2002 20:26:01 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 4217 invoked by uid 71); 6 Apr 2002 20:26:01 -0000 Date: Sat, 06 Apr 2002 12:26:00 -0000 Message-ID: <20020406202601.4216.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: "John David Anglin" Subject: Re: fortran/6138: Incorrect access of integer*1 variables on PA Reply-To: "John David Anglin" X-SW-Source: 2002-04/txt/msg00414.txt.bz2 List-Id: The following reply was made to PR fortran/6138; it has been noted by GNATS. From: "John David Anglin" To: toon@moene.indiv.nluug.nl (Toon Moene) Cc: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org Subject: Re: fortran/6138: Incorrect access of integer*1 variables on PA Date: Sat, 6 Apr 2002 15:24:27 -0500 (EST) > Unfortunately, after half a day of fiddling, I'm not sure if the reason > this fails on HPPA is the same as the reason it fails on POWERPC. On the PA, I am fairly certain the problem is in the "conversion" from INTEGER*2 to INTEGER*1. > On the latter, even the following is incorrect: > > INTEGER*1 I > I = -9 > PRINT*,I > END > > which prints 247 ;-) OK under hppa-linux. What's the assembly code look like? The problems still could be related. I would guess the wrong location for I is being passed. > Welllllll, perhaps this means that this afternoon multiplied one problem > into two :-( Sorry. Dave -- J. David Anglin dave.anglin@nrc.ca National Research Council of Canada (613) 990-0752 (FAX: 952-6605)