From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12379 invoked by alias); 20 Jan 2003 04:27:13 -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 12087 invoked from network); 20 Jan 2003 04:27:09 -0000 Received: from unknown (HELO localhost.redhat.com) (205.151.14.190) by 172.16.49.205 with SMTP; 20 Jan 2003 04:27:09 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 88AFA3EFD; Sun, 19 Jan 2003 23:26:54 -0500 (EST) Message-ID: <3E2B7A8E.6050403@redhat.com> Date: Mon, 20 Jan 2003 04:27:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.1) Gecko/20021211 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Joel Brobecker Cc: gdb-patches@sources.redhat.com Subject: Re: HP/UX 64 need CALL_DUMMY_LOCATION ON_STACK? References: <3E2B59FE.8090401@redhat.com> <20030120030414.GK5477@gnat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-01/txt/msg00678.txt.bz2 >> I recently changed the default for CALL_DUMMY_LOCATION from ON_STACK to >> AT_ENTRY. I suspect the HP/PA 64 currently assumes ON_STACK. >> >> Anyone able to check this theory? > > > I'll try to have a look today (thanks for this notice!). I'd better explain why I think I broke it :-/ I believe the old code had the sequence: tm-hppa64.h: #include "tm-hppa.h" tm-hppa.h: #define CALL_DUMMY_LOCATION ON_STACK #undef CALL_DUMMY_LOCATION gdbarch.h: #if !multi-arch // do nothing with CALL_DUMMY_LOCATION #endif inferior.h: #ifndef CALL_DUMMY_LOCATION #define CALL_DUMMY_LOCATION ON_STACK #endif My change effectively changed the middle one so that CALL_DUMMY_LOCATION defaults to AT_ENTRY_POINT - good for everyone else, just not for 64 bit HP/UX. Andrew