Re: [Tinycc-devel] FWD: Can't build for riscv64 or arm64

[Christian Jullien]

This post does not solves missing types but be aware that more recent gcc 
versions changed the names to [unsigned] __int128

Hence
__uint128_t => unsigned __int128
__int128_t  => __int128

Old names remain for compatibility and are *strictly* equivalent.
For example, starting with gcc v11.x, sdt::numeric_limits and typeinfo (C++) 
return the same exact values for old and new names and are totally 
interchangeable.

IMHO, if tcc implements one day 128 bits, it should be with new name (+ a 
typedef for older names).

C. 

-----Original Message-----
From: tinycc-devel-bounces+eligis=orange.fr@nongnu.org 
[mailto:tinycc-devel-bounces+eligis=orange.fr@nongnu.org] On Behalf Of Detlef 
Riekenberg
Sent: Friday, February 03, 2023 19:11
To: tinycc-devel@nongnu.org
Subject: *** SPAM *** Re: [Tinycc-devel] FWD: Can't build for riscv64 or arm64

Hi Sagar

tcc has no support for 128bit int types.
__uint128_t
__int128_t


You might try with a replacement (typedef struct with 2x uint64)
This should be at least enough for the structsize for the typedef in signal.h,
but acessing the elements in the code you try to compile will propably fail

-- 
Bye bye ... Detlef


> When building lib/bt-exe.c , it imports ../tccrun.c
> Which throws error
> 
> /usr/include/bits/signal.h:14: error ';' expected (got "__uint128_t"
> 
> /usr/include/bits/signal.h is as follows:
> 
> typedef struct {
>     __uint128_t vregs[32];
>     unsigned int fpsr;
>     unsigned int fpcr;



_______________________________________________
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel