Jonas Maebe wrote:
On 20 Nov 2009, at 18:08, Paul Ishenin wrote:
I have attached compiler gprof output of compiler itself. Using output I was
able to find and improve(?) 3 functions I found in output.
Did you benchmark whether this changed code is indeed faster and whether it
makes
In our previous episode, Inoussa OUEDRAOGO said:
> >> You can help improve the upcoming 2.4.0 release by downloading and
> >> testing this release. If you want you can report what you have done here:
> >> http://wiki.freepascal.org/Testers_2.4.0
> >
> > How is one supposed to reported the results o
On 22 Nov 2009, at 15:31, Paul Ishenin wrote:
> Jonas Maebe wrote:
>> On 20 Nov 2009, at 18:08, Paul Ishenin wrote:
>>
>> Did you benchmark whether this changed code is indeed faster and whether it
>> makes any difference at all for the compiler? Changing working code because
>> it /might/ bec
hi,
while adding sourceline info to the Lazarus disassembler output I ran
into the DEBUGSTART_, DEBUGINFO_ and
DEBUGEND_ symbols.
What I wonder is why DEBUGSTART and DEBUGEND are reported as functions,
while DEBUGINFO is reported as datavariable (fpc 2.2.4, stabs).
(gdb) ptype DEBUGSTART_UNI
On 22 Nov 2009, at 18:43, Marc Weustink wrote:
> while adding sourceline info to the Lazarus disassembler output I ran into
> the DEBUGSTART_, DEBUGINFO_ and
> DEBUGEND_ symbols.
> What I wonder is why DEBUGSTART and DEBUGEND are reported as functions, while
> DEBUGINFO is reported as datavari
Jonas Maebe wrote:
On 22 Nov 2009, at 18:43, Marc Weustink wrote:
while adding sourceline info to the Lazarus disassembler output I ran into the
DEBUGSTART_, DEBUGINFO_ and DEBUGEND_
symbols.
What I wonder is why DEBUGSTART and DEBUGEND are reported as functions, while
DEBUGINFO is reported
Hello,
I managed to install the latest svn FPC and use it with Lazarus.
Trying to compile VirtualTreeView component I get many errors about type
conversions, like:
Error: Illegal type conversion: "Set Of TVTColumnOption" to "DWord"
for line
Dummy := LongWord(FOptions);
Error: Illegal ty
On 22 Nov 2009, at 22:59, Juha Manninen wrote:
> Seems that integers and sets can't be casted to each other any more.
No, the size of sets in Delphi and TP mode has been made Delphi/TP compatible
by default, i.o.w.: {$packsets 1} is now the default for Delphi and TP mode. To
convert a non-ordi
On 22 Nov 2009, at 23:06, Jonas Maebe wrote:
> the size of sets in Delphi and TP mode has been made Delphi/TP compatible by
> default, i.o.w.: {$packsets 1}
Sorry, that should read {$packset 1}. And the remedy is to either change the
typecast, or (and this is backward compatible) add {$packset
