From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25468 invoked by alias); 20 Jan 2003 02:08:11 -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 24623 invoked from network); 20 Jan 2003 02:08:06 -0000 Received: from unknown (HELO localhost.redhat.com) (205.151.14.190) by 172.16.49.205 with SMTP; 20 Jan 2003 02:08:06 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id D61993EFD for ; Sun, 19 Jan 2003 21:07:58 -0500 (EST) Message-ID: <3E2B59FE.8090401@redhat.com> Date: Mon, 20 Jan 2003 02:08: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: gdb-patches@sources.redhat.com Subject: HP/UX 64 need CALL_DUMMY_LOCATION ON_STACK? Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-01/txt/msg00676.txt.bz2 Hello, In checking various things to do with dummy frames, I noticed this potential foo-bar. 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? Andrew