> AFAIK mingw-w64 uses callbacks to reclaim TLS memory. In the first case, upon
> destruction of the static object there were 5 blocks of memory unfreed; and
> in the second case there were 6. If we say there was no memory leak in case
> 1, then there must be in case 2, IMO.
I've tried this my
于 2014/1/17 星期五 6:45, Edscott Wilson 写道:
> I've used plugins fairly recently. No problem porting from Linux to
> Windows. Just compile the plugin as a dll and make sure you avoid C++
> name mangling.
>
>
You mean now we can build mingw(64) gcc with --enable-plugin smoothly?
--
Best Regards,
xu
Additional information:
Another example attached.
On line #54 there is an #if directive. If I put an #if 0 there, the function
ThreadProc() would get directly called - hence would run in the same thread
with main() - and I got the following result:
E:\Desktop>g++ test2.cpp -static -std=c++11
E
I'm quite sure it is due to exceptions. Memory leaks did not occure if those
two try...catch'es were in the same thread or no rethrow_exception() was used.
Best regards.
2014-01-17
lh_mouse
-
发
I've used plugins fairly recently. No problem porting from Linux to
Windows. Just compile the plugin as a dll and make sure you avoid C++ name
mangling.
2014/1/16 xunxun
> 于 2014/1/16 星期四 22:13, Иван Иванов 写道:
>
> Hello! Is it possible to develop and use GCC plugins with MinGW-w64 on
> windows
2014/1/16 Jan Blok
> Hi,
>
> I'm trying to crosscompile robovm library (from robovm.org) on Linux to a
> windows dll.
> All small dlls and test work/run great on windows, but compiling basically
> LLVM to a dll seems too much for the linker.
> The linker crashes immediately with core dump, as see
Hello
lh_mouse schrieb am 18:38 Donnerstag, 16.Januar 2014:
> I got memory leaks in this code. Hope someone would help.
> Minimal sample code attached.
> Compiled with g++ test.cpp -std=c++11 -static, then attached with OllyDbg, bp
> malloc, calloc, realloc, free. There > were 2 or 3 blocks of
Hi,
I'm trying to crosscompile robovm library (from robovm.org) on Linux to a
windows dll.
All small dlls and test work/run great on windows, but compiling basically
LLVM to a dll seems too much for the linker.
The linker crashes immediately with core dump, as seen below.
Steps I took are explain
Hi guys:
I got memory leaks in this code. Hope someone would help.
Minimal sample code attached.
Compiled with g++ test.cpp -std=c++11 -static, then attached with OllyDbg, bp
malloc, calloc, realloc, free. There were 2 or 3 blocks of memory that were not
freed upon termination.
gcc -v:
Thread mo
2014/1/16 Ruben Van Boxem
> 2014/1/16 Abir Basak
>
>> > Long time ago we add possibility to build Clang into mingw-builds
>> scripts.
>> > Now we want to provide Clang builds for mingw-w64 toolchains.
>> >
>> > There are two possibilities that we can do:
>> > *1. *Include clang builds into toolc
于 2014/1/16 星期四 22:13, Иван Иванов 写道:
Hello! Is it possible to develop and use GCC plugins with MinGW-w64 on
windows? Are there any MinGW-w64 binaries available that supports GCC
plugins? I tried googling for it, but couldn't find any.
Long long time ago, I ported DragonEgg plugin to
2014/1/16 Иван Иванов :
> Hello! Is it possible to develop and use GCC plugins with MinGW-w64 on
> windows? Are there any MinGW-w64 binaries available that supports GCC
> plugins? I tried googling for it, but couldn't find any.
I haven't used plugins pretty much for windows. I know it is possible
Hello! Is it possible to develop and use GCC plugins with MinGW-w64 on windows?
Are there any MinGW-w64 binaries available that supports GCC plugins? I tried
googling for it, but couldn't find any.
--
CenturyLink Cloud: Th
> As a side question, what does Clang development have to do with MinGW64?
> Aren't these actually competing projects?
Only if you take a narrow or literal view of what MinGW-w64 is. I
guess the name dates back to when the only open source toolchain worth
using was GCC. Good technology is worth p
Hello everyone,
I try to build Mingw w64 on Linux (ubuntu 12.04 64bits) with GCC 4.8.1
and pthread library.
I follow the instruction of the documentation but I have a problem when
I build libgomp:
make[1]: entrant dans le répertoire «
/mypath/build/gcc/x86_64-w64-mingw32/libgomp »
Makefile:
2014/1/16 Abir Basak
> > Long time ago we add possibility to build Clang into mingw-builds
> scripts.
> > Now we want to provide Clang builds for mingw-w64 toolchains.
> >
> > There are two possibilities that we can do:
> > *1. *Include clang builds into toolchain archive
> > *2.* Provide separat
2014/1/16 Jim Michaels
> ntstatus.h:#define STATUS_INVALID_IMAGE_FORMAT
> ((NTSTATUS)0xC07B)
>
> when I run my 64-bit exe, I get this windows error dialog box with the
> above error number saying the application cannot start in windows 64-bit.
> in 32-bit, it refuses to link due to 2 library
On Thu, Jan 16, 2014, wynfi...@gmail.com wrote:
> When you say specify the bin/directory, I suppose you mean
> /opt/windows_32/bin
>
> because if you cp wget.exe to cygwin's /bin you'd overwrite the
> cygwin compatible wget.exe.
Yes, that's definitely an issue. However, copying to /op
Hi,
by default _WIN32 gets defined by compiler. So don't rely on WIN32,
which only gets defined in certain context (eg -std=gnu). Actually
that "WIN32" gets defined is unintended, and caused by a stupid hidden
feature of gcc/g++.
Regards,
Kai
---
ntstatus.h:#define STATUS_INVALID_IMAGE_FORMAT
((NTSTATUS)0xC07B)
when I run my 64-bit exe, I get this windows error dialog box with the above
error number saying the application cannot start in windows 64-bit.
in 32-bit, it refuses to link due to 2 library coding error2 in th
> Long time ago we add possibility to build Clang into mingw-builds scripts.
> Now we want to provide Clang builds for mingw-w64 toolchains.
>
> There are two possibilities that we can do:
> *1. *Include clang builds into toolchain archive
> *2.* Provide separate builds of GCC+Clang
>
> I have a qu
21 matches
Mail list logo
