On Wed, 17 May 2017, fredvs wrote:
Michael Van Canneyt wrote
You didn't even file an official request in the bugtracker ?
Because I tried already and because I know the (rejected) answer.
Where is this bugreport ?
I was talking about earlier other requests.
Each case is always
Michael Van Canneyt wrote
>>> You didn't even file an official request in the bugtracker ?
>>
>> Because I tried already and because I know the (rejected) answer.
>
> Where is this bugreport ?
I was talking about earlier other requests.
But now, if you think that the request has a little
On Wed, 17 May 2017, fredvs wrote:
But, IMHO, if fpc uses a external linker, it is also part of the compilation
process. And each feature of the linker should be analyzed.
We are agreed on that.
Michael Van Canneyt wrote
You didn't even file an official request in the bugtracker ?
Michael Van Canneyt wrote
> On Wed, 17 May 2017, fredvs wrote:
>
>> Hello.
>>
>> OK, I see that fpc team is afraid to change something that mom-Delphi did
>> not do.
>
> This is simply not correct and a *very* unfair statement on your part.
> Mails like this will really not get you anywhere.
On Wed, 17 May 2017, fredvs wrote:
Hello.
OK, I see that fpc team is afraid to change something that mom-Delphi did
not do.
This is simply not correct and a *very* unfair statement on your part.
Mails like this will really not get you anywhere.
1. You didn't even file an official request
2017-05-17 13:32 GMT+02:00 fredvs :
>
> OK, I see that fpc team is afraid to change something that mom-Delphi did
> not do.
You don't know that. Lack of bug report / feature request on mantis, means
that the feature request doesn't exist in any formal way. Sometimes is good
Hello.
OK, I see that fpc team is afraid to change something that mom-Delphi did
not do.
So, to resume, for people who wants to smartlink their libraries, you may
use this command:
*fpc -k--gc-sections my_smartlinked_library.pas*
Fre;D
-
Many thanks ;-)
--
View this message in
On 2017-05-16 09:20, fredvs wrote:
Michael Van Canneyt wrote
On Tue, 16 May 2017, fredvs wrote:
Michael Van Canneyt wrote
What can be misunderstood about adding --gc-sections to the linker
options if -XX is used on the command-line ?
Ha, the way you present it seems to show that you did
On 2017-05-16 03:15, fredvs wrote:
noreply wrote
On 2017-05-15 04:26, fredvs wrote:
After lot of fight, there is a solution: using -*-gc-sections*.
And the question was :
/Why FPC does not provide --gc-sections to the linker with the -XX
paramer
for libraries ? (Bug ?) /
Hopefully that's
On Tue, 16 May 2017, fredvs wrote:
Michael Van Canneyt wrote
On Tue, 16 May 2017, fredvs wrote:
Michael Van Canneyt wrote
What can be misunderstood about adding --gc-sections to the linker
options if -XX is used on the command-line ?
Ha, the way you present it seems to show that you did
Marco van de Voort wrote
> In our previous episode, Michael Van Canneyt said:
>> > Does it work for all situations? I remember a bug for the rust
>> compiler
>> > that broke libraries when --gc-sections was used, because it removed
>> the
>> > metadata that rust needed to load the library. One
Michael Van Canneyt wrote
> On Tue, 16 May 2017, fredvs wrote:
>
>> Michael Van Canneyt wrote
>>> What can be misunderstood about adding --gc-sections to the linker
>>> options if -XX is used on the command-line ?
>>
>> Ha, the way you present it seems to show that you did understand it ;-)
>>
On Tue, 16 May 2017, fredvs wrote:
Michael Van Canneyt wrote
What can be misunderstood about adding --gc-sections to the linker
options if -XX is used on the command-line ?
Ha, the way you present it seems to show that you did understand it ;-)
OK, maybe is it time to add a feature
In our previous episode, Michael Van Canneyt said:
> > Does it work for all situations? I remember a bug for the rust compiler
> > that broke libraries when --gc-sections was used, because it removed the
> > metadata that rust needed to load the library. One of the fpc devs can
> > probably say
Michael Van Canneyt wrote
> What can be misunderstood about adding --gc-sections to the linker
> options if -XX is used on the command-line ?
Ha, the way you present it seems to show that you did understand it ;-)
OK, maybe is it time to add a feature request...
Fre;D
-
Many thanks
In our previous episode, fredvs said:
> Nobody uses fpc library here ?
Yes, but I don't care about size unless it is outrageous.
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
On Tue, 16 May 2017, Henry Vermaak wrote:
On Tue, May 16, 2017 at 01:15:34AM -0700, fredvs wrote:
It works for all situations, so I propose that fpc add --gc-sections
as parameter for the linker if the user has used -XX parameter to
compile a library.
Does it work for all situations? I
On Tue, May 16, 2017 at 01:15:34AM -0700, fredvs wrote:
> It works for all situations, so I propose that fpc add --gc-sections
> as parameter for the linker if the user has used -XX parameter to
> compile a library.
Does it work for all situations? I remember a bug for the rust compiler
that
On Tue, 16 May 2017, fredvs wrote:
Maciej Izak wrote
2017-05-16 10:15 GMT+02:00 fredvs
fiens@
:
It works for all situations, so I propose that fpc add --gc-sections as
parameter for the linker if the user has used -XX parameter to compile a
library.
for features requests please
Maciej Izak wrote
> 2017-05-16 10:15 GMT+02:00 fredvs
> fiens@
> :
>
>> It works for all situations, so I propose that fpc add --gc-sections as
>> parameter for the linker if the user has used -XX parameter to compile a
>> library.
>>
>
> for features requests please use
2017-05-16 10:15 GMT+02:00 fredvs :
> It works for all situations, so I propose that fpc add --gc-sections as
> parameter for the linker if the user has used -XX parameter to compile a
> library.
>
for features requests please use https://bugs.freepascal.org .
--
Best
noreply wrote
> On 2017-05-15 04:26, fredvs wrote:
>> After lot of fight, there is a solution: using -*-gc-sections*.
>>
>> And the question was :
>>
>> /Why FPC does not provide --gc-sections to the linker with the -XX
>> paramer
>> for libraries ? (Bug ?) /
>
>
> Hopefully that's all there
On Mon, 15 May 2017, nore...@z505.com wrote:
On 2017-05-15 04:19, Michael Van Canneyt wrote:
If you want to compare today, you need to add the sizes of all the C
libraries that are loaded during execution of a C program with the
size of an FPC program.
I think you'll find that the sizes of
On 2017-05-15 04:26, fredvs wrote:
After lot of fight, there is a solution: using -*-gc-sections*.
And the question was :
/Why FPC does not provide --gc-sections to the linker with the -XX
paramer
for libraries ? (Bug ?) /
Hopefully that's all there is to it, but how do you know that this
On 2017-05-15 04:19, Michael Van Canneyt wrote:
If you want to compare today, you need to add the sizes of all the C
libraries that are loaded during execution of a C program with the
size of an FPC program.
I think you'll find that the sizes of FPC programs are not so different
then.
Just
On Mon, 15 May 2017, fredvs wrote:
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
Ha, news, finally.
Huh, did you read my post ?
I did.
I responded to the statement that fpc libraries are big and "unusable".
It talk about smartlinking of libraries that does not work.
Michael Van Canneyt wrote
> On Mon, 15 May 2017, fredvs wrote:
>
>> fredvs wrote
>>> Hello.
>>>
>>> Sorry to come back with this story but there are (good) news.
>>>
>>> Using
>> *
>>> --gc-sections
>> *
>>> makes the library smartlinked.
>>>
>>> So the question is:
>>>
>>> Why FPC does not
On Mon, 15 May 2017, fredvs wrote:
fredvs wrote
Hello.
Sorry to come back with this story but there are (good) news.
Using
*
--gc-sections
*
makes the library smartlinked.
So the question is:
Why FPC does not provide
*
--gc-sections
*
to the linker with the -XX paramer for
fredvs wrote
> Hello.
>
> Sorry to come back with this story but there are (good) news.
>
> Using
*
> --gc-sections
*
> makes the library smartlinked.
>
> So the question is:
>
> Why FPC does not provide
*
> --gc-sections
*
> to the linker with the -XX paramer for libraries ? (Bug ?)
>
>
Hello.
Sorry to come back with this story but there are (good) news.
Using *--gc-sections* makes the library smartlinked.
So the question is:
Why FPC does not provide *--gc-sections* to the linker with the -XX paramer
for libraries ? (Bug ?)
Fre;D
-
Many thanks ;-)
--
View this
>>> Sorry to insist on that, but the size of fp library is very too big
>>> vs
> other libraries (C for example).
Except in the case of KOL applications where many of my KOL Dll's/Exe's
were smaller than any C/C++ tool could ever create... But KOL is window's
specific mostly. Someone ported it,
On 14.01.2017 17:18, fredvs wrote:
>>> Sorry to insist on that, but the size of fp library is very too big vs
> other libraries (C for example).
>
>> The size of FPC libraries will always(*) be bigger then e.g. C ones,
>> because in FPC the RTL is statically linked into the program/library,
>>
>> Sorry to insist on that, but the size of fp library is very too big vs
other libraries (C for example).
> The size of FPC libraries will always(*) be bigger then e.g. C ones,
> because in FPC the RTL is statically linked into the program/library,
> while C libraries link against the C runtime
>> Sorry to insist on that, but the size of fp library is very too big vs
other libraries (C for example).
> The size of FPC libraries will always(*) be bigger then e.g. C ones,
> because in FPC the RTL is statically linked into the program/library,
> while C libraries link against the C runtime
On Mon, 3 Feb 2014, Fred van Stappen wrote:
Date: Mon, 3 Feb 2014 18:30:57 +0100
From: mich...@freepascal.org
To: fpc-pascal@lists.freepascal.org
Subject: Re: [fpc-pascal] Size of program vs library ?
On Mon, 3 Feb 2014, Fred van Stappen wrote:
Hello.
Here size of nude program
If I am correct, the compiler will add the PIC by itself.
But someone of the compiler team should confirm this...
Michael.
Yep, Michael, many thanks for answer.
Sorry to insist on that, but the size of fp library is very too big vs other
libraries (C for example).
But there are huge
Am 04.02.2014 13:35, schrieb Fred van Stappen:
Sorry to insist on that, but the size of fp library is very too big vs
other libraries (C for example).
The size of FPC libraries will always(*) be bigger then e.g. C ones,
because in FPC the RTL is statically linked into the program/library,
(*) Once dynamic runtime packages are supported this might change
though...
Regards,
Sven
Ok, thanks Sven, that will be the best...
But before the triumph of fp, i will do that universal audio open source
library with fp too...
Many thanks for all of you, fp
Hello.
Here size of nude program and library compiled with fpc 2.7.1.
Why is it a so big size-difference ?
Compiled with = fpc 2.7.1 = linux 64
Compiler parameters : -MObjFPC -Scghi -CX -Os1 -Xs -XX -vewnhi -fPIC
program prognude ;
begin
end.
= 26.9 k
library libnude ;
begin
end.
= 196.3 k
On Mon, 3 Feb 2014, Fred van Stappen wrote:
Hello.
Here size of nude program and library compiled with fpc 2.7.1.
Why is it a so big size-difference ?
Compiled with = fpc 2.7.1 = linux 64
Compiler parameters : -MObjFPC -Scghi -CX -Os1 -Xs -XX -vewnhi -fPIC
I suspect PIC is to blame. This
Date: Mon, 3 Feb 2014 18:30:57 +0100
From: mich...@freepascal.org
To: fpc-pascal@lists.freepascal.org
Subject: Re: [fpc-pascal] Size of program vs library ?
On Mon, 3 Feb 2014, Fred van Stappen wrote:
Hello.
Here size of nude program and library compiled with fpc 2.7.1.
Why
41 matches
Mail list logo