>>>>> Joel Sherrill writes:
Joel> FAIL: gcc.target/powerpc/405-mullhw-1.c scan-assembler mullhw
Joel> Are those things which would be expected to fail on a vanilla
Joel> 603e target without networking or disk?
Joel> Is this another category of tests to avoid somehow?
405-mullhw-1.c is invoked with -mcpu=405 and directly scans the
assembly language output -- does not try to create an object file or run
an executable. If that fails, you should check if the RTEMS configuration
somehow is inhibiting generation of the mullhwX instruction and
TARGET_MULHW flag.
David
