Hi,
I just had time to see how tcc behaves with callgrind (a valgrind tool) on
Fedora.
1) Install required tools
$ sudo dnf install graphviz valgrind kcachegrind
2) run tcc on top of callgrind and collect results.
$ valgrind --tool=callgrind ./tcc -c -I include tccgen.c
3) See res
David Martens about exsymtab in 2015:
http://lists.nongnu.org/archive/html/tinycc-devel/2015-05/msg00057.html
Currently exsymtab development is done (I think)
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinf
> Gosh, and you even put the exsymtab stuff into [mob] now. Without discussion
http://lists.nongnu.org/archive/html/tinycc-devel/2015-05/threads.html
(David Martens)
> don't think [mob] is working for you
> Sigh. Will decide somewhen next week I guess.
Very interesting. Who are deciders?
> You
2010 actually, for 2.4.37.10.
https://lwn.net/Articles/403650/
But yes, the jump in size and complexity from 2.4 to 2.6 is quite dramatic.
-Original Message-
From: Tinycc-devel
[mailto:tinycc-devel-bounces+michael=theessentialexchange@nongnu.org] On
Behalf Of Sergey Korshunoff
Sent
Hi,
On Sun, 17 Apr 2016, Michael Matz wrote:
Can try to extract this
Sorry, reading a comment: no op now (a patch attached)
This is just silly. Put
#define __builtin_expect(a,b) (a)
anywhere and you're done. No need for support in the compiler.
Argh! And now you put in this thing into
Hi,
On Sat, 16 Apr 2016, Sergey Korshunoff wrote:
Can try to extract this
Sorry, reading a comment: no op now (a patch attached)
This is just silly. Put
#define __builtin_expect(a,b) (a)
anywhere and you're done. No need for support in the compiler.
Ciao,
Michael.
Hi,
On Sat, 16 Apr 2016, u-tcc-u...@aetey.se wrote:
So, the implementation of __clear_cache (and only it!) needs to be
provided by tcc itself, but only when compiling with pcc. I.e. some
file
__clear_cache() or the lack of it is not pcc-specific at all, actually
it is gcc-specific by defin
Hi,
On Sat, 16 Apr 2016, Vladimir Vissoultchev wrote:
Ok, so the portable way is to loop the string and call `toupper`
probably inside the #ifdef?
Something like that. Of course that breaks when e.g. the strings are
utf-8 encoded. I simply wouldn't bother to do that portably right now.
Ot
Hi,
On Fri, 15 Apr 2016, Christian Jullien wrote:
I wonder if s.o ever tried to compile tcc with gcc and then use
kcachegrind on some big project compiled with tcc to see what tcc areas
can/must be optimized?
Yes, I did in the past. Not surprisingly it's malloc/free overhead and
character
> improve hash performance
A question: how to convert a exsymtab code related to define_pish() change.
A snipped of the old code (before above patch) attached.
define_push_old.snippet
Description: Binary data
___
Tinycc-devel mailing list
Tinycc-devel@
Hi,
Just comitted the patch to mob. Before that fixed the failing test and split
the patch in two so that the allocators could easily be reversed if problems
crop up.
I also set up travis continuous integration so my dev (and mob) branch
automatically reports on https://github.com/wqweto/tinycc t
On Sun, Apr 17, 2016 at 02:15:43PM +0300, Sergey Korshunoff wrote:
> > snapshots http://pcc.ludd.ltu.se/ftp/pub
> Thanks
>
> > Regrettably, pcc with disabled gcc compatibility does not compile tcc
> > (breaks on tcclib1.c).
>
> No problem with CC=pcc on [mob] and ARCH=i386
> libtcc1.c is compile
> snapshots http://pcc.ludd.ltu.se/ftp/pub
Thanks
> Regrettably, pcc with disabled gcc compatibility does not compile tcc (breaks
> on tcclib1.c).
No problem with CC=pcc on [mob] and ARCH=i386
libtcc1.c is compiled by tcc even if CC="pcc -disable-gcc-compat"
I can assume we speek about compilin
Hello Sergey,
On Sun, Apr 17, 2016 at 11:52:12AM +0300, Sergey Korshunoff wrote:
> Comparing pcc and pcc 1.2.0.DEVEL 20141206:
...
(apparently you mean "tcc and pcc")
These are independent projects with different design goals,
so they are going to have different limitations and strong points.
>> * pcc is a nice compiler: small, classic design, some optimizations
>> and checks, some original
>> ideas.
> +1
u-tcc-uepj, Is there a git repository of the pcc?
Comparing pcc and pcc 1.2.0.DEVEL 20141206:
1) pcc don't have __linux macro defined
2) a test program (with strays)
#include
int ma
15 matches
Mail list logo
