Re: Re : PPC440, GCC-4.1.1 supposes cr{2,3,4} saved but the hard real time kernel doesn't...

2006-11-28 Thread Ian Lance Taylor
Etienne Lorrain <[EMAIL PROTECTED]> writes: > powerpc-eabi-gcc -Wall -W -O2 -g -fno-strict-aliasing -ffunction-sections > -fdata-sections -fno-schedule-insns -std=gnu99 -fcall-used-cr2 > -fcall-used-cr3 -fcall-used-cr4 -Xassembler -mregnames ... *.c > > ../net/src/net_dbg.c:668: error: Attempt

Re : PPC440, GCC-4.1.1 supposes cr{2,3,4} saved but the hard real time kernel doesn't...

2006-11-28 Thread Etienne Lorrain
@gcc.gnu.org Envoyé le : Mardi, 28 Novembre 2006, 15h26mn 27s Objet : Re: PPC440, GCC-4.1.1 supposes cr{2,3,4} saved but the hard real time kernel doesn't... Etienne Lorrain <[EMAIL PROTECTED]> writes: > My problem is quite simple, the PPC has few conditions registers and some are &

Re: PPC440, GCC-4.1.1 supposes cr{2,3,4} saved but the hard real time kernel doesn't...

2006-11-28 Thread Ian Lance Taylor
Etienne Lorrain <[EMAIL PROTECTED]> writes: > My problem is quite simple, the PPC has few conditions registers and some are > assumed to be saved over function calls (in my test case NU_Sleep()), but the > hard real time kernel do not save those (partial flags) registers. > This behaviour is per

PPC440, GCC-4.1.1 supposes cr{2,3,4} saved but the hard real time kernel doesn't...

2006-11-28 Thread Etienne Lorrain
Hello, My problem is quite simple, the PPC has few conditions registers and some are assumed to be saved over function calls (in my test case NU_Sleep()), but the hard real time kernel do not save those (partial flags) registers. This behaviour is perfectly documented in gcc-4.1.1/gcc/config/rs6