On the other hand one shouldn't expect any hacks to be necessary for GCC 2.9.5/6. It might Just Work.
Bill. On 18 August 2011 07:53, Jason <ja...@njkfrudils.plus.com> wrote: > Hi > > Some thoughts > > The gcc farm only goes back to gcc-4.1 in general > gcc-3.1 was the first gcc to support x86_64 > Slackware 8.1 released 2002 had gcc-2.95 but slackware 9.0 released 2003 had > gcc-3.2 , and slackware was(not now) generally behind the curve > gcc-2.96 was a redhat patch to 2.95 , gcc 3.0 and 3.1 were hardly used due to > stability issues(actually bad programming practice , pointer aliasing > violating the C standard) > > One issue with MPIR on doing simplifications is that often you have to work > around existing hacks/workarounds on old compilers/arches/oses , so on a good > proportion of previous simplifications I left it halfway done as the effort > was > too much. I either need to generalize all these hacks or dump 'em and for the > old hacks dump 'em. I can write a new assembler function in the time it takes > to work around (and test when possible!) a hack , and I guess thats more > inportant > > Jason > > > On Thursday 18 August 2011 00:32:04 Bill Hart wrote: >> Many machines only have 2.96. The reason is because of its stability I >> think. >> >> On 17 August 2011 19:38, Jason <ja...@njkfrudils.plus.com> wrote: >> > On Wednesday 17 August 2011 16:08:37 jason wrote: >> >> Hi I've removed the define >> >> HAVE_HOST_CPU_FAMILY_x86_64 >> >> as it was not used anywhere , and I plan to get rid of the other >> >> define HAVE_HOST_CPU_* >> >> >> >> There is one case left here >> >> /build.vc10/cfg.h:# define HAVE_HOST_CPU_FAMILY_x86_64 1 >> >> >> >> I assume this can be removed as well >> >> >> >> Jason >> > >> > Hi >> > >> > I plan to make the earliest version of GCC supported 3.4 , this is the >> > earliest version that we test on , and assuming this I can clean up some >> > old workarounds in the code. Any objections? >> > >> > Jason >> > >> > -- >> > You received this message because you are subscribed to the Google Groups >> > "mpir-devel" group. To post to this group, send email to >> > mpir-devel@googlegroups.com. To unsubscribe from this group, send email >> > to mpir-devel+unsubscr...@googlegroups.com. For more options, visit this >> > group at http://groups.google.com/group/mpir-devel?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "mpir-devel" group. > To post to this group, send email to mpir-devel@googlegroups.com. > To unsubscribe from this group, send email to > mpir-devel+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/mpir-devel?hl=en. > > -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to mpir-devel@googlegroups.com. To unsubscribe from this group, send email to mpir-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en.
