From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: Date: Mon, 16 Jan 2012 13:51:45 -0500 Message-ID: From: Comeau At9Fans To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=20cf30051010c7bfdc04b6a9b4f1 Subject: Re: [9fans] assembly syntax in plan 9 Topicbox-Message-UUID: 5df76fce-ead7-11e9-9d60-3106f5b1d025 --20cf30051010c7bfdc04b6a9b4f1 Content-Type: text/plain; charset=ISO-8859-1 On Mon, Jan 16, 2012 at 10:41 AM, Bakul Shah wrote: > A frame pointer is needed for C99's variable length arrays but not > otherwise. Only an issue if ever plan9 C is extended to handle C99 or C1x. > gcc has to do the right thing even with -fno-frame-pointer. > What we do in problematic cases with Comeau is to generate code to arrange for the allocation of the VLA on the heap. I'm not saying this is perfect, but at least it gets the feature implementable and up and running as "a portable implementation" versus perhaps not being able to implement it at all on some platforms. --20cf30051010c7bfdc04b6a9b4f1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Mon, Jan 16, 2012 at 10:41 AM, Bakul Shah <bakul@bitblocks.com> wrote:
A frame pointer is needed for C99's varia= ble length arrays but not otherwise. Only an issue if ever plan9 C is exten= ded to handle C99 or C1x. gcc has to do the right thing even with -fno-fram= e-pointer.

What we do in problematic cases with= Comeau is to generate code to arrange for the allocation of the VLA on the= heap. =A0I'm not saying this is perfect, but at least it gets the feat= ure implementable and up and running as "a portable implementation&quo= t; versus perhaps not being able to implement it at all on some platforms.<= /div>
--20cf30051010c7bfdc04b6a9b4f1--