From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6376 invoked by alias); 8 Feb 2002 07:08:06 -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 6181 invoked from network); 8 Feb 2002 07:07:33 -0000 Received: from unknown (HELO localhost.redhat.com) (24.114.26.18) by sources.redhat.com with SMTP; 8 Feb 2002 07:07:33 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id C92F03E76; Fri, 8 Feb 2002 02:07:31 -0500 (EST) Message-ID: <3C637933.7060502@cygnus.com> Date: Thu, 07 Feb 2002 23:08:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.7) Gecko/20020103 X-Accept-Language: en-us MIME-Version: 1.0 To: Richard.Earnshaw@arm.com Cc: gdb@sources.redhat.com Subject: Re: Moving to GDB_MULTI_ARCH_PARTIAL References: <200202061721.RAA02197@cam-mail2.cambridge.arm.com> <3C6349CB.5080700@cygnus.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-02/txt/msg00126.txt.bz2 > In the mean time I'll re-build everything :-/ i386-aout: gdbarch.h:1147: #error "Non multi-arch definition of REGISTER_CONVERTIBLE" gdbarch.h:1151: warning: `REGISTER_CONVERTIBLE' redefined tm.h:215: warning: this is the location of the previous definition gdbarch.h:1375: #error "Non multi-arch definition of PUSH_ARGUMENTS" gdbarch.h:1379: warning: `PUSH_ARGUMENTS' redefined tm.h:242: warning: this is the location of the previous definition looking around: tm-i386.h:#define REGISTER_CONVERTIBLE(regnum) i386_register_convertible (regnum) tm-ptx.h:#undef REGISTER_CONVERTIBLE tm-ptx.h:#define REGISTER_CONVERTIBLE(N) \ tm-symmetry.h:#undef REGISTER_CONVERTIBLE tm-symmetry.h:#define REGISTER_CONVERTIBLE(N) \ this suggests REGISTER_CONVERTIBLE doesn't need to be immediatly converted. However, it also explains why, at level one, it isn't strict about overriding macros. Given a case like the i386, the base cpu may be multi-arched but the variants (tm-ptx.h and tm-symmetry.h) may not. This again lets them continue to build and work. Andrew