From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18538 invoked by alias); 12 Sep 2002 14:49:53 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 18457 invoked from network); 12 Sep 2002 14:49:50 -0000 Received: from unknown (HELO mailhost.intrinsity.com) (208.246.32.130) by sources.redhat.com with SMTP; 12 Sep 2002 14:49:50 -0000 Received: from victoria.eng.evsx.com (victoria.eng.evsx.com [192.168.1.29]) by mailhost.intrinsity.com (Postfix) with ESMTP id 907923F3A6; Thu, 12 Sep 2002 09:49:49 -0500 (CDT) Received: from beeville.vert.intrinsity.com (beeville.vert.intrinsity.com [192.168.3.48]) by victoria.eng.evsx.com (8.10.1/8.10.1) with ESMTP id g8CEnn012186; Thu, 12 Sep 2002 09:49:49 -0500 (CDT) From: Fred Fish Received: (from fnf@localhost) by beeville.vert.intrinsity.com (8.11.2/8.11.4) id g8CEnmL09055; Thu, 12 Sep 2002 09:49:48 -0500 Message-Id: <200209121449.g8CEnmL09055@beeville.vert.intrinsity.com> Subject: Re: MIPS sign extension of addresses To: macro@ds2.pg.gda.pl (Maciej W. Rozycki) Date: Thu, 12 Sep 2002 07:49:00 -0000 Cc: fnf@intrinsity.com (Fred Fish), binutils@sources.redhat.com, gdb@sources.redhat.com Reply-To: fnf@intrinsity.com (Fred Fish) In-Reply-To: from "Maciej W. Rozycki" at Sep 10, 2002 06:57:49 PM MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2002-09/txt/msg00111.txt.bz2 > Well, that seems the reason of the trouble -- for MIPS addresses in > object and executable files should be treated as signed and bfd_vma should > be a signed type since that's how MIPS works. So does that mean that it would be more desirable if the MIPS ports used signed long long for bfd_vma/CORE_ADDR instead of unsigned long long? I'm willing to work on making that happen if that is the consensus for making MIPS support more consistent with how the hardware works. I've not yet checked, but are there fundamental reasons why bfd_vma or CORE_ADDR have to be unsigned? -Fred