From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] use of C99
Date: Wed, 08 Apr 2009 16:01:51 -0500 [thread overview]
Message-ID: <49DD10BF.80002@freescale.com> (raw)
In-Reply-To: <49DD0E8A.904@freescale.com>
Scott Wood wrote:
> It frees the variable up for later such blocks to use. As does
> declaring iterators inside a for loop, but I guess that's forbidden as
> well. :-)
I'm not sure whether we want to allow the same variable to be defined
more than once, even with the same type, inside a function.
> Chances are it will allocate all stack space for all variables up front,
> regardless of where they're declared.
Yes, but it many cases it won't allocate any stack space at all because
it will just keep the variable in a register. My point was that if a
variable is defined later in a function, then it's more likely to have
limited scope, so the compiler will be more likely to use a register
instead of stack to store it.
>> This is what we do today, and I think it's ugly.
>
> Yes. But not as ugly as having two #ifdef blocks.
Agreed, but I don't consider it to be much of a compromise.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2009-04-08 21:01 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 18:51 [U-Boot] use of C99 Kumar Gala
2009-04-08 19:28 ` Wolfgang Denk
2009-04-08 19:46 ` Jerry Van Baren
2009-04-08 20:25 ` Timur Tabi
2009-04-08 20:46 ` Premi, Sanjeev
2009-04-08 20:57 ` Timur Tabi
2009-04-08 21:26 ` Premi, Sanjeev
2009-04-08 21:34 ` Timur Tabi
2009-04-08 21:03 ` Ben Warren
2009-04-08 21:23 ` Premi, Sanjeev
2009-04-08 20:52 ` Scott Wood
2009-04-08 21:01 ` Timur Tabi [this message]
2009-04-08 22:26 ` Scott Wood
2009-04-08 21:34 ` Wolfgang Denk
2009-04-08 21:38 ` Timur Tabi
2009-04-08 22:39 ` Graeme Russ
2009-04-08 22:45 ` Timur Tabi
2009-04-08 22:59 ` Wolfgang Denk
2009-04-08 23:09 ` Scott Wood
2009-04-08 22:28 ` Scott Wood
2009-04-08 21:27 ` Wolfgang Denk
2009-04-08 23:22 ` Larry Johnson
2009-04-08 23:40 ` Scott Wood
2009-04-09 4:27 ` Kumar Gala
2009-04-09 11:38 ` Jerry Van Baren
-- strict thread matches above, loose matches on Subject: below --
2009-04-09 1:53 Pink Boy
2009-04-09 2:12 ` Jerry Van Baren
2009-04-09 5:50 ` Wolfgang Denk
2009-04-09 13:27 ` Larry Johnson
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=49DD10BF.80002@freescale.com \
--to=timur@freescale.com \
--cc=u-boot@lists.denx.de \
/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