From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] assembly syntax in plan 9
Date: Mon, 16 Jan 2012 11:03:43 -0800 [thread overview]
Message-ID: <CFE0D78F-3C9A-4DB5-A3F2-13A8FC54BD74@bitblocks.com> (raw)
In-Reply-To: <CAE9W7-gXhbmmVw-o6fwTJtr6KNhdmiow3_p-S8=5hz21X7i1uA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 723 bytes --]
How do you deal with longjmp?
On Jan 16, 2012, at 10:51 AM, Comeau At9Fans <comeauat9fans@gmail.com> wrote:
> On Mon, Jan 16, 2012 at 10:41 AM, Bakul Shah <bakul@bitblocks.com> 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.
[-- Attachment #2: Type: text/html, Size: 1192 bytes --]
next prev parent reply other threads:[~2012-01-16 19:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 12:30 Alexander Kapshuk
2012-01-16 13:08 ` Charles Forsyth
2012-01-16 13:27 ` Alexander Kapshuk
2012-01-16 15:41 ` Bakul Shah
2012-01-16 18:51 ` Comeau At9Fans
2012-01-16 19:03 ` Bakul Shah [this message]
2012-01-16 19:39 ` Charles Forsyth
2012-01-17 19:27 ` Comeau At9Fans
[not found] ` <CAOw7k5iYxoVUHYYxf1Dg9ESWwTon_aGFxhNkuyUGbkXwiKO9DA@mail.gmail.c>
2012-01-16 19:49 ` erik quanstrom
2012-01-17 19:29 ` Comeau At9Fans
2012-01-16 20:11 ` Joel C. Salomon
2012-01-16 23:18 ` Bakul Shah
2012-01-17 19:31 ` Comeau At9Fans
2012-01-17 19:21 ` Comeau At9Fans
2012-01-18 17:48 ` Bakul Shah
2012-01-18 18:32 ` Comeau At9Fans
2012-01-16 16:07 ` Joel C. Salomon
2012-01-16 16:27 ` erik quanstrom
2012-01-16 16:40 ` Charles Forsyth
2012-01-16 16:54 ` Bakul Shah
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CFE0D78F-3C9A-4DB5-A3F2-13A8FC54BD74@bitblocks.com \
--to=bakul@bitblocks.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).