[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Tinycc-devel] github

From: Christian Jullien
Subject: Re: [Tinycc-devel] github
Date: Sun, 19 Apr 2020 07:11:43 +0200

For sure I would like to have a CI.
I personally test about every commit on Windows x86/x64, Linux arm32/arm64 and 
a little bit less often on Linux x64/Alpine x64.
I definitively would like to test Linux/rsicv64 too but I lack access to a 
machine having this cpu.

GitHub has another advantage, it perhaps more stable than current repository.

Why don't you setup a pure mirror on GitHub just for CI and without the 
possibility to commit on it? This mirror will synchronize, say, every 4 hours 
and launch non-regression tests for all supported os/system.


-----Original Message-----
From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=address@hidden] On 
Behalf Of Robert Hölzl
Sent: Saturday, April 18, 2020 21:05
To: address@hidden
Subject: [Tinycc-devel] github

hey guys,

TinyCC is great because it supports so much configurations (3 OSes, even 
more CPU archs).

But the downside is, that nobody can ensure that his change wont break 
any of these configurations.
(Probably most of us are testing only on their own PC, which is one OS 
with probably x86-64).

How about a CI?

I would be happy to add the corresponding scripts, so that at least 
windows (x86 and x64), linux (x64) and macos (x64) are tested.
I did not investigate yet, but it could be even possible to utlitze qemu 
to test all cpu archs (not only x86, x64).

But to make this work I need the repo to be homed at github or gitlab.
It seems that on github there is already an organization "TinyCC".
Bit it seems not to be supported by the core devs.
In fact the guy which created this repo even started some CI scripts.

@the core devs: Please point our your thoughts.
Are you interested in a CI (even it might need a switch to 


Tinycc-devel mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]