Danny Backx wrote:
> Apparently the compiler on my system has hickups. I hadn't reinstalled a
> fresh cegcc.dll for a looong time; apparently I didn't do a full rebuild
> + reinstall since the last upgrade of my Linux system.
>
> The compiler doesn't appear to cope well with the default compiler
>
Forget all that.
Apparently the compiler on my system has hickups. I hadn't reinstalled a
fresh cegcc.dll for a looong time; apparently I didn't do a full rebuild
+ reinstall since the last upgrade of my Linux system.
The compiler doesn't appear to cope well with the default compiler
options (I'v
I wasn't entirely clear. I started getting the problem I described
below, so I reverted my change, and I'm still getting the problem :-(
I had already discovered that gdb also traps this, and the way to map
these exception codes into explanations. The trouble is now to find out
why this is happeni
Danny Backx escreveu:
> This is spooky.
>
> I edited startup.c slightly, recompiled the cegcc.dll . And then,
> apparently, something went wrong. Not a single application built with
> cegcc wants to run any more, the mingw32ce stuff does still work.
>
> warning: __init_c__: initted = 1
> warnin
This is spooky.
I edited startup.c slightly, recompiled the cegcc.dll . And then,
apparently, something went wrong. Not a single application built with
cegcc wants to run any more, the mingw32ce stuff does still work.
warning: __init_c__: initted = 1
warning: "WCETRACE" not found in registry
warn
Danny Backx wrote:
> BTW, does anyone know how to trap events like these and get information
> on what went wrong ?
>
SEH is one way. Easier on eVC/MSVC since you have
__try/__catch/__finally there. With gcc you have to do it manually.
On ARM SEH is table based. Take a look at
newlib/libc/sys
Danny Backx wrote:
> dannypc: {79} arm-wince-cegcc-gcc -mfloat-abi=hard -mfpu=fpa float.c -o
> float.exe -lmmtimer
> Info: resolving _CRT_MT by linking to __imp__CRT_MT (auto-import)
>
> The executable from the last compile only prints one message. I guess
> I've created an executable that works
dannypc: {77} arm-wince-cegcc-gcc -mfloat-abi=soft -mfpu=fpa float.c -o
float.exe -lmmtimer
Info: resolving _CRT_MT by linking to __imp__CRT_MT (auto-import)
dannypc: {78} arm-wince-cegcc-gcc -mfloat-abi=hard float.c -o float.exe
-lmmtimer
float.c:1: sorry, unimplemented: -mfloat-abi=hard and VFP
d
Klaus Rechert wrote:
> Hi,
>
> i wonder how fpu-calls are handled on WinCE. AFAIK arm cpus do not have FPU
> units. Cegcc is not compiled with soft-float support, therefore i assume the
> wince kernel takes care of fpu-emulation. Should not be gcc soft-float
> support enabled by default, since i
Several bits and pieces of input.
1. The gcc manual, ARM section, says -mhard-float is the default.
2. That doesn't seem to be true, because -mhard-float is not accepted
on the compiler command line.
I wrote a very simple program to fiddle with. Compiling it with
different options gives thi
Hi,
i wonder how fpu-calls are handled on WinCE. AFAIK arm cpus do not have FPU
units. Cegcc is not compiled with soft-float support, therefore i assume the
wince kernel takes care of fpu-emulation. Should not be gcc soft-float
support enabled by default, since in general it is faster than ker
11 matches
Mail list logo
