From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17609 invoked by alias); 1 Aug 2002 20:54:55 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 17602 invoked from network); 1 Aug 2002 20:54:54 -0000 Received: from unknown (HELO cygnus.com) (205.180.83.203) by sources.redhat.com with SMTP; 1 Aug 2002 20:54:54 -0000 Received: from redhat.com (reddwarf.sfbay.redhat.com [172.16.24.50]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id NAA16083; Thu, 1 Aug 2002 13:54:19 -0700 (PDT) Message-ID: <3D499BCF.2E79188@redhat.com> Date: Thu, 01 Aug 2002 13:54:00 -0000 From: Michael Snyder Organization: Red Hat, Inc. X-Accept-Language: en MIME-Version: 1.0 To: Andrew Cagney CC: Kevin Buettner , gdb-patches@sources.redhat.com Subject: Re: [PATCH] 64-bit support for Irix 6 References: <1020731172757.ZM21630@localhost.localdomain> <3D494F95.5060708@ges.redhat.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2002-08/txt/msg00018.txt.bz2 Andrew Cagney wrote: > > > > > #include "mips/tm-bigmips.h" > > > > +#undef MIPS_REGSIZE > > +#define MIPS_REGSIZE 8 > > + > > /* SGI's assembler doesn't grok dollar signs in identifiers. > > So we use dots instead. This item must be coordinated with G++. */ > > #undef CPLUS_MARKER > > @@ -89,11 +92,12 @@ > > 32 * sizeof(double) + ((N) - 32) * MIPS_REGSIZE) > > > > #undef REGISTER_VIRTUAL_TYPE > > +/* define 8 byte register type */ > > #define REGISTER_VIRTUAL_TYPE(N) \ > > (((N) >= FP0_REGNUM && (N) < FP0_REGNUM+32) ? builtin_type_double \ > > : ((N) == 32 /*SR*/) ? builtin_type_uint32 \ > > : ((N) >= 70 && (N) <= 89) ? builtin_type_uint32 \ > > - : builtin_type_int) > > + : builtin_type_long_long) > > > > /* Force N32 ABI as the default. */ > > #define MIPS_DEFAULT_ABI MIPS_ABI_N32 > > > > Kevin, this is wrong. > > It is no longer acceptable to add support for an additional sub-target > using non-multi-arch mechanisms. Does that mean that if we touch a macro, we have to multi-arch it? For instance, if we touch the PUSH_ARGUMENTS function, and PUSH_ARGUMENTS hasn't been multi-arched, do we have to multi-arch it?