Jim,
I was corrected by Ken Chapman, that to download PicoBlaze, one has to acknowledge they have read and agree to the "use restrictions."
Peter and I had a chat about this subject: any IP that is specific to a device (that would be Lattice, Altera, or Xilinx) is optimized for their device, and would be suitably poor in any other technology. So, if you want something that is technology agnostic, you would end up buying something from a 3rd party, and paying them (or your own team) to make different versions of it that are all code and cycle identical, and technology independent (? I am presuming this is possible: it may not be!).
So, that is why if I designing an ASIC I buy an 'XYZ' (insert ARM, PPC, MIPS, or whatever you like here) core: I know what I am getting, I can get it for 130nm, 90nm, 65nm, etc.; I can emulate it in an FPGA (if I have to); I can ask questions and get answers.
If I want to get the most for my money, I decide whose chip I am going to use, and I use their tools and IP. I "hope" that my c code can be compiled and run on another vendor if I decide I must switch to another vendor (for whatever reason).
The one time I had a major project of many uP's on many pcb's, and we changed from Intel to Motorola (gasp!), it was not trivial to port all the code (written in c) from one to the other platform....I wouldn't want to do it today, either. But at least, it was possible, and it could be done (and we did it successfully).
As for support of old code:
formatting link
Xilinx offers the last best and debugged version of each code build, for free, to customers who need to maintain an old design.
Of course, we can not provide the old Windoze version, but a trip to the Saturday Flea Market at Foothill (or equivalent) will get you all the old Microsquat stuff you want. As well, we no longer have rights to distribute nor support certain old schematic tools, or simulators, but as customers, you have the rights to use the old versions to fix old stuff (they have archives, too).
So, be my guest, pick a processor: pick the one that you will get the most use from, be the most efficient to implement in the technology targeted, make the best use of code already written, and will be maintainable for the lifetime of your product lines.
Austin