From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id E626E2C0345 for ; Fri, 12 Jul 2013 21:38:41 +1000 (EST) Received: from tom.nabble.com ([192.168.236.105]) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1UxbgN-00025Z-2w for linuxppc-dev@ozlabs.org; Fri, 12 Jul 2013 04:38:39 -0700 Date: Fri, 12 Jul 2013 04:38:39 -0700 (PDT) From: JiveTalkin To: linuxppc-dev@ozlabs.org Message-ID: <1373629119047-73669.post@n7.nabble.com> In-Reply-To: <1373464479578-73565.post@n7.nabble.com> References: <1373464479578-73565.post@n7.nabble.com> Subject: Re: ABI defined register usage within function calls MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Moderator..can you change the subject of this to "Understanding register usage as per ABI rules for functions" ?? Additionally, doesn't anyone have anything to say about this? -- View this message in context: http://linuxppc.10917.n7.nabble.com/ABI-defined-register-usage-within-function-calls-tp73565p73669.html Sent from the linuxppc-dev mailing list archive at Nabble.com.