Matt Thomas <[EMAIL PROTECTED]> writes: > Over the past several weeks, I've revamped the VAX backend: > > - fixed various bugs > - improved 64bit move, add, subtract code. > - added patterns for ffs, bswap16, bswap32, sync_lock_test_and_set, > and > sync_lock_release > - modified it to generate PIC code. > - fixed the dwarf2 output so it is readonly in shared libraries. > - moved the constraints from vax.h to constraints.md > - moved predicates to predicates.md > - added several peephole and peephole2 patterns > > So the last major change to make the VAX backend completely modern is to > remove the need for "HAVE_cc0". However, even instructions that modify > the CC don't always changes all the CC bits; some instructions preserve > certain bits. I'd like to do this but currently it's above my level of > gcc expertise. > > Should the above be submitted as one megapatch? Or as a dozen or two > smaller patches?
Smaller patches are generally better. However, you are a VAX backend maintainer, and not too many people care about the VAX these days. So you can handle patches to the VAX backend code as you see fit (as long as they get sent to gcc-patches somehow). A mega patch is OK. Any patches to code outside of gcc/config/vax should be sent as smaller patches. (I have no useful comment on your other issues. Thanks for doing this work.) Ian
