From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14514 invoked by alias); 25 Apr 2002 03:06:20 -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 14507 invoked from network); 25 Apr 2002 03:06:20 -0000 Received: from unknown (HELO nile.gnat.com) (205.232.38.5) by sources.redhat.com with SMTP; 25 Apr 2002 03:06:20 -0000 Received: by nile.gnat.com (Postfix, from userid 338) id D3D43F28C9; Wed, 24 Apr 2002 23:06:19 -0400 (EDT) To: charlet@ACT-Europe.FR, dave@hiauly1.hia.nrc.ca Subject: Re: PA specifies invalid T_ADAFLAGS Cc: gcc@gcc.gnu.org, willy@debian.org Message-Id: <20020425030619.D3D43F28C9@nile.gnat.com> Date: Wed, 24 Apr 2002 20:09:00 -0000 From: dewar@gnat.com (Robert Dewar) X-SW-Source: 2002-04/txt/msg01275.txt.bz2 > Is this a bug in the PA backend? Without fixing the problem, it will not > be possible to correctly build GNAT under hppa-linux, except by starting > with a working hpux port. It's been some time since I tried it but > starting from the last binary release for hpux was very difficult because > there are major problems building the current source with 2.8.1x. No, it is not a bug in the PA backend, it is just that the segmentation in HPPA works on the base address before indexing. This means that if you use virtual indexing (an important part of the data structure approach used by GNAT), then the virual origin can be in the "wrong" segment.