build/core: Don't use -fno-strict-aliasing

Don't use -fno-strict-aliasing: It's no longer needed.

Change-Id: I7b6e9524197dc152b57a8d1900dd6d7f9fe3452d
Signed-off-by: Bernhard Rosenkraenzer <Bernhard.Rosenkranzer@linaro.org>
build: Use -Wno-error=strict-aliasing for the HOST compiler

Since everyone uses his own host compiler, and there's still a lot
of broken compilers that report false positives (gcc <= 4.5) around,
use -Wno-error=strict-aliasing for the HOST compiler.

If things are broken on the host side, we'll notice at build time
anyway.

Change-Id: I1a7db826866c4342d168c1efa7971a988d199d3a
Signed-off-by: Bernhard Rosenkraenzer <Bernhard.Rosenkranzer@linaro.org>
Revert "build: Use -Wno-error=strict-aliasing for the HOST compiler"

This reverts commit 074b9cc5c5308afeb0b83c68a7a1393edb5caead.
The commit prepended -Wno-error=strict-aliasing and was overridden.
Will commit a proper fix.
build: Don't add -fno-strict-aliasing to HOST compiler flags

Change-Id: I07eef86f11ec3761e0922855cb6ff881c2773966
Signed-off-by: Bernhard Rosenkraenzer <Bernhard.Rosenkranzer@linaro.org>
build: Explicitly disable -Werror=strict-alising for HOST builds

Change-Id: Ib1e834951196ab3ea6acbe47c27eebe5633f55d2
Signed-off-by: Bernhard Rosenkraenzer <Bernhard.Rosenkranzer@linaro.org>
build: Add option to disable strict-aliasing optimizations

This is useful for builds that pull in unmodified AOSP repositories
that can't be compiled with strict-aliasing compliance enabled

Change-Id: I0599127b1e113c0799dd8fa92db00b989ebc9bd3
Signed-off-by: Bernhard Rosenkraenzer <Bernhard.Rosenkranzer@linaro.org>