So, no response here, other than a few (brief) comments on irc.
It's hard to know how to advocate for a patch when I'm not sure what the
objections are. But it seems likely that that biggest areas of concern
aren't the changes to the inline asm, but the files I'm deleting from
\intrinsc\.
W
Hmm, not necessarily a gcc bug. It might be simply that the dll
itself has dependencies to other dll-files.
Try to check by dependency-walker tool, or via the objdump tool, what
other DLL-files might be referenced.
Most likely it is an issue about libgcc.dll file.
Regards,
Kai
-
On 08/06/2013 05:12 PM, Michael Cronenworth wrote:
> I'm attempting to build a project that uses both PostgreSQL (libpq.dll) and
> CuRL
> (libcurl.dll), but I have run into a issue when both are linked into the same
> executable. I have a simple test case that I am attaching that demonstrates
> t
Hello niXman!
On Wed, Aug 7, 2013 at 2:30 PM, niXman wrote:
> 2013/8/7 K. Frank
>
>> Do I anticipate any issues using libcurl with mingw-w64? If so, what
>> should I look out for and how might I deal with it?
>
> No, libcurl is easy to build with mingw-w64.
Thanks for the confirmation.
>> Seco
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
abort() is a msvcr(t) function, and it does not throw an exception, just
prints a message and terminates your program.
Well, actually, it does call SIGABRT handler before terminating. But
that's in-program, and isn't known to the debugger. And most lib
2013/8/8 LRN :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 07.08.2013 22:37, Michael Cronenworth wrote:
>> On 08/07/2013 01:35 PM, LRN wrote:
>>> What does "might" mean there? Like, you may get a dependency, or you may
>>> not? It doesn't sound like you ALWAYS get a dependency.
>>> Pre
