From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/5] Remove assert()
Date: Tue, 28 Nov 2017 21:30:47 -0500 [thread overview]
Message-ID: <20171129023047.GL3587@bill-the-cat> (raw)
In-Reply-To: <CAK7LNARJCozjj-ZfSe7aMBfJXH0FsAnrs0tcaNF9u1hLsa_o+w@mail.gmail.com>
On Wed, Nov 29, 2017 at 11:01:02AM +0900, Masahiro Yamada wrote:
> 2017-11-29 10:42 GMT+09:00 Tom Rini <trini@konsulko.com>:
> > On Wed, Nov 29, 2017 at 12:17:35AM +0900, Masahiro Yamada wrote:
> >> 2017-11-28 23:52 GMT+09:00 Tom Rini <trini@konsulko.com>:
> >> > On Tue, Nov 28, 2017 at 09:23:18PM +0900, Masahiro Yamada wrote:
> >> >
> >> >> Buildman test passed.
> >> >>
> >> >>
> >> >> Masahiro Yamada (5):
> >> >> Move CONFIG_PANIC_HANG to Kconfig
> >> >> ARM: openrd: set CONFIG_LOGLEVEL to 2
> >> >> Enable CONFIG_PANIC_HANG for boards without do_reset()
> >> >> treewide: convert assert() to BUG_ON()
> >> >> Remove assert()
> >> >
> >> > Have you done a size check on this series? If not, I'll fire one up,
> >> > thanks!
> >> >
> >>
> >> I think I did it correctly.
> >>
> >> At least, I needed the following patch for openrd boards:
> >> http://patchwork.ozlabs.org/patch/842106/
> >>
> >> Looks like the NAND core pull-request needs it, too.
> >
> > So, in my testing (which is gcc-6 for everything thanks to Debian/9):
> > 06: Remove assert()
> > arm: + clearfog peach-pi snow smdk5250 smdk5420 turris_omnia spring omap3_evm peach-pit
> > -(am335x_hs_evm) arm-linux-gnueabihf-ld.bfd: region `.sram' overflowed by 760 bytes
> > +(clearfog,turris_omnia) arm-linux-gnueabihf-ld.bfd: SPL image too big
> > +(am335x_hs_evm) arm-linux-gnueabihf-ld.bfd: region `.sram' overflowed by 1080 bytes
> > +(snow,smdk5250,peach-pi,smdk5420,spring,peach-pit) arch/arm/mach-exynos/built-in.o: In function `clock_calc_best_scalar':
> > +(snow,smdk5250,peach-pi,smdk5420,spring,peach-pit) build/../arch/arm/mach-exynos/clock.c:1408: undefined reference to `panic'
> > +(omap3_evm) arm-linux-gnueabihf-ld.bfd: region `.sram' overflowed by 28 bytes
> >
> > And then a lot of platforms grow in size. Taking a harder peek, BUG_ON
> > is always set. However, assert() is only set when DEBUG is set. Now, I
> > can certainly see an argument along the lines of that being fairly
> > unexpected, and I don't know that I would disagree.
> >
> > After a very quick look over what git grep -l says, perhaps we want to
> > introduce a new (default off) option to preserve the current behavior of
> > assert() in BUG_ON, as it looks like almost only kernel imported code is
> > using BUG_ON.
> >
>
> Do you have an idea for the option name?
ENABLE_BUG_ON_CHECKS ?
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20171128/fc4e4803/attachment.sig>
next prev parent reply other threads:[~2017-11-29 2:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 12:23 [U-Boot] [PATCH 0/5] Remove assert() Masahiro Yamada
2017-11-28 12:23 ` [U-Boot] [PATCH 1/5] Move CONFIG_PANIC_HANG to Kconfig Masahiro Yamada
2017-11-28 12:23 ` [U-Boot] [PATCH 2/5] ARM: openrd: set CONFIG_LOGLEVEL to 2 Masahiro Yamada
2017-11-28 15:37 ` Masahiro Yamada
2017-11-28 12:23 ` [U-Boot] [PATCH 3/5] Enable CONFIG_PANIC_HANG for boards without do_reset() Masahiro Yamada
2017-11-28 12:23 ` [U-Boot] [PATCH 4/5] treewide: convert assert() to BUG_ON() Masahiro Yamada
2017-11-29 13:08 ` Simon Glass
2017-11-29 14:17 ` Masahiro Yamada
2017-12-02 3:29 ` Simon Glass
2017-11-28 12:23 ` [U-Boot] [PATCH 5/5] Remove assert() Masahiro Yamada
2017-11-28 14:52 ` [U-Boot] [PATCH 0/5] " Tom Rini
2017-11-28 15:17 ` Masahiro Yamada
2017-11-29 1:42 ` Tom Rini
2017-11-29 2:01 ` Masahiro Yamada
2017-11-29 2:30 ` Tom Rini [this message]
2017-11-29 3:02 ` Masahiro Yamada
2017-11-29 3:04 ` Tom Rini
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=20171129023047.GL3587@bill-the-cat \
--to=trini@konsulko.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