I should add: make the type, the new mode, the testcases etc. entirely target-specific; target-independent GCC should not need to know or care about the specifics of this type. It's bad enough target-independent GCC knowing about HImode, SImode, DImode and TImode outside default target hook implementations for targets that use those modes. And is there anything wrong with the existing PDImode name?
(It's not wrong to provide a PDImode-support file for libgcc in libgcc/config/, say, to be used by any targets that want to use such a type, but I think it's best kept separate from the main libgcc2.c and libgcc2.h. And you won't get the PDImode changes into upstream glibc's soft-fp.h, which dictates defining things in sfp-machine.h just as is done for TImode types - the TImode soft-fp files are local to GCC.) -- Joseph S. Myers jos...@codesourcery.com
