From: erik quanstrom <quanstro@quanstro.net>
To: fernanbolando@mailc.net, 9fans@9fans.net
Subject: Re: [9fans] zero length arrays in gcc
Date: Tue, 22 Sep 2009 14:58:28 -0400 [thread overview]
Message-ID: <09dd2940addf4ad34b64bb04c2b9d06f@brasstown.quanstro.net> (raw)
In-Reply-To: <<1d5d51400909221149u32faccd7ue23a538afa523a23@mail.gmail.com>>
> pcc does not allow this since zero lenth array is another gcc
> extension. I tried declaring it as
>
> static unsigned startLabel[];
>
> The resulting bytecode can then be compiled however it will only
> crash. I traced it a pointer that tries to read an unallocated section
> in memory.
the only thing that makes sense is
static unsigned startLabel0;
static unsigned startLabel[] = &startLabel0
this might not work. one can't rule out deep and dark
magic with gcc.
- erik
next parent reply other threads:[~2009-09-22 18:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<1d5d51400909221149u32faccd7ue23a538afa523a23@mail.gmail.com>
2009-09-22 18:58 ` erik quanstrom [this message]
2009-09-22 18:49 Fernan Bolando
2009-09-22 19:19 ` Bakul Shah
2009-09-25 8:14 ` Fernan Bolando
2009-09-27 17:01 ` Russ Cox
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=09dd2940addf4ad34b64bb04c2b9d06f@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
--cc=fernanbolando@mailc.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).