kernel/tools/include/nolibc/arch-arm.h, branch linux-6.2.yHosts the 0x221E linux distro kernel.https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-6.2.y2022-04-21T00:05:46Ztools/nolibc: Remove .global _start from the entry point code2022-04-21T00:05:46ZAmmar Faiziammarfaizi2@gnuweeb.org2022-03-29T10:17:31Zurn:sha1:1590c59836dace3a20945bad049fe8802c4e6f3f
Building with clang yields the following error:
```
<inline asm>:3:1: error: _start changed binding to STB_GLOBAL
.global _start
^
1 error generated.
```
Make sure only specify one between `.global _start` and `.weak _start`.
Remove `.global _start`.
Cc: llvm@lists.linux.dev
Reviewed-by: Nick Desaulniers <ndesaulniers@google.com>
Acked-by: Willy Tarreau <w@1wt.eu>
Signed-off-by: Ammar Faizi <ammarfaizi2@gnuweeb.org>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
tools/nolibc: Replace `asm` with `__asm__`2022-04-21T00:05:46ZAmmar Faiziammarfaizi2@gnuweeb.org2022-03-29T10:17:30Zurn:sha1:37d62758e773939636b8fa64a1a39a8a0d3a9f8c
Replace `asm` with `__asm__` to support compilation with -std flag.
Using `asm` with -std flag makes GCC think `asm()` is a function call
instead of an inline assembly.
GCC doc says:
For the C language, the `asm` keyword is a GNU extension. When
writing C code that can be compiled with `-ansi` and the `-std`
options that select C dialects without GNU extensions, use
`__asm__` instead of `asm`.
Link: https://gcc.gnu.org/onlinedocs/gcc/Basic-Asm.html
Reported-by: Alviro Iskandar Setiawan <alviro.iskandar@gnuweeb.org>
Acked-by: Willy Tarreau <w@1wt.eu>
Signed-off-by: Ammar Faizi <ammarfaizi2@gnuweeb.org>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
tools/nolibc/arch: mark the _start symbol as weak2022-04-21T00:05:45ZWilly Tarreauw@1wt.eu2022-02-07T16:23:45Zurn:sha1:dffeb81af5fe5eedccf5ea4a8a120d8c3accd26e
By doing so we can link together multiple C files that have been compiled
with nolibc and which each have a _start symbol.
Signed-off-by: Willy Tarreau <w@1wt.eu>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
tools/nolibc/arch: split arch-specific code into individual files2022-04-21T00:05:43ZWilly Tarreauw@1wt.eu2022-02-07T16:23:17Zurn:sha1:271661c1cde5ff47eb7af9946866cd66b70dc328
In order to ease maintenance, this splits the arch-specific code into
one file per architecture. A common file "arch.h" is used to include the
right file among arch-* based on the detected architecture. Projects
which are already split per architecture could simply rename these
files to $arch/arch.h and get rid of the common arch.h. For this
reason, include guards were placed into each arch-specific file.
Signed-off-by: Willy Tarreau <w@1wt.eu>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>