On Tue, Mar 11, 2014 at 6:18 PM, Marco van de Voort wrote:
> In our previous episode, Marcos Douglas said:
>> >> http://svn.freepascal.org/svn/fpc/branches/fixes_2_6 ?
>> >
>> > from memory .. tags/release_2_6_4
>>
>> Yes, thanks... but for updates we will continue using /branches/fixes_2_6 ?
>
>
On 3/11/2014 2:31 PM, Mattias Gaertner wrote:
In the light of FPC 2.6.4 being released today, what is the word on
using the 2.6.4 compiler with Lazarus 1.2?
Next Lazarus release will be built with it. That's probably 1.2.2.
Ok, now if that would be working again on the newer Mac OS X, but then I
On Tue, 11 Mar 2014 13:56:18 -0700
Ralf Quint wrote:
> On 3/4/2014 6:52 AM, Mattias Gaertner wrote:
> > The Lazarus team is glad to announce the release of Lazarus 1.2.
> >
> > This release was built with fpc 2.6.2.
> >
> In the light of FPC 2.6.4 being released today, what is the word on
> usin
In our previous episode, Marcos Douglas said:
> >> http://svn.freepascal.org/svn/fpc/branches/fixes_2_6 ?
> >
> > from memory .. tags/release_2_6_4
>
> Yes, thanks... but for updates we will continue using /branches/fixes_2_6 ?
yes. Version will be updated to 2.6.5 tomorrow.
But note since 2.6.
On Tue, Mar 11, 2014 at 5:57 PM, Marco van de Voort wrote:
> In our previous episode, Marcos Douglas said:
>> Where is the branch for download,
>> http://svn.freepascal.org/svn/fpc/branches/fixes_2_6 ?
>
> from memory .. tags/release_2_6_4
Yes, thanks... but for updates we will continue using /b
In our previous episode, Marcos Douglas said:
> Where is the branch for download,
> http://svn.freepascal.org/svn/fpc/branches/fixes_2_6 ?
from memory .. tags/release_2_6_4
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepasc
On 3/4/2014 6:52 AM, Mattias Gaertner wrote:
The Lazarus team is glad to announce the release of Lazarus 1.2.
This release was built with fpc 2.6.2.
In the light of FPC 2.6.4 being released today, what is the word on
using the 2.6.4 compiler with Lazarus 1.2?
(I am currently running my main se
On Tue, Mar 11, 2014 at 4:36 PM, Marco van de Voort wrote:
>
> Finally, FPC 2.6.4 has landed. FPC 2.6.4 is an update to 2.6.2 and 2.6.0 that
> contains most library progress over the 2.6.2. It will probably conclude the
> 2.6.x branch.
>
> Building is still in progress and some formats (deb) and t
Yay! Thank you guys.
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
2014-03-11 16:36 GMT-03:00 Marco van de Voort :
>
> Finally, FPC 2.6.4 has landed. FPC 2.6.4 is an update to 2.6.2 and 2.6.0
> that
> contains most library progress over the 2.6.2. It will probably conclude
> the
> 2.6.x branch.
>
> Building is still in progress and some formats (deb) and targets
Finally, FPC 2.6.4 has landed. FPC 2.6.4 is an update to 2.6.2 and 2.6.0 that
contains most library progress over the 2.6.2. It will probably conclude the
2.6.x branch.
Building is still in progress and some formats (deb) and targets might
not be available yet.
Changes that may break backwards
I know. As a counterpoint to my initial statement, Windows CE defaults
to building into ARM. That's why I hedged. :)
My point is, while only Windows Phone 8 *enforces* Thumb, others,
specifically iOS, Android, bada, all *default* to Thumb. Won't be long
until CPU builders wake up to that and s
Am 11.03.2014 15:12, schrieb Vsevolod Alekseyev:
Windows CE is not modern :)
Windows Phone 8 is not based on Windows CE, but on Windows NT. Also
Windows CE never had problems with non-Thumb code...
Regards,
Sven
___
fpc-devel maillist - fpc-devel@l
From where I sit, it beats patching a huge codebase that I know next to
nothing about. Besides, my job is made easier by avoiding the gnarliest
parts of the FPC RTL. No objects, no dynarrays, no RTTI, no exceptions,
no Unicode. That's how easy (read: old-fashioned, almost Turbo
Pascal-style) *m
For the record, all modern mobile SDKs that I know of use Thumb as the
default instruction set for native code compilation. And with Thumb-2 on
ARMv7 cores, the performance is on par between ARM and Thumb. The
original Thumb, years ago, was compiled to ARM, but not any longer.
Thumb may even b
Not on Windows. The calling convention of DLL functions (including API) and
callbacks is mandated by the platform indeed, but within your app it's a
free-for-all. Just ask Delphi with their funky register-based convention :)
> Normally, the ABI is defined by the OS vendor and not the tool chain
How interesting. Where's you hear this?
> Supposedly the interrupt code of the OS does not save and restore the
"running in Thumb mode" flag. So you are out of luck with non-Thumb code.
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://l
Michael Schnell wrote:
On 03/11/2014 03:10 AM, Vsevolod Alekseyev wrote:
I've tried several assembly sequences that would branch and switch
mode; they all would cause an exception.
Supposedly the interrupt code of the OS does not save and restore the
"running in Thumb mode" flag. So you are o
On 03/11/2014 08:53 AM, Sven Barth wrote:
That Windows isn't normal here should have been shown by the MinGW ABI
problem already :P
In Windows the correct ABI is not even published.
E.g. we all do know that (with normal X86 32 bit windows) The Microsoft
C compilers rely on the area to be be us
On 03/11/2014 03:13 AM, Vsevolod Alekseyev wrote:
The calling convention of C code *is* largely driven by the platform's
toolchain.
So you mean "the meaning of 'STDCALL' needs to adhere to the toolchain
used"
This of course is true (but not that closely depending on the OS itself)
OTOH the o
On 03/11/2014 03:10 AM, Vsevolod Alekseyev wrote:
I've tried several assembly sequences that would branch and switch
mode; they all would cause an exception.
Supposedly the interrupt code of the OS does not save and restore the
"running in Thumb mode" flag. So you are out of luck with non-Thum
Am 11.03.2014 07:48, schrieb Florian Klämpfl:
On 11. März 2014 03:13:18 MEZ, Vsevolod Alekseyev wrote:
It's not all assembly. The fake FPC RTL was written in C because I
wanted it
to be portable (Intel/ARM/Thumb at the very least, at some point MIPS
too).
The calling convention of C code *is*
Am 11.03.2014 07:50, schrieb Florian Klämpfl:
On 11. März 2014 03:10:08 MEZ, Vsevolod Alekseyev .
Anyways, as far as I can see, the biggest hurdle to implementing a
Windows
Phone target in FPC would be the ARM dialect. It's strictly Thumb-2
with
hardware floating point and hard-float ABI.
This
23 matches
Mail list logo
