From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16886 invoked by alias); 9 Oct 2013 05:09:50 -0000 Mailing-List: contact libffi-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libffi-discuss-owner@sourceware.org Received: (qmail 16872 invoked by uid 89); 9 Oct 2013 05:09:49 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-0.2 required=5.0 tests=AWL,BAYES_00,RDNS_NONE,SPF_HELO_PASS,SPF_PASS autolearn=no version=3.3.2 X-HELO: ygrex.ru Received: from Unknown (HELO ygrex.ru) (5.19.241.250) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Wed, 09 Oct 2013 05:09:48 +0000 Received: from ygrex-mac (c-24-6-109-123.hsd1.ca.comcast.net [24.6.109.123]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ygrex.ru (Postfix) with ESMTPSA id E6B59DE099; Wed, 9 Oct 2013 09:09:42 +0400 (MSK) Date: Wed, 09 Oct 2013 05:09:00 -0000 From: Igor Bogomazov To: Andrew Haley Cc: Anthony Green , Anthony Green , libffi-discuss@sourceware.org Subject: Re: return value buffer malloc()'ed vs alloca()'ed Message-ID: <20131008220936.6df82e24@ygrex-mac> In-Reply-To: <525444CE.80704@redhat.com> References: <20131008101354.43baeeeb@ygrex-mac> <5254428A.9080204@redhat.com> <1307910644.3010634.1381254018689.JavaMail.root@redhat.com> <525444CE.80704@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SW-Source: 2013/txt/msg00178.txt.bz2 On Tue, 08 Oct 2013 18:45:50 +0100 Andrew Haley wrote: > On 10/08/2013 06:40 PM, Anthony Green wrote: > > We've had this discussion many times... > > > > https://www.google.com/search?q=libffi+largest+integral+type&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a > > > > particularly... > > > > http://sourceware-org.1504.n7.nabble.com/closure-api-return-value-types-problem-td201402.html > > > > I've written it off as a wart that we must live with (so, a > > documentation bug). But maybe somebody can demonstrate how to > > change it without impacting current users. > > I'd garbage-collected it from my brain. I'm surprised no-one got > around to fixing the docs, and the "simple example" ! > > ... but then I didn't do it either. > > Andrew. > Thank you, I have got a clue stack/heap allocation does not matter here -- Sincerely yours, Igor Bogomazov