From: Minkyu Kang <mk7.kang@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Please fix warnings on ARM Samsung boards
Date: Tue, 04 Nov 2014 10:02:32 +0900 [thread overview]
Message-ID: <545825A8.6040908@samsung.com> (raw)
In-Reply-To: <CAMhH57QzSMY=4jQ1FW7PvAj+cf5esB0bHhxLvUSE=HLxJT4aDg@mail.gmail.com>
Dear Masahiro YAMADA,
On 04/11/14 00:38, Masahiro YAMADA wrote:
> Hi Samsung developers,
>
>
> I see some warnings when I build Samsung boards.
>
>
> I requested this three months ago,
> but nobody would fix the warnings.
> http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/191762
>
>
>
>
> masahiro at oscar:~/workspace/u-boot$ arm-unknown-linux-gnueabi-gcc -v
> Using built-in specs.
> COLLECT_GCC=arm-unknown-linux-gnueabi-gcc
> COLLECT_LTO_WRAPPER=/opt/gcc-4.9.0-nolibc/arm-unknown-linux-gnueabi/bin/../libexec/gcc/arm-unknown-linux-gnueabi/4.9.0/lto-wrapper
> Target: arm-unknown-linux-gnueabi
> Configured with: /home/tony/buildall/src/gcc/configure
> --target=arm-unknown-linux-gnueabi --host=x86_64-linux-gnu
> --build=x86_64-linux-gnu --enable-targets=all
> --prefix=/opt/cross/gcc-4.9.0-nolibc/arm-unknown-linux-gnueabi/
> --enable-languages=c --with-newlib --without-headers --disable-nls
> --disable-threads --disable-shared --disable-libmudflap
> --disable-libssp --disable-libgomp --disable-decimal-float
> --enable-checking=release
> --with-mpfr=/home/tony/buildall/src/sys-x86_64
> --with-gmp=/home/tony/buildall/src/sys-x86_64 --disable-bootstrap
> --disable-libquadmath --disable-libatomic
> Thread model: single
> gcc version 4.9.0 (GCC)
> masahiro at oscar:~/workspace/u-boot$ make odroid_defconfig
> #
> # configuration written to .config
> #
> masahiro at oscar:~/workspace/u-boot$ make CROSS_COMPILE=arm-unknown-linux-gnueabi-
> [ snip ]
> LD arch/arm/cpu/armv7/s5p-common/built-in.o
> LD arch/arm/cpu/armv7/built-in.o
> AS arch/arm/cpu/armv7/start.o
> CC arch/arm/cpu/armv7/exynos/clock.o
> arch/arm/cpu/armv7/exynos/clock.c: In function 'clock_get_periph_rate':
> arch/arm/cpu/armv7/exynos/clock.c:264:47: warning: array subscript is
> above array bounds [-Warray-bounds]
> struct clk_bit_info *bit_info = &clk_bit_info[peripheral];
> ^
> arch/arm/cpu/armv7/exynos/clock.c:264:47: warning: array subscript is
> above array bounds [-Warray-bounds]
> [ snip ]
> LD arch/arm/lib/built-in.o
> CC arch/arm/lib/eabi_compat.o
> CC board/samsung/common/gadget.o
> CC board/samsung/common/misc.o
> CC board/samsung/common/board.o
> board/samsung/common/board.c: In function 'dram_init':
> board/samsung/common/board.c:95:32: warning: iteration 4u invokes
> undefined behavior [-Waggressive-loop-optimizations]
> addr = CONFIG_SYS_SDRAM_BASE + (i * SDRAM_BANK_SIZE);
> ^
> board/samsung/common/board.c:94:2: note: containing loop
> for (i = 0; i < CONFIG_NR_DRAM_BANKS; i++) {
> ^
> board/samsung/common/board.c: In function 'dram_init_banksize':
> board/samsung/common/board.c:107:32: warning: iteration 4u invokes
> undefined behavior [-Waggressive-loop-optimizations]
> addr = CONFIG_SYS_SDRAM_BASE + (i * SDRAM_BANK_SIZE);
> ^
> board/samsung/common/board.c:106:2: note: containing loop
> for (i = 0; i < CONFIG_NR_DRAM_BANKS; i++) {
> ^
I will check soon.
Thanks,
Minkyu Kang.
prev parent reply other threads:[~2014-11-04 1:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 15:38 [U-Boot] Please fix warnings on ARM Samsung boards Masahiro YAMADA
2014-11-04 1:02 ` Minkyu Kang [this message]
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=545825A8.6040908@samsung.com \
--to=mk7.kang@samsung.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