From: Comeau At9Fans <comeauat9fans@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] assembly syntax in plan 9
Date: Wed, 18 Jan 2012 13:32:37 -0500 [thread overview]
Message-ID: <CAE9W7-i7eeXD5pebO8EQDEDLoySG1+rHaS-v3PLFSqPUhWHJBg@mail.gmail.com> (raw)
In-Reply-To: <561264DD-3FF2-4FD9-82FD-78DC12DE3F05@bitblocks.com>
[-- Attachment #1: Type: text/plain, Size: 2015 bytes --]
On Wed, Jan 18, 2012 at 12:48 PM, Bakul Shah <bakul@bitblocks.com> wrote:
> On Jan 17, 2012, at 11:21 AM, Comeau At9Fans <comeauat9fans@gmail.com>
> wrote:
> On Mon, Jan 16, 2012 at 2:03 PM, Bakul Shah <bakul@bitblocks.com> wrote:
>
> How do you deal with longjmp?
>>
>
> I don't have it in front of me, but I do seem to recall the Standard
> allows that the VLA might still be around though, believe it has an example
> with said, for better or worse...
>
>
> Do you have a reference?
>
Ok, so, gunna make me look, let's see, ok: 7.13.2.1p5, note the may's and
might's. There should be narrative backing those up.
> 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.
>>
>>
> Seems to me if you can port C, you can use a FP to implement VLAs without
> alloca games and more efficiently. You can always store the FP in stack
> local memory if out of registers.
>
I probably overstated the situation by saying not being able to implement
it at all... probably should have said I never thought of it beyond the
obvious implementations.
--
Greg Comeau / 4.3.10.1 with C++0xisms now in beta!
Comeau C/C++ ONLINE ==> http://www.comeaucomputing.com/tryitout
World Class Compilers: Breathtaking C++, Amazing C99, Fabulous C90.
Comeau C/C++ with Dinkumware's Libraries... Have you tried it?
[-- Attachment #2: Type: text/html, Size: 3750 bytes --]
next prev parent reply other threads:[~2012-01-18 18:32 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
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 [this message]
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=CAE9W7-i7eeXD5pebO8EQDEDLoySG1+rHaS-v3PLFSqPUhWHJBg@mail.gmail.com \
--to=comeauat9fans@gmail.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).