From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5317 invoked by alias); 22 Aug 2003 21:11:41 -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 5310 invoked from network); 22 Aug 2003 21:11:39 -0000 Received: from unknown (HELO walton.kettenis.dyndns.org) (213.93.115.144) by sources.redhat.com with SMTP; 22 Aug 2003 21:11:39 -0000 Received: from elgar.kettenis.dyndns.org (elgar.kettenis.dyndns.org [192.168.0.2]) by walton.kettenis.dyndns.org (8.12.6p2/8.12.5) with ESMTP id h7MLBc0j002105 for ; Fri, 22 Aug 2003 23:11:38 +0200 (CEST) (envelope-from kettenis@elgar.kettenis.dyndns.org) Received: from elgar.kettenis.dyndns.org (localhost [127.0.0.1]) by elgar.kettenis.dyndns.org (8.12.6p2/8.12.6) with ESMTP id h7MLBcJh024942 for ; Fri, 22 Aug 2003 23:11:38 +0200 (CEST) (envelope-from kettenis@elgar.kettenis.dyndns.org) Received: (from kettenis@localhost) by elgar.kettenis.dyndns.org (8.12.6p2/8.12.6/Submit) id h7MLBct7024939; Fri, 22 Aug 2003 23:11:38 +0200 (CEST) To: gdb@sources.redhat.com Subject: Re: [RFC] Supporting alternative ABIs References: <20030822084054.GA1110@cygbert.vinschen.de> From: Mark Kettenis Date: Fri, 22 Aug 2003 21:11:00 -0000 In-Reply-To: Corinna Vinschen's message of "Fri, 22 Aug 2003 10:40:54 +0200" Message-ID: <86isop2y9h.fsf@elgar.kettenis.dyndns.org> X-SW-Source: 2003-08/txt/msg00263.txt.bz2 Corinna Vinschen writes: > - EXTRACT_RETURN_VALUE, STORE_RETURN_VALUE, USE_STRUCT_CONVENTION and > gdbarch_push_dummy_code gdbarch methods would be changed to expect > the type of the function, not the type of its return value. They > can use TYPE_TARGET_TYPE to get the return value type, but this will > also give them access to the `calling_convention' for the function type. > > - gdbarch_push_dummy_call and EXTRACT_STRUCT_VALUE_ADDRESS would > receive the function's type as an additional argument, to give them > access to the function's calling convention information. > > - USE_STRUCT_CONVENTION and gdbarch_push_dummy_code would not require > the `gcc_p' and `using_gcc' flags anymore since this information > is now given in the function type node. Due to the way, > gdbarch_parse_dwarf2_calling_convention evaluates the `calling_convention' > value, all inferior call-related gdbarch methods could simply trust its > value. I was working on the (32-bit) SPARC target today, and wished I had the function type available, so I'm positive this would be a good move. Mark