[cfe-dev] Mingw-w64 runtime failure when using clang 7.0 on Windows targeting mingw-w64/gcc

[Edward Diener via cfe-dev]

On 11/21/2018 3:37 PM, Edward Diener via cfe-dev wrote:
> In testing the Boost Parameter library using clang-7.0 32-bit targeting 
> mingw-w64/gcc on Windows I ran into a mingw-w64 runtime failure when 
> attempting to run the final command-line executable program. The full 
> message is:
> 
> Mingw-w64 runtime failure:
>    Unknown pseudo relocation protocol version 65536.
> 
> This application has requested the Runtime to terminate it in an unusual 
> way. Please contact the application's support team for more information.
> 
> Using clang-6.0 32-bit targeting mingw-w64/gcc on Windows the 
> command-line executable program runs correctly. Using mingw-w64/gcc-8.1, 
> which is the backend I am using with clang-7.0, on Windows the 
> command-line program runs correctly. Nor does it matter what 
> mingw-w64/gcc version I use as the backend for clang-7.0 the runtime 
> failure persists.
> 
> There is a bug report at https://sourceforge.net/p/mingw-w64/bugs/769/, 
> which points to a bug report at
> https://sourceware.org/bugzilla/show_bug.cgi?id=23872, with a fix at
> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=73af69e74974eaa155eec89867e3ccc77ab39f6d, 
> 
> which it was suggested to me on the mingw-w64 mailing list might fix the 
> problem I encountered. However after I applied the "fix" to the various 
> linker scripts of the mingw-w64/gcc backend I am using with clang-7.0 
> the runtime failure still persisted.
> 
> I can give detailed instructions for duplicating this problem using the 
> latest Boost 1.68 version, the source code, and the command-lines to 
> build the executable which fails. But before I go to that length in this 
> message I wanted first to ask if this problem has been encountered 
> already among clang developers or via bug reports, and is therefore a 
> known issue with clang-7.0 on Windows targeting mingw-w64/gcc ?

I have created a bug report for this clang-7.0 problem at 
https://bugs.llvm.org/show_bug.cgi?id=39754.