[Top][All Lists]

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

Re: [Tinycc-devel] Tiny c availability

From: Christian Jullien
Subject: Re: [Tinycc-devel] Tiny c availability
Date: Thu, 9 Jul 2020 17:22:48 +0200

I added USES file which list known projects working with tcc. To be 

-----Original Message-----
From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange.fr@nongnu.org] On 
Behalf Of Steffen Nurpmeso
Sent: Thursday, July 09, 2020 15:47
To: tinycc-devel@nongnu.org
Subject: Re: [Tinycc-devel] Tiny c availability

arnold@skeeve.com wrote in
 |> arnold@skeeve.com wrote in
 |> <202007090906.069964j4023321@freefriends.org>:
 |>|I compile gawk with it all the time and gawk passes its test suite.
 |>|I use it mainly when I want a quick build to test something.
 |>|My big wish for tcc is that it'd produce debug info for use with GDB.
 |Steffen Nurpmeso <steffen@sdaoden.eu> wrote:
 |> Oh please not as a regular built-in option.
 |Why not? Why shouldn't I get fast compile with the option for debug
 |info also? Why must I be forced to fall back to GCC just to debug?

The changeset for backtracing is surprisingly small, but lots of
conditionals etc.  I do not know.  I never use a debugger.  All
printf() here.  tcc is still very, very fast.

|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Tinycc-devel mailing list

reply via email to

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