Pedro Alves a écrit :
> pgeorges wrote:
>> I ported this program to evc4, and I get the same type of crash. So
>> cegcc is ok, but I don't understand why this code works well with gcc
>> on x86, and why the crash only occurs with optimisation on.
>>
>
>
pgeorges a écrit :
> Hi,
>
> I port chess engines to Pocket PC ARM, and for one of them (others are
> ok), the program crashes as soon as I compile it with -O1, -O2 or -O3
> option.
> I managed to get in which functions it crashes, but as it is a complex
> program I am
Hi,
I port chess engines to Pocket PC ARM, and for one of them (others are
ok), the program crashes as soon as I compile it with -O1, -O2 or -O3
option.
I managed to get in which functions it crashes, but as it is a complex
program I am not able currently to produce small portion of code that
Danny Backx a écrit :
> On Thu, 2007-11-15 at 22:44 +, Pedro Alves wrote:
>
>> Definitely not show-stoppers.
>>
>
> I believe the one identified show-stopper has been fixed by Pedro, with
> confirmation that the fix is good.
>
> I've heard of no other show-stoppers.
>
> Also some recent
Pedro Alves a écrit :
> However, if you find that you can isolate the parts of
> the code that are critical, it may be better to use a pool
> or a special allocator for the memory management of those
> time critical allocations/objects.
>
> Cheers,
> Pedro Alves
>
>
I made some tests with malloc
At http://msdn2.microsoft.com/en-us/library/ms913056.aspx
it is stated that
"All threads initially start at THREAD_PRIORITY_NORMAL (251)."
Currently I use
CeSetThreadPriority(GetCurrentThread(), priority);
where priority is between 248 and 254 to run threads in background.
If I remember well, thi
Hi,
I ported a chess program to Pocket PC with cegcc :
http://prolinux.free.fr/scid/PPC.html
The code is in C, compiled with cegcc and the UI uses Tcl/Tk.
Pascal
Danny Backx a écrit :
> On Fri, 2007-10-12 at 09:03 +0200, Jacek M. Holeczek wrote:
>
>> Yes, I think a list of projects utilizing
Pedro Alves a écrit :
> Danny Backx escreveu:
>> On Wed, 2007-09-19 at 17:51 +0200, pgeorges wrote:
>>>> Crosswords, compiled with cegcc, runs noticably slower than compiled
>>>> with the m$ compiler. Eric House also reported this. I've not
>>>>
Danny Backx a écrit :
> On Wed, 2007-09-19 at 11:51 +0200, pgeorges wrote:
>
>>>> I ported some chess engines to Pocket PC with cegecc and noticed the
>>>> number of calculated positions per second is about 30% lower with my
>>>> ports than th
Pedro Alves a écrit :
> pgeorges wrote:
>> Hi,
>>
>> I ported some chess engines to Pocket PC with cegecc and noticed the
>> number of calculated positions per second is about 30% lower with my
>> ports than the equivalent made by other people who used Micros
Hi,
I ported some chess engines to Pocket PC with cegecc and noticed the
number of calculated positions per second is about 30% lower with my
ports than the equivalent made by other people who used Microsoft compilers.
Years ago I made some comparisons between gcc and icc under Linux and
notice
I personaly create a CAB file with the 3 cegcc DLLs incorporated to
distribute my application and ease its installation.
If there were several versions of those DLLs, packaging would be harder.
So could it be possible for those DLLs to detect on which WinCE version
they run and dynamically provi
Danny Backx a écrit :
> On Mon, 2007-09-03 at 21:01 +0200, pgeorges wrote:
>
>> HeapCompact is indeed only available with WinCE 5 and higher, so it is
>> not so important. But CreateToolhelp32Snapshot is more important, as it
>> is present since Wince 3.0, so maybe it
Danny Backx a écrit :
> HeapCompact is described on MSDN to be present on Windows CE 5 or
> higher; my device has an older WinCE. Therefore when I add HeapCompact
> to src/cegcc/importlibs/defs/coredll.def , and create a test application
> that uses it, WinCE tells me it is not a valid Pocket PC ap
14 matches
Mail list logo
