Thanks for the link. The issue you see is caused by
register-clobbering of r10/r11 etc. Those are callee saved-registers.
So you need to save them too.
By adding following lines (without the +):
GSYM_PREFIX`'ecm_redc3:
push%rbp# Push registers
As I understand it, the word "toolchain"
is the word referring to the gcc tools, msys and all
that usually runs with mingw.
Can someone here give me the url for the
64 bit equivalent of 32 bit
mingw-get-inst-20110530.exe
file?
-
On Tue, Feb 21, 2012 at 5:02 AM, Me Myself and I
wrote:
>
> As I understand it, the word "toolchain"
> is the word referring to the gcc tools, msys and all
> that usually runs with mingw.
no. It's just the compiler, linker, eventually a debugger, + some
files (like the win32 headers and import li
On Wed, Feb 22, 2012 at 4:02 AM, Vincent Torri wrote:
> On Tue, Feb 21, 2012 at 5:02 AM, Me Myself and I wrote:
>
>> Can someone here give me the url for the
>> 64 bit equivalent of 32 bit
>>
>> mingw-get-inst-20110530.exe
>>
>> file?
>
> There is no such installer for the mingw-w64 project (at lea
Thank you for giving me suggestions of things to try. I have tried pushing and
popping r8,r9,r10,r11,rcx, and rdx. However, this did not change the behavior
of the program.
I looked at the documentation you mentioned and they seem to say that r10/r11
should be considered volatile (ie, destroy
Hi,
Just a simple question. I just install Win64 cross compiler on Linux
(x86_64)
and there are two gcc which seems identical:
bin/x86_64-w64-mingw32-gcc
x86_64-w64-mingw32/bin/gcc
at least, file size is equal; and "diff" can't tell the difference.
So, what's the difference between these two s
Hi KC,
I think this question was raised already many times about it. The binaries in
/bin are user-executables and you should use only this one.
That those binaries in your /bin directory have prefix
'x86_64-w64-mingw32-', indicates that you are using a cross-compiler.
The binaries in /x86_64-w6
