On 03/26/2013 03:44 PM, Iain Buclaw wrote: > This is why there are gdc-4.7, gdc-4.8 branches. They are there to be > guaranteed to work with those gcc releases. There won't be any support for > multiple gcc versions in one source.
I think you've misunderstood me (although I don't think I expressed myself well, so mea culpa). I recognize the existence and purpose of the gcc-4.7 and gcc-4.8 branches and it makes perfect sense to organize things that way. It's just that some remarks make it seem like new versions of the frontend will only be guaranteed to work on 4.9. That seems to me to be unfortunate, although I understand how the difficulties of adapting new versions of the the frontend to GCC may make it inevitable. I remember you discussing some work that would help to make it possible to just pull in new versions of the frontend without any large re-working -- IIRC replacing some direct calls to the DMD backend with a more generic API that would be backend-agnostic -- and if there's in any case going to be some period of instability due to switching to 4.9, I wonder if now might be the moment to do that work?
