diff options
author | Kevin Hao <haokexin@gmail.com> | 2015-01-15 12:07:33 +0000 |
---|---|---|
committer | Catalin Marinas <catalin.marinas@arm.com> | 2015-01-15 15:52:21 +0000 |
commit | d67703a8a69eecc8367bb9f848640b9efd430337 (patch) | |
tree | ae63f78378941268b3001d763f5ec7cde078e040 /arch/powerpc/kvm/book3s_emulate.c | |
parent | 0ce339a9e60d417e2747ff7c4869d9691a606e49 (diff) | |
download | talos-op-linux-d67703a8a69eecc8367bb9f848640b9efd430337.tar.gz talos-op-linux-d67703a8a69eecc8367bb9f848640b9efd430337.zip |
arm64: kill off the libgcc dependency
The arm64 kernel builds fine without the libgcc. Actually it should not
be used at all in the kernel. The following are the reasons indicated
by Russell King:
Although libgcc is part of the compiler, libgcc is built with the
expectation that it will be running in userland - it expects to link
to a libc. That's why you can't build libgcc without having the glibc
headers around.
[...]
Meanwhile, having the kernel build the compiler support functions that
it needs ensures that (a) we know what compiler support functions are
being used, (b) we know the implementation of those support functions
are sane for use in the kernel, (c) we can build them with appropriate
compiler flags for best performance, and (d) we remove an unnecessary
dependency on the build toolchain.
Signed-off-by: Kevin Hao <haokexin@gmail.com>
Acked-by: Will Deacon <will.deacon@arm.com>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Diffstat (limited to 'arch/powerpc/kvm/book3s_emulate.c')
0 files changed, 0 insertions, 0 deletions