On 07.05.2025 03:05, Michael Ackermann via Tinycc-devel wrote:
$ arm-tcc --version
tcc version 0.9.28rc 2025-02-13 HEAD@f8bd136d* (ARM eabihf Linux)
$ pwd
musl-1.1.24-src
$ /usr/bin/arm-tcc -std=c99 -nostdinc -ffreestanding \
-D_XOPEN_SOURCE=700 -I./arch/arm -I./arch/generic -Iobj/src/internal \
-I./src/include -I./src/internal -Iobj/include -I./include -O1 -Wno-error \
-static -DBROKEN_EBX_ASM -DSYSCALL_NO_TLS=1 -DCRT -c \
-o obj/crt/Scrt1.o crt/Scrt1.c
In file included from crt/Scrt1.c:1:
In file included from crt/crt1.c:6:
./arch/arm/crt_arch.h:18: error: operand expected
Seems arm-tcc doesn't pick up the token for inline __asm__()
Hi,
I would say that certainly an attempt to compile a complete system
like yours has big potential to improve tinycc, however in order
to benefit from it (rather than just produce frustration), there
are still only two options I'm afraid:
1) you find the problem yourself (and possibly push or propose a fix)
2) you investigate the issue at least to the point where you can show
a reproducible test case.
In general, if tcc produces an error message such as
./arch/arm/crt_arch.h:18: error: operand expected
the purpose of that message is to help its user in the first place
rather than to be pasted into an email and to be sent to the devel-list.
How should anyone else be able to find out more easily than you what is
at line 18 of ./arch/arm/crt_arch.h which is a file on your computer.
-- grischka
The complete ebuild sys-libs:musl-1.1.24:20250507-000924.log is attached.
If musl-libc could be compiled with arm-tcc, then this would unblock further
~500 ebuilds that already passed with i386-tcc, to expand test-coverage for
arm-tcc. Although no kernel exists yet that could be compiled with arm-tcc
itself, for runtime testing the base-system profile should work with some
gcc-compiled kernel regardless (portability towards either linux2 or linux5
syscall abi tested OK already); meaning then both i386-tcc and arm-tcc
got some decent compile-time and run-time test-coverage with a complete
operating system release driven by TinyCC. Currently that is possible with
i386-tcc only. In theory the test-setup would be suitable for riscv64-tcc too
for compile-time/run-time testing this against a set of ~500 packages.
Regards
_______________________________________________
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
_______________________________________________
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
