From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-32851-listarch-gdb-patches=sources.redhat.com@sources.redhat.com>
Received: (qmail 12500 invoked by alias); 5 May 2004 15:44:20 -0000
Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-patches-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sources.redhat.com>
List-Help: <mailto:gdb-patches-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-patches-owner@sources.redhat.com
Received: (qmail 12485 invoked from network); 5 May 2004 15:44:20 -0000
Received: from unknown (HELO mx1.redhat.com) (66.187.233.31)
  by sources.redhat.com with SMTP; 5 May 2004 15:44:20 -0000
Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254])
	by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i45FiJkI029494
	for <gdb-patches@sources.redhat.com>; Wed, 5 May 2004 11:44:19 -0400
Received: from localhost.redhat.com (to-dhcp51.toronto.redhat.com [172.16.14.151])
	by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i45FiJv05314;
	Wed, 5 May 2004 11:44:19 -0400
Received: from gnu.org (localhost [127.0.0.1])
	by localhost.redhat.com (Postfix) with ESMTP
	id 77E942B9D; Wed,  5 May 2004 11:44:19 -0400 (EDT)
Message-ID: <40990BD3.1080506@gnu.org>
Date: Wed, 05 May 2004 15:44:00 -0000
From: Andrew Cagney <cagney@gnu.org>
User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040217
MIME-Version: 1.0
To: gdb-patches@sources.redhat.com
Subject: Re: [obish] Delete PARM_BOUNDARY
References: <4097E4EF.6010205@gnu.org>
In-Reply-To: <4097E4EF.6010205@gnu.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2004-05/txt/msg00138.txt.bz2

> Hello,
> 
> Other posts drew my attention to this:
> 
> - PARM_BOUNDARY is only used by push_value
> 
> - push_value is only used by legacy_push_arguments.
> 
> - legacy_push_arguments is only used when push_dummy_call isn't supplied
> 
> yet:
> 
> - only m68k sets PARAM_BOUNDARY
> 
> - m68k sets (as of recent changes) push_dummy_call
> 
> hence PARM_BOUNDARY is dead.
> 
> baring comments I'll commit this in a day or so,

I've checked this in.

Andrew

> 	* gdbarch.sh (PARM_BOUNDARY): Delete.
> 	gdbarch.h, gdbarch.c: Re-generate.
> 	* valops.c (PARM_BOUNDARY): Delete macro.
> 	(value_push): Delete PARM_BOUNDARY code.
> 	* m68k-tdep.c (m68k_gdbarch_init): Do not set parm_boundary.