From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] Add assert() for debug assertions
Date: Wed, 29 Jun 2011 17:54:57 -0400 [thread overview]
Message-ID: <201106291755.04266.vapier@gentoo.org> (raw)
In-Reply-To: <20110629210124.0F53A15AEB8D@gemini.denx.de>
On Wednesday, June 29, 2011 17:01:23 Wolfgang Denk wrote:
> Mike Frysinger wrote:
> > do we really care about that when people are using #define DEBUG ? i'd
> > say this is an unnecessary indirection ...
>
> Yes, we do care about the memory footprint - no matter whether with or
> without DEBUG.
there's caring about it, and there's nitpicking over ~10 bytes per call site.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20110629/70affcb3/attachment.pgp
next prev parent reply other threads:[~2011-06-29 21:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 19:49 [U-Boot] [PATCH v3] Add assert() for debug assertions Simon Glass
2011-06-29 20:43 ` Mike Frysinger
2011-06-29 21:01 ` Wolfgang Denk
2011-06-29 21:54 ` Mike Frysinger [this message]
2011-09-07 22:29 ` Simon Glass
2011-09-09 0:34 ` Mike Frysinger
2011-09-09 13:55 ` Simon Glass
2011-09-09 22:04 ` Wolfgang Denk
2011-09-09 22:38 ` [U-Boot] [PATCH] Fix warning: "assert" redefined Wolfgang Denk
2011-09-09 22:46 ` Simon Glass
2011-09-10 20:37 ` Wolfgang Denk
2011-09-10 14:07 ` [U-Boot] [PATCH] utx8245: fix build breakage due to assert() Wolfgang Denk
2011-09-10 20:42 ` Wolfgang Denk
2011-09-10 14:19 ` [U-Boot] [PATCH] tegra2: fix warning: "assert" redefined Wolfgang Denk
2011-09-10 20:44 ` Wolfgang Denk
2011-09-12 4:39 ` Simon Glass
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=201106291755.04266.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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