On 09/11/2019 13:46, Michael Van Canneyt wrote:
It's never enough:
http://www.muppetlabs.com/~breadbox/software/tiny/teensy.html
Michael.
That level of byte-counting is just plain insanity, even for me! Still,
when it comes to byte-counting, I did do something similar in my first
ever patch
On Sat, 9 Nov 2019, Bart via fpc-devel wrote:
On Sat, Nov 9, 2019 at 9:08 AM Michael Van Canneyt
wrote:
That is why I decided to keep it: the mode of sysutils is known and will
never change. A user is supposed to take this into account.
OK.
This error was confirmed as a compiler bug.
Op 2019-11-08 om 23:37 schreef J. Gareth Moreton:
It is a good point. With my C++ programs, I tend to compile with
everything statically linked and self-contained, since it tends to be
smaller than a dynamically-linked program plus the redistributable
combined (and the risk of "DLL Hell"
On 09/11/2019 17:40, Michael Van Canneyt wrote:
> I have extensively argued before why I think the testsuite is completely
> unsuitable for testing single unit functionality, I will not repeat my
> arguments again.
We can add testsuite makefile targets that only run the tests under
units, or even
On Sat, 9 Nov 2019, Jonas Maebe wrote:
On 09/11/2019 17:40, Michael Van Canneyt wrote:
I have extensively argued before why I think the testsuite is completely
unsuitable for testing single unit functionality, I will not repeat my
arguments again.
We can add testsuite makefile targets that
On 09/11/2019 13:29, Michael Van Canneyt wrote:
> When testing I converted the tests to the format suitable for my rtl
> testsuite, so they are run whenever I run that testsuite.
They're even more useful if they can be run by anyone, and are
automatically used during the nightly testsuite run.
On Sat, 9 Nov 2019, Marco van de Voort wrote:
Seeking to reduce binary size (without sacrificing speed) and make as
many optimisations as possible may be a fool's errand because the
returns don't justify the costs, but I personally enjoy the challenge
and puzzle-solving element of it. I
On Sat, 9 Nov 2019, Jonas Maebe wrote:
On 09/11/2019 14:43, Michael Van Canneyt wrote:
Let me know what you need extra to be able to run them with the compiler
testsuite.
Do you know which tests were copied from the existing testsuite at some
point? E.g. utrwsync.pp is derived from an old
On 09/11/2019 14:43, Michael Van Canneyt wrote:
>
> Let me know what you need extra to be able to run them with the compiler
> testsuite.
Do you know which tests were copied from the existing testsuite at some
point? E.g. utrwsync.pp is derived from an old (buggy) version of
Am 09.11.19 um 18:19 schrieb Michael Van Canneyt:
On Sat, 9 Nov 2019, Jonas Maebe wrote:
On 09/11/2019 17:40, Michael Van Canneyt wrote:
I have extensively argued before why I think the testsuite is completely
unsuitable for testing single unit functionality, I will not repeat my
arguments
On 09/11/2019 18:19, Michael Van Canneyt wrote:
>
> Running the testsuite (even part of it) requires too much preparation
> and takes too much time.
For testing RTL units, all that would be required is
a) compile the RTL
b) cd tests
c) make TEST_FPC=fpc tests_all -j 4 (or e.g. make TEST_FPC=fpc
> By the way, what is your 'particular CPU'? If it's not Intel-based,
amd zen 1. gen - the same x86_64. Not much help for testing on other platforms.
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
On Sat, 9 Nov 2019, J. Gareth Moreton wrote:
Competitions aside, there are times where space is a premium, whether it be
from distributing an application on a DVD, bandwidth or data limits (even
some first world countries are still on dial-up in places, or are otherwise
monopolised by a
On Fri, 8 Nov 2019, Bart via fpc-devel wrote:
1.
Minor issue.
Defining the ranges TByteBitIndex will confuse users if they define a
constant array with that range and then compile their program in
either mode fpc or mode tp.
I have something like:
const
Expected: array[TIntegerBitIndex] of
Op 2019-11-09 om 02:24 schreef Marģers . via fpc-devel:
3) it changes code location (code cross page boundaries). For my particular cpu there are 64 byte code page. If loop can fit in it, speed is twice as it overlaps even one byte over page boundary. Jumping forward is ok (as expected code
On Sat, 9 Nov 2019, Jonas Maebe wrote:
On 09/11/2019 13:29, Michael Van Canneyt wrote:
When testing I converted the tests to the format suitable for my rtl
testsuite, so they are run whenever I run that testsuite.
They're even more useful if they can be run by anyone, and are
automatically
Competitions aside, there are times where space is a premium, whether it
be from distributing an application on a DVD, bandwidth or data limits
(even some first world countries are still on dial-up in places, or are
otherwise monopolised by a single, bad-quality provider), the smaller
capacity
Am 09.11.19 um 17:40 schrieb Michael Van Canneyt:
On Sat, 9 Nov 2019, Jonas Maebe wrote:
On 09/11/2019 14:43, Michael Van Canneyt wrote:
Let me know what you need extra to be able to run them with the compiler
testsuite.
Do you know which tests were copied from the existing testsuite at
Am 09.11.19 um 18:08 schrieb Michael Van Canneyt:
On Sat, 9 Nov 2019, Florian Klämpfl wrote:
We don't need custom-formatted reports for the testsuite, just exit
codes from individual test programs. It seems we can easily create
those
by simply creating programs that include individual
Op 2019-11-09 om 18:28 schreef Jonas Maebe:
That's why I proposed to add support for running only the tests specific
to the RTL and/or specific units.
A tagging system for tests in the .pp tests might be the best?
Occasionally some central admin would have to be updated (automatically)
and
Am 09.11.19 um 20:02 schrieb Michael Van Canneyt:
On Sat, 9 Nov 2019, Florian Klämpfl wrote:
What matters is we have the tests.
Yes. But I see no point in having the rtl tests cluttered to different
locations.
Exactly.
My solution is WAY superior to yours in this respect.
I have
On Sat, 9 Nov 2019, Jonas Maebe wrote:
I definitely want to help to integrate the tests somehow in the daily
testrun, but I will not use the slow testsuite.
With parallel compilation, it will be barely slower.
home:~/rtl> time retest Classes > out
3.400u 0.628s 0:04.02 100.0%0+0k
Am 09.11.19 um 20:26 schrieb Michael Van Canneyt:
On Sat, 9 Nov 2019, Florian Klämpfl wrote:
Am 09.11.19 um 20:02 schrieb Michael Van Canneyt:
On Sat, 9 Nov 2019, Florian Klämpfl wrote:
What matters is we have the tests.
Yes. But I see no point in having the rtl tests cluttered to
On Sat, Nov 9, 2019 at 9:08 AM Michael Van Canneyt
wrote:
> That is why I decided to keep it: the mode of sysutils is known and will
> never change. A user is supposed to take this into account.
OK.
> This error was confirmed as a compiler bug. It also disappears if you remove
> the inline
On 09/11/2019 15:14, Michael Van Canneyt wrote:
On Sat, 9 Nov 2019, J. Gareth Moreton wrote:
Competitions aside, there are times where space is a premium, whether
it be from distributing an application on a DVD, bandwidth or data
limits (even some first world countries are still on dial-up
J. Gareth Moreton schrieb am Sa., 9. Nov. 2019,
16:20:
>
> On 09/11/2019 15:14, Michael Van Canneyt wrote:
> >
> >
> > On Sat, 9 Nov 2019, J. Gareth Moreton wrote:
> >
> >> Competitions aside, there are times where space is a premium, whether
> >> it be from distributing an application on a DVD,
On Sat, 9 Nov 2019, J. Gareth Moreton wrote:
I tend to think more size gains can be obtained from more aggressive
smartlinking.
The smartlinking is sometimes disabled by the way code is written.
To give an example, pas2js has a switch to convert published to public
sections. As a result,
On Sat, 9 Nov 2019, Florian Klämpfl wrote:
We don't need custom-formatted reports for the testsuite, just exit
codes from individual test programs. It seems we can easily create those
by simply creating programs that include individual units. The punit
unit can be moved to tests/tstunits when
On 09/11/2019 20:17, Michael Van Canneyt wrote:
>
>
> On Sat, 9 Nov 2019, Jonas Maebe wrote:
>
>>> I definitely want to help to integrate the tests somehow in the daily
>>> testrun, but I will not use the slow testsuite.
>>
>> With parallel compilation, it will be barely slower.
>
>
Op 2019-11-09 om 18:29 schreef Florian Klämpfl:
And you don't call this unix only docompile.sh not cumbersome with the
compiler parameters in some configuration file?
I definitely want to help to integrate the tests somehow in the daily
testrun, but I will not use the slow testsuite.
On Sat, 9 Nov 2019, Florian Klämpfl wrote:
Am 09.11.19 um 20:02 schrieb Michael Van Canneyt:
On Sat, 9 Nov 2019, Florian Klämpfl wrote:
What matters is we have the tests.
Yes. But I see no point in having the rtl tests cluttered to different
locations.
Exactly.
My solution is WAY
Is there anything I should do to aid testing the jump optimisations, or
is there anything else that needs cleaning up?
Unfortunately there are "TODO" comments in some of the "condition_in"
functions because I don't know enough about that particular platform to
ensure correctness, but it is
On Sat, 9 Nov 2019, Florian Klämpfl wrote:
What matters is we have the tests.
Yes. But I see no point in having the rtl tests cluttered to different
locations.
Exactly.
My solution is WAY superior to yours in this respect.
I have exactly 1 application which I open in lazarus.
I can
Florian Klämpfl schrieb am Sa., 9. Nov. 2019,
20:45:
> Am 09.11.19 um 20:26 schrieb Michael Van Canneyt:
> >
> >
> > On Sat, 9 Nov 2019, Florian Klämpfl wrote:
> >
> >> Am 09.11.19 um 20:02 schrieb Michael Van Canneyt:
> >>>
> >>>
> >>> On Sat, 9 Nov 2019, Florian Klämpfl wrote:
> >>>
> >
On 09/11/2019 20:17, Michael Van Canneyt wrote:
> home:~/fpc> time make clean all PP=ppcx64-3.0.4 > out
> /usr/bin/ld: warning: x86_64/bin/x86_64-linux/link.res contains output
> sections; did you forget -T?
> 119.139u 11.763s 1:47.32 121.9% 0+0k 179800+1292024io 2pf+0w
>
> home:~/fpc> time make
Does the smart linker strip out LCL components that are not used, or
must everything that's registered in a package or unit be included?
Granted, since forms are being read from a resource file, I doubt it can
really be tied into the compiler that closely.
Gareth aka. Kit
On 09/11/2019
36 matches
Mail list logo
