On Friday 12 May 2017 20:28:54 Fred van Stappen wrote:
>
> > accidentally not working -XX, with active smartlinking it was reduced to
> > 26072 bytes.
>
> Do you mean that you have a trick to do smartlinking working for libraries
> ?
>
No, the first time I presented the benchmark results in the
> BTW, the mergesort benchmark binary also was 177576 bytes with accidentally
> not working -XX, with active smartlinking it was reduced to 26072 bytes.
Hello Martin.
In a other topic, they talk about to use : -k--gc-sections.
Fre;D
On Friday 12 May 2017 06:06:41 Martin Schreiber wrote:
> On Friday 12 May 2017 00:07:09 Fred van Stappen wrote:
> > > It is logical that the libraries are bigger because the libraries
> > > contain all named code
> >
> > Huh, :
> >
> >
> > program prognude ;
> > begin
> > end.
> > => 26.9 k
> >
>
On Friday 12 May 2017 03:44:30 Edson H wrote:
>
> I'm currently developing a Pascal Compiler
Do you refer to
https://github.com/t-edson/PicPas
? Looks good! Does the IDE have integrated debug capabilities?
I worked many years with PIC16xxx. Programming always was done in assembler.
Martin
On Friday 12 May 2017 13:52:36 Fred van Stappen wrote:
> > BTW, the mergesort benchmark binary also was 177576 bytes with
> > accidentally not working -XX, with active smartlinking it was reduced to
> > 26072 bytes.
>
> Hello Martin.
>
> In a other topic, they talk about to use : -k--gc-sections.
On Friday 12 May 2017 13:52:36 Fred van Stappen wrote:
> > BTW, the mergesort benchmark binary also was 177576 bytes with
> > accidentally not working -XX, with active smartlinking it was reduced to
> > 26072 bytes.
>
> Hello Martin.
>
> In a other topic, they talk about to use : -k--gc-sections.
Yes. That's my compiler. It has only basic features. The idea is to integrate
the PIC12F and PIC18F series, a simulator, a burning software and a debug
integrated. But it will be later.
By now it's a very optimized compiler. It's better than some other commercial
products.
7 matches
Mail list logo
