Hi Sophie,
Thanks for the question.
The chief blocker for updating gollvm to later versions of LLVM trunk is dealing with LLVM's
opaque pointer migration in the gollvm
bridge source code. The bridge (which maps from gofrontend's IR to LLVM IR) was written prior to opaque pointers and it assumes that given an LLVM type T, it can always ask for what T points to (which is exactly what you can't do under the opaque pointer model).
Fixing this is not a huge amounts of work (maybe a few weeks? hard to tell) but the folks with the highest level of gollvm expertise have been tied up with other more important priorities.
So to answer your question, no plans in the short term. I could provide some limited help (pointers etc) but I don't have the time to make a significant investment in this at the moment.
Thanks, Than