From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1503 invoked by alias); 26 Apr 2002 17:56:31 -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 1435 invoked from network); 26 Apr 2002 17:56:29 -0000 Received: from unknown (HELO cygnus.com) (205.180.83.203) by sources.redhat.com with SMTP; 26 Apr 2002 17:56:29 -0000 Received: from porcupine.cygnus.com (remus.sfbay.redhat.com [172.16.27.252]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id KAA25980 for ; Fri, 26 Apr 2002 10:56:27 -0700 (PDT) Received: from porcupine.cygnus.com (IDENT:wonZRLBCudiL2ryHpixrA5Gq8UycH7pG@localhost.localdomain [127.0.0.1]) by porcupine.cygnus.com (8.12.2/8.12.2) with ESMTP id g3QHPUv9012865; Fri, 26 Apr 2002 11:25:30 -0600 Received: from porcupine.cygnus.com (law@localhost) by porcupine.cygnus.com (8.12.2/8.12.2/Submit) with ESMTP id g3QHPUDK012860; Fri, 26 Apr 2002 11:25:30 -0600 To: "John David Anglin" cc: willy@debian.org (Matthew Wilcox), gcc@gcc.gnu.org Subject: Re: PA specifies invalid T_ADAFLAGS Reply-To: law@redhat.com From: law@redhat.com In-reply-to: Your message of Thu, 25 Apr 2002 16:14:36 EDT. <200204252014.g3PKEb5K022548@hiauly1.hia.nrc.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 26 Apr 2002 10:56:00 -0000 Message-ID: <12859.1019841929@porcupine.cygnus.com> X-SW-Source: 2002-04/txt/msg01447.txt.bz2 In message <200204252014.g3PKEb5K022548@hiauly1.hia.nrc.ca>, "John David Anglin " writes: > > I'm not terribly familiar with gcc's configure / build system, so I don't > > know who's at fault here. Should PA be specifying this in X_ADAFLAGS? > > Should Ada not be using T_ADAFLAGS like this? > > I believe that this suggestion is correct. We should be specifying > X_ADAFLAGS in a "x-" file, or files. It's the host not the > target that's affected by this issue. The appropriate xmake_file > defines need to be added to config.gcc. I think we only want to do > this for the hpux, bsd and osf configurations (ie., those that use > the SOM linker and hppa64). The pro doesn't use space registers. > Linux puts the same value in all the relevant space registers. > Don't know about the memory models for the other elf ports. Actually OSF puts the same value in all the space registers. I don't recall what BSD did. Not that it matters, I don't believe anyone is still running the UofU BSD or OSF1 ports. The few embedded PAs were level 0 implementations -- which don't have space registers at all. jeff