From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15779 invoked by alias); 4 Dec 2002 10:02:15 -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 15772 invoked from network); 4 Dec 2002 10:02:13 -0000 Received: from unknown (HELO fw-cam.cambridge.arm.com) (193.131.176.3) by sources.redhat.com with SMTP; 4 Dec 2002 10:02:13 -0000 Received: by fw-cam.cambridge.arm.com; id KAA25165; Wed, 4 Dec 2002 10:02:12 GMT Received: from unknown(172.16.1.2) by fw-cam.cambridge.arm.com via smap (V5.5) id xma025074; Wed, 4 Dec 02 10:02:08 GMT Received: from pc960.cambridge.arm.com (pc960.cambridge.arm.com [10.1.205.4]) by cam-admin0.cambridge.arm.com (8.9.3/8.9.3) with ESMTP id KAA19831; Wed, 4 Dec 2002 10:02:07 GMT Received: from pc960.cambridge.arm.com (rearnsha@localhost) by pc960.cambridge.arm.com (8.11.6/8.9.3) with ESMTP id gB4A27w05408; Wed, 4 Dec 2002 10:02:07 GMT Message-Id: <200212041002.gB4A27w05408@pc960.cambridge.arm.com> X-Authentication-Warning: pc960.cambridge.arm.com: rearnsha owned process doing -bs To: Fernando Nasser cc: Michael Snyder , gdb-patches@sources.redhat.com, rearnsha@arm.com, cagney@redhat.com, kevinb@redhat.com, fnasser Reply-To: Richard.Earnshaw@arm.com Organization: ARM Ltd. X-Telephone: +44 1223 400569 (direct+voicemail), +44 1223 400400 (switchbd) X-Fax: +44 1223 400410 X-Address: ARM Ltd., 110 Fulbourn Road, Cherry Hinton, Cambridge CB1 9NJ. Subject: Re: [RFA] arm_extract_return_value, big-endian In-reply-to: Your message of "Tue, 03 Dec 2002 10:52:12 EST." <3DECD32C.2050403@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 04 Dec 2002 02:02:00 -0000 From: Richard Earnshaw X-SW-Source: 2002-12/txt/msg00111.txt.bz2 fnasser@redhat.com said: > Humm..., I am having second thoughts about this. Isn't the problem > you are seeing the same problem of not having the values peoperly > sign-extended? No. In this case we really need to copy the least significant 1 (or 2) bytes into the 1 or 2 bytes in the valbuf target. That means doing a copy from the higher addresses. So in that respect, the patch is correct. But it breaks the case where the return value is more than one word. R.