Hi, With the help of Janis, the ppc405 tests can now detect when the scan assembler won't pass. I moved on to do the same with the ppc440 tests and noticed that there is no cpp predefine to know when you are compiled for a ppc440.
$ powerpc-rtems4.10-gcc -mcpu=440 -E - -dM </dev/null >440 $ powerpc-rtems4.10-gcc -mcpu=405 -E - -dM </dev/null >405 $ diff 405 440 34d33 < #define __PPC405__ 1 It is easy enough to add a cpp predefine but is this the right thing to do? Is there any alternative? The unfortunate thing is that I think these tests are really ensuring that MASK_DLMZB is used as expected. If this is right, then shouldn't there be a cpp predefine similar to __NO_LWSYNC__ for dlmzb? And the tests use that rather than testing for a specific CPU model? And then should there be tests for the other CPU models which have this feature to ensure the -mcpu=[405fp|440fp|464|464fp] also do the right thing? I don't see why 2 of the 6 CPU models have this test. I am happy to take care of this if I just know the right path. Thanks. -- Joel Sherrill, Ph.D. Director of Research & Development joel.sherr...@oarcorp.com On-Line Applications Research Ask me about RTEMS: a free RTOS Huntsville AL 35805 Support Available (256) 722-9985
