Re: [Tinycc-devel] Waiting for a release / Please delay any commits

2024-04-17 Thread Steffen Nurpmeso
Hi. tinycc-devel@nongnu.org wrote in : |>> We have the tinycc 0.9.28 release canditate for a long time, |>> but still no release | |@grischka, we need you | |>> Savannah has a buglist for tinycc: |>> [1]https://savannah.nongnu.org/bugs/?group=tinycc[/1] |>> It works for collecting issue,

[Tinycc-devel] AutoReply: Tinycc-devel Digest, Vol 251, Issue 11

2024-04-17 Thread t.b.y.taoboyu
这是来自QQ邮箱的假期自动回复邮件。你好,我最近正在休假中,无法亲自回复你的邮件。我将在假期结束后,尽快给你回复。 ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Re: [Tinycc-devel] new backend

2024-04-17 Thread Paul Moore
I want to create a lite c compiler for the HACK computer described in “the elements of computing systems” aka ‘nand to tetris’ – here, Home | nand2tetris. A fun read. I have implemented the system on an fpga and want to cross compile c code to it. It’s a 16bit

Re: [Tinycc-devel] new backend

2024-04-17 Thread Detlef Riekenberg via Tinycc-devel
Hi PaulCan you please tell me more about the new backend,which you are working on?Either here or with private mail.Thanks.> Well somewhere along the way I fixed it > when I started making gjmp and gjmp_append return sane values. Great > Are there any docs out there that describe how to write a

Re: [Tinycc-devel] Re: Waiting for a release / Please delay any commits

2024-04-17 Thread Detlef Riekenberg via Tinycc-devel
>> We have the tinycc 0.9.28 release canditate for a long time,>> but still no release@grischka, we need you>> Savannah has a buglist for tinycc:>> https://savannah.nongnu.org/bugs/?group=tinycc>> It works for collecting issue,>> but unfortunately no one works on this issue list> I did not even

Re: [Tinycc-devel] Waiting for a release / Please delay any commits

2024-04-17 Thread Detlef Riekenberg via Tinycc-devel
Hi Ekaitz>> My suggestions:>> * Please hold back any commit before the release.>> * If you think, you have an urgent change to fix an urgent bug,>> discuss it on the mailing list first.>> * Together, we decide, if we postpone the change after the release is out,>> or commit the fix before the