On Wed, 15 Feb 2006, DJ Delorie wrote: > I hope I can stick with my cmp/jmp model and manage them myself still, > though, because there's a LOT of patterns in m32c where the set of > flags affected depends on which alternative you select, and most > patterns affect the flags in some (usually nonorthagonal) way.
Unless I'm delirious (it's way past bedtime) I see a m32c port and it's cc0-free. Is there a problem? > Or is gcc going to start putting things between the cmp and jmp? Yes. At least reload wants to do that. The choice a port has is to either have cc-free reload insns (like i386) or keep the cc setter and user combined at least until after reload (cbranch, but you don't have to use the cbranchM4 name; you can do the combination to a cbranch-type insn in the CC user). Not my idea, so it's probably sane. :-) brgds, H-P PS. There may be other choices, but none that caught my attention.
