summaryrefslogtreecommitdiffstats
path: root/dts/Bindings/leds
diff options
context:
space:
mode:
authorSascha Hauer <s.hauer@pengutronix.de>2015-07-08 12:50:25 +0200
committerSascha Hauer <s.hauer@pengutronix.de>2015-07-08 12:57:34 +0200
commitd0c482359f89e8ea4d4c9ee558f94868f2a78ca2 (patch)
tree98255969e5c6c34706f35ec0cd91e0cb34d4fcbe /dts/Bindings/leds
parentd46b6785c4bcd3ceb7d90895e9f44a7bf7d6757d (diff)
downloadbarebox-d0c482359f89e8ea4d4c9ee558f94868f2a78ca2.tar.gz
barebox-d0c482359f89e8ea4d4c9ee558f94868f2a78ca2.tar.xz
Build with -fno-delete-null-pointer-checks
This becomes important with gcc-4.9. Without this gcc assumes that accessing NULL pointers traps and everything that happens behind the access is not executed. This recently happened with i.MX53 which has: static int imx53_silicon_revision(void) { void __iomem *rom = MX53_IROM_BASE_ADDR; rev = readl(rom + SI_REV); ... } This resulted in object code in which the last instruction is the readl, the reset of the function is missing because gcc assumes this is never executed. Disable this optimization with -fno-delete-null-pointer-checks since in barebox NULL pointers can indeed be valid. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'dts/Bindings/leds')
0 files changed, 0 insertions, 0 deletions