Hi TinyCC follower.
The current branch is a release candidate for TinyCC 0.9.28 since some month.
From the active people here, only grischka has the rights to make a release,
and I suggest, that we should help him to be comfortable to make a release by:
* more testing
* add only minimal fixes
/i386-linux-gnu/libcurses.soOn my xubuntu, the installed package is: libncurses-dev:i386 I used the example from "Writing Programs with NCURSES"(ncurses-intro.pdf) in the section "Using the library"Am 06.01.24, 13:53 schrieb grischka via Tinycc-devel :
On 06.01.2024 01:10, D
via Tinycc-devel :
On 06.01.2024 01:10, Detlef Riekenberg via Tinycc-devel wrote:
>
> Of course, there might be more issues in 0.9.28rc
> As example, "i386-tcc" on a x86_64 linux machine
> is missing additional search dirs:
Can we see the o
Hi Aurélie TissonThanks for your report.This was fixed at least more than 52 month ago.(I tried tcc 0.9.27+git20200815.62c30a4a,and that version works without issues)Others have also already tested your exampleals also discovered, that this is fixed.Currently, we have a tcc 0.9.28rc and
Am 15.01.24, 08:27 schrieb Brad Robinson via Tinycc-devel :> Just wondering if there are any plans to add support for utf8 (aka u8"string")> and utf16 (aka u"string") string literals in tcc?I also would like this c11 feature to be supportedand I have an old patch to detect thisbut it is not used
Am 15.01.24, 08:57 schrieb Mathias Widman :> I am new to the list so forgive my lack of knowledge of previous questions.Welcome here, Mathias.> I wonder if there are any plans on incorporating/supporting SIMD intrinsics.Which target processor / which intrinsics?intrinsics
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
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
>> 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
We have the tinycc 0.9.28 release canditate for a long time,but still no release.All people here can help grischka to be more confident to make a release.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
Welcome to tinycc and thanks for your recent riscv-changes @Ekaitz.All are waiting for a release and should avoid to add new features.Since your changes are only for riscv targets, i hope, that the changes would not delay the release of tcc 0.9.28 even further,(but only @grischka can make a
Am 31.03.24, 17:45 schrieb 837806295 via Tinycc-devel :Hi 837806295.Using a name for communication is better...> Hello!> Report a Bug about Parsing #ifdef, #ifndef and #else Line.Your intention to write a bug rebort is good,but your example is not vaild C code.From your example:> { > #ifndef Test
Hi César Welcome to TinyCC> Basically, what I need is just a C compiler.> Written in C. A good C compiler. It depends, what you define as a 'good' compiler.TinyCC is a single pass compiler and very good at compilation speed.The code created by TinyCC is often remarkable slower,compared to code
Hi @ekaitz>> For adding new features, a message to the mailing list is always better.> I wasn't sure about that so I just decided to send the changes. > You are right.It is always a good idea,but very important during the rc phase.> Now that we are in the mailing list, > I have some support for
Hi grischka.When do you plan to do a release?What can we, to help you?-- Regards ... Detlef
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Am 24.03.24, 16:53 schrieb "codif...@gmail.com" :> "release" personally I've just tracked git master (or is it main these days?) > and pull roughly monthly, > maybe I just got lucky, but its always "just works" (tm)Yes, using the mob branch is good (most of the time),but the tcc version in various
> How do we feel about the lack of __VA_OPT__?I would delay that after the release.@grischka, your ping for a release.-- Regards ... Detlef
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
tcc should be as small an simple as possible,so i vote against any colored output.For colored output, i pipe the output through a script.I use "colormake.pl" here and to reduce typing, i use a link with the shorter name "cmpl".Oh, i changed my "colormake.pl" to recognice tcc / *tcc.-- Regards ...
18 matches
Mail list logo