[Tinycc-devel] NetBSD/aarch64 Unknown relocation type for got: 299

Yet another reloc error with clang, on NetBSD aarch64 this time uname -a NetBSD arm64 9.1 NetBSD 9.1 (GENERIC64) #0: Sun Oct 18 19:24:30 UTC 2020 mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/evbarm/compile/GENERIC64 evbarm ./configure --strip-binaries --cc=clang

[Tinycc-devel] Unknown relocation type for got: 285, the return!

Hi, I'm quite sure Herman fixed relocation error type 285 on aarch64. This morning it is back again on Linux Fedora 33 aarch64 (RPi 3) when tcc is boostrapped with clang (11) ./configure --strip-binaries --with-selinux --cc=clang --prefix=/home/jullien/tinycc/static Binary directory

[Tinycc-devel] NetBSD/aarch64 Unknown relocation type for got: 299

I fixed this one also. But the problem is that below commits are gone. This happended after te commit 'arm-asm: Implement branch to label '     Herman commit 94714f046b423b6ee10471575082419a280ac663 Author: herman

Re: [Tinycc-devel] x86_64 tcc doesn't set sign bit on NaNs

As long as my script that tests many build tcc configurations is happy, I'm happy too :o) -Original Message- From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of Michael Matz Sent: Monday, January 04, 2021 23:42 To: jull...@eligis.com;

Re: [Tinycc-devel] x86_64 tcc doesn't set sign bit on NaNs

Hello, On Mon, 4 Jan 2021, Christian Jullien wrote: Also on OpenBSD x64 with clang 10 Bah. I could fix this generically with using signbit(3) to check for the required sign flip, but I'm not sure how widespread it's availability or correctnes is on other platforms. So Hermans disabling

Re: [Tinycc-devel] issues/questions with stddef.h which comes with tcc

Does this mean that TCC works with CLang includes and libraries on Linux-arm, Linux-arm64, Linux x64, Linux-riscv, FreeBSD-x64, FreeBSD-arm64, NetBSD-x64, and NetBSD-arm64? That would be very useful. I mentioned wondering before but didn't get a useful answer. It's amazing that you have access

Re: [Tinycc-devel] issues/questions with stddef.h which comes with tcc

And I want to mention that there's a license problem for people who want to embed Tiny C in a product if they have to use GCC headers, since GCC is full GPL. It would be nice to supply people with a solution to that real problem. On Fri, Jan 1, 2021 at 3:30 PM Michael Matz wrote: > Hello, > >

Re: [Tinycc-devel] issues/questions with stddef.h which comes with tcc

I'm not buying this. Every operating system is supposed to come with a C runtime library and C include files that work on that specific OS and on every possible standard C compiler? You think C compilers are still that privileged? People don't even USE C anymore. I'm sure that was perfectly

Re: [Tinycc-devel] issues/questions with stddef.h which comes with tcc

That's wonderful. Yours and Ivo van Poorten's answers tell me that I don't have a problem. I was starting to think that the answer was: You're on your own. You'll have to come up with your own header and library that work, that's your problem, not ours. On Mon, Jan 4, 2021 at 9:59 AM Christian

Re: [Tinycc-devel] issues/questions with stddef.h which comes with tcc

On Mon, 4 Jan 2021 09:12:20 -0800 Joshua Scholar wrote: > And I want to mention that there's a license problem for people who > want to embed Tiny C in a product if they have to use GCC headers, > since GCC is full GPL. I have the impression that you do not know the difference between compiler

Re: [Tinycc-devel] issues/questions with stddef.h which comes with tcc

More good news. Thank you. On Mon, Jan 4, 2021 at 9:54 AM Ivo van Poorten wrote: > On Mon, 4 Jan 2021 09:12:20 -0800 Joshua Scholar > wrote: > > And I want to mention that there's a license problem for people who > > want to embed Tiny C in a product if they have to use GCC headers, > > since

Re: [Tinycc-devel] issues/questions with stddef.h which comes with tcc

Yup! I test them all for nearly every commits, or at least when I think a commit may break something. I have access to much more than 12 setups, most of them are mine others are from gnu farm. My OpenLisp compiler has been compiled on over 160 gnu triplets. The most uncommon are: zLinux,

Re: [Tinycc-devel] arm-asm: Test script

Hi, On Mon, 4 Jan 2021 05:05:40 +0100 (CET) Michael Matz wrote: > Yeah, put it into tests/ I'd say. Ok, I've added it as tests/arm-asm-testsuite.sh . > The x86 assembler also has a little > testfile in there that isn't used by default (as it shows a few > differences between GNU as and

[Tinycc-devel] [PATCH 2/3] arm-asm: Add ldrex, ldrexb, strex, strexb

--- arm-asm.c | 67 +-- arm-tok.h | 4 2 files changed, 69 insertions(+), 2 deletions(-) diff --git a/arm-asm.c b/arm-asm.c index 27f396b..5b64fa6 100644 --- a/arm-asm.c +++ b/arm-asm.c @@ -939,10 +939,11 @@ static void

[Tinycc-devel] [PATCH 1/3] arm-asm: Implement branch to label

--- arm-asm.c | 34 +++--- 1 file changed, 19 insertions(+), 15 deletions(-) diff --git a/arm-asm.c b/arm-asm.c index fc92898..27f396b 100644 --- a/arm-asm.c +++ b/arm-asm.c @@ -1058,9 +1058,9 @@ static uint32_t encbranchoffset(int pos, int addr, int fail) {

[Tinycc-devel] [PATCH 0/3] Improvements to ARM inline assembler

This patchset adds some more improvements to the ARM inline assembler. 1. Bugfix for branch instruction so it can actually branch to (past) labels. 2. Add ldrex, strex instructions. 3. Allow implicit offset 0, for example: ldr r1, [r2] Danny Milosavljevic (3): arm-asm: Implement branch to

[Tinycc-devel] [PATCH 3/3] arm-asm: Allow implicit offset 0 in input of asm_single_data_transfer_opcode

--- arm-asm.c | 18 +++--- 1 file changed, 11 insertions(+), 7 deletions(-) diff --git a/arm-asm.c b/arm-asm.c index 5b64fa6..0f7340c 100644 --- a/arm-asm.c +++ b/arm-asm.c @@ -992,15 +992,19 @@ static void asm_single_data_transfer_opcode(TCCState *s1, int token)