On 11/21/18, Edward Diener wrote:
> On 11/20/2018 10:50 PM, Ozkan Sezer wrote:
>> On 11/21/18, Edward Diener wrote:
>>> I am building an application using clang-7.0 targeting gcc with
>>> mingw-64/gcc-8.1 as the backend. The application shows no errors
>>> compiling or linking. When I try to debu
On 11/21/18, Edward Diener wrote:
> On 11/20/2018 10:50 PM, Ozkan Sezer wrote:
>> On 11/21/18, Edward Diener wrote:
>>> I am building an application using clang-7.0 targeting gcc with
>>> mingw-64/gcc-8.1 as the backend. The application shows no errors
>>> compiling or linking. When I try to debu
On 11/20/2018 10:50 PM, Ozkan Sezer wrote:
On 11/21/18, Edward Diener wrote:
I am building an application using clang-7.0 targeting gcc with
mingw-64/gcc-8.1 as the backend. The application shows no errors
compiling or linking. When I try to debug the application I get the
messages from within
On 11/21/18, Edward Diener wrote:
> I am building an application using clang-7.0 targeting gcc with
> mingw-64/gcc-8.1 as the backend. The application shows no errors
> compiling or linking. When I try to debug the application I get the
> messages from within gdb:
>
> [New Thread 6432.0x1b38]
> Mi
I am building an application using clang-7.0 targeting gcc with
mingw-64/gcc-8.1 as the backend. The application shows no errors
compiling or linking. When I try to debug the application I get the
messages from within gdb:
[New Thread 6432.0x1b38]
Mingw-w64 runtime failure:
Unknown pseudo re
