From: Billy <billy@dadadada.net>
To: eCos discussion <ecos-discuss@sources.redhat.com>
Subject: [ECOS] variable length automatic arrays.
Date: Sun, 17 Apr 2005 15:36:00 -0000 [thread overview]
Message-ID: <42627DC6.8070006@dadadada.net> (raw)
Short question:
Does eCos allocate dynamically sized arrays?
Longer version:
I'm worried about dynamic arrays under arm-elf-gcc 3.3.4.
Looks like our application code, at least, is being adversely
affected by this bug:
"gcc-3.3: Miscompiles automatic dynamic arrays"
http://lists.debian.org/debian-gcc/2004/07/msg00135.html
So we're going through our app hunting these down. Upgrading
the compiler to 3.4 might fix it, but new parser fussiness
appears to be making that a more painful option than bughunting.
Does eCos code rely on this gcc feature? Do we have
to audit eCos code for varlength automatic arrays
or just our app code?
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2005-04-17 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-17 15:36 Billy [this message]
2005-04-17 16:09 ` Andrew Lunn
2005-04-18 13:20 ` Nick Garnett
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=42627DC6.8070006@dadadada.net \
--to=billy@dadadada.net \
--cc=ecos-discuss@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).