From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27213 invoked by alias); 21 Apr 2002 03:08:48 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 27203 invoked from network); 21 Apr 2002 03:08:47 -0000 Received: from unknown (HELO hiauly1.hia.nrc.ca) (132.246.100.193) by sources.redhat.com with SMTP; 21 Apr 2002 03:08:47 -0000 Received: from hiauly1.hia.nrc.ca (localhost [127.0.0.1]) by hiauly1.hia.nrc.ca (8.12.0.Beta16/8.12.0.Beta16) with ESMTP id g3L38jFN022755; Sat, 20 Apr 2002 23:08:46 -0400 (EDT) Received: (from dave@localhost) by hiauly1.hia.nrc.ca (8.12.0.Beta16/8.12.0.Beta16) id g3L38jAi022753; Sat, 20 Apr 2002 23:08:45 -0400 (EDT) Message-Id: <200204210308.g3L38jAi022753@hiauly1.hia.nrc.ca> Subject: Re: GCC 3.1 Prerelease To: gcc@gcc.gnu.org Date: Sat, 20 Apr 2002 20:09:00 -0000 From: "John David Anglin" Cc: mark@codesourcery.com MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SW-Source: 2002-04/txt/msg01020.txt.bz2 These are the PA issues regarding the 3.1 release: Fortran: PR6138: Incorrect access of interger*1 variables on PA. This is a regression from 3.0.x, and it also affects powerpc. In my opinion, it is a verious serious bug affecting many programs and should be fixed before the 3.1 release. The problem is in the front-end, in code that I am not familiar with. C++: g++.jason/synth5.C: this testsuite fail is a regression that occurred about March 15. The errors are: synth5.h:3: storage size of `_ZTI1A' isn't known synth5.h:7: storage size of `_ZTI1B' isn't known At the moment, I don't consider this regression to be a very serious problem. It also affects powerpc. C: This thread discusses a problem initially found building bleadperl with hppa64-hp-hpux. While there is a problem with the machine definition, the analysis done so far points to problems in register allocation and optimization as the root causes of the compilation failure. These problems are not in 3.0.x. The register allocation issue seems similar to that discussed in this thread . In the PA case, a FP register was selected in a situation where a general register should have been selected. Dave -- J. David Anglin dave.anglin@nrc.ca National Research Council of Canada (613) 990-0752 (FAX: 952-6605)