On 10.03.2014 03:45, Karoly Balogh (Charlie/SGR) wrote:
Hi,
On Sat, 22 Feb 2014, Sven Barth wrote:
With revision 26849 which I just committed a few minutes ago an imporant
milestone was reached for reviving the M68k port: the cross compiled compiler
is now not only able to compile a program,
On 10.03.2014 00:20, Vsevolod Alekseyev wrote:
Enter Windows Phone 8. In order to have a good debugging experience, you need
to build the code both for Intel x86 (for the emulator), and for ARM (for
devices). The flavor of ARM that WP8 uses is strictly Thumb-2, with hard
floating point and
On 03/10/2014 12:20 AM, Vsevolod Alekseyev wrote:
WP8 uses is strictly Thumb-2, with hard floating point and hard-float calling
convention (i. e. parameters in floating point registers).
Why/how does the OS dictate how in a user program the functions are
called ? (In fact in an ASM program
Hi,
On Mon, 10 Mar 2014, Sven Barth wrote:
Well, today on IRC you mentioned Atari too many times for an Amiga guy's
taste, so I couldn't resist...
Once is already too many? :P
Yes! :)
http://charlie.amigaspirit.hu/screenshots/uae/UAE-FPC-m68k-2.7.1-FirstEver.png
:)
Congrats! So
Am 10.03.2014 12:04, schrieb Karoly Balogh (Charlie/SGR):
Hi,
On Mon, 10 Mar 2014, Sven Barth wrote:
Well, today on IRC you mentioned Atari too many times for an Amiga guy's
taste, so I couldn't resist...
Once is already too many? :P
Yes! :)
:P
And besides, it was a decade old wish of me
Please elaborate in how far the calling convention does not match. This
might be a bug in FPC then
I'm talking about my replacement for the subset of the Pascal RTL. The
calling code assumes the Pascal convention, the implementation is in C. They
don't match on Intel.
i386 FPC has support for
Am 10.03.2014 13:52, schrieb Vsevolod Alekseyev:
Please elaborate in how far the calling convention does not match. This
might be a bug in FPC then
I'm talking about my replacement for the subset of the Pascal RTL. The
calling code assumes the Pascal convention, the implementation is in C.
Hi.
I use heaptrc and cwstring units in Linux.
If memoryleak occurs and program ends, then i get SIGSEGV in cwstring.pp:481
(iconv call)
because cwstring unit is finalized before heaptrc.
#1 iconv(optimized out, 0x7fffd738, 0x7fffd760, 0x7fffd730,
0x7fffd748) at iconv.c:53
#2
On 10 Mar 2014, at 16:13, Petr Kristan wrote:
If memoryleak occurs and program ends, then i get SIGSEGV in
cwstring.pp:481 (iconv call)
because cwstring unit is finalized before heaptrc.
If you use -gh, then heaptrc will be the first unit of the uses clause
and will be finalized after
10.03.2014 19:40, Jonas Maebe пишет:
On 10 Mar 2014, at 16:13, Petr Kristan wrote:
If memoryleak occurs and program ends, then i get SIGSEGV in cwstring.pp:481
(iconv call)
because cwstring unit is finalized before heaptrc.
If you use -gh, then heaptrc will be the first unit of the uses
On 10 Mar 2014, at 17:17, Sergei Gorelkin wrote:
10.03.2014 19:40, Jonas Maebe пишет:
On 10 Mar 2014, at 16:13, Petr Kristan wrote:
If memoryleak occurs and program ends, then i get SIGSEGV in
cwstring.pp:481 (iconv call)
because cwstring unit is finalized before heaptrc.
If you
Am 10.03.2014 02:36, schrieb Vsevolod Alekseyev:
It looks to me like development by drive-by patch has been going for quite a
while. I smell burnout...
We are waiting for a patch set for an easy to use WP8 compiler :)
___
fpc-devel maillist -
On 03/10/2014 03:03 PM, Sven Barth wrote:
Am 10.03.2014 13:52, schrieb Vsevolod Alekseyev:
I don't now remember the exact history behind each
replacement, but here they are.
- DGROUP is a problem; I comment it out
- So is ASSUME
- The syntax of SEGMENT is different
- Instead of .386p
Let me reintroduce back each of the problematic lines and see what happens.
Uncommenting DGROUP causes the following error message:
error A2214: GROUP directive not allowed with /coff option
I don't know what does DGROUP do, but Nikolay knows :) It's a DOS remnant,
and makes no sense in Win32.
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* largely driven by the platform's
toolchain.
Why/how does the OS dictate how in a user program the
15 matches
Mail list logo
