Hi -- ---- Ryan Mallon <ryan@xxxxxxxxxxxxxxxx> wrote: > Martin Guy wrote: > > Hi! > > You probably know I have some patches to gcc that fix Maverick code > > generation and even add a flag -mieee to disable all the > > non-strictly-conformant instructions. > > I'm now going mad trying to nail the last rare Maverick bug and am > > seeing such crazy results that I must consider there being something > > dodgy about my particular hardware or kernel. > > > > Briefly, would someone with a Cirrus EP93XX chip running an EABI OS > > run the attached program and tell me whether for them too it gives > > different results at each run, then let me know together with their > > silicon revision number (5th and 6th chars of the second line of text > > on the chip housing). > > > > Here's what I am seeing: > > > > Every test program I try works perfectly except for paranoia, which > > gives different results each time I run it, from failure to segfault > > to illegal instruction to infinite loops. > > Hi Martin, > > I'm running the precompiled binary (I don't have your toolchain > installed). My kernel is a modified 2.6.20 with EABI support. > > Linux version 2.6.20-snapper (andre@tutira) (gcc version 4.3.2 (Sourcery > G++ Lite 2008q3-72) ) #297 Mon Feb 2 15:17:07 NZDT 2009 > CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177 > > My chip id is: EP9315-IBZ, EFWAE2AP0620 > > When I run the binary, I consistently get a crash on an illegal > instruction. Running in gdb I get: Same for me, but I don't have gdb or patched gcc available to go further. TS-7250 (ep9302), also on NFS root, 2.6.28.4 sparsemem (a WIP ...) CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=40007177 Linux version 2.6.28.4-m (ccm@ccm-amd64) (gcc version 4.1.1 (CodeSourcery ARM Sourcery G++ 2006q3-26)) #13 PREEMPT Wed 11 23:25:22 EST 2009 regards, ...... Charlie > > (gdb) r > Starting program: /paranoia > > Program received signal SIGILL, Illegal instruction. > 0x0000950c in main () >