On Thu, Jul 8, 2010 at 12:08 PM, Dave Korn <dave.korn.cyg...@gmail.com> wrote: >> GCC 4.5.x branch and the 4.6.x branch ABI changed for win64, I'm trying >> to avoid breaking user's self-built packages, so 4.5.0 and earlier is >> out of the question. The current 4.3.4 is too old for mingw-w64. > > Going with 4.5.1 seems the simplest solution. > > I'm slightly astonished though! How on earth did you manage to swing > permission to put an ABI-breaking backwardly-incompatible change on a release > branch?
4.5.x ABI and 4.6.x ABI are what differ, not 4.5.0 and 4.5.1. There's no point in making the first shipped compiler have an ABI that's already been changed. Hence 4.6.
