Peter Paluch writes: > Package: gcc > Version: 1:2.95.2-13 > Severity: wishlist > > I would be very glad to see PGCC packages included in Debian. After all, > there already is a huge amount of packages for programming and development > in Debian (what makes Debian a perfect platform for software development), > so why not include also the PGCC? It's probably not so unstable, and it may > even help the PGCC project to grow up and mature.
I don't see a good reason to include pgcc in Debian. Currently I see the following disadvantages: - Just another compiler in the distribution. We currently have gcc-2.7.2.3, which we still need for 2.0 kernels, we have 2.95.3 as our standard compiler. We need to include egcs-1.1.2, if 2.2 and 2.4 kernels really need it, and 3.0 will be included as the next standard compiler. - pgcc would be the only compiler generating incompatible code for the standard build architecture i386-linux. - in previous discussions on debian-devel, the pgcc mandators never posted any concrete data how much better pgcc would perform (For current comparisions, please compare with the gcc HEAD branch). I intend to close this report unless there are other arguments. (What could work: submit a .dpatch to the current gcc2.95/gcc2.97, which is included in the source package, but never applied by default, and commit you on maintaining this patch. So everybody could build gcc with this patch applied. However I am unsure, who gets an advantage from this procedure instead of building pgcc on its own).

