•
•
•
•
What is DaniWeb IT Discussion Community?
You're currently browsing the Assembly section within the Software Development category of DaniWeb, a massive community of 392,007 software developers, web developers, Internet marketers, and tech gurus who are all enthusiastic about making contacts, networking, and learning from each other. In fact, there are 4,187 IT professionals currently interacting right now! Registration is free, only takes a minute and lets you enjoy all of the interactive features of the site.
Please support our Assembly advertiser:
Views: 926 | Replies: 0
 |
•
•
Join Date: Aug 2007
Posts: 2
Reputation: 
Rep Power: 0
Solved Threads: 0
Newbie Poster
64 bit programming issue ... Hi,
I am currently porting 64 bit application with C and Assembly code (x86-64) from Linux to windows.
I am using Microsoft C-Compiler 2005 and Yasm for compiling C and assembly code respectively.
I have modified the assembly files as per the 64-bit ABI specification for windows and i do get expected results when i use “RTCs” flag which is meant for stack pointer verification. This flag also requires optimization flags to be turned off.
The problem starts when i dont use the “RTCs” (which is the case in release version) it tries to access initial locations (0×04a0) of memory in C-code.
I suspect that it has something to do with calling convention mismatch when control gets transferred from assembly to C-function.
Any help in this regard would be highly appreciated.
With warm regards,
KEDAR
I am currently porting 64 bit application with C and Assembly code (x86-64) from Linux to windows.
I am using Microsoft C-Compiler 2005 and Yasm for compiling C and assembly code respectively.
I have modified the assembly files as per the 64-bit ABI specification for windows and i do get expected results when i use “RTCs” flag which is meant for stack pointer verification. This flag also requires optimization flags to be turned off.
The problem starts when i dont use the “RTCs” (which is the case in release version) it tries to access initial locations (0×04a0) of memory in C-code.
I suspect that it has something to do with calling convention mismatch when control gets transferred from assembly to C-function.
Any help in this regard would be highly appreciated.
With warm regards,
KEDAR
|
•
•
•
•
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
•
•
•
•
•
•
•
•
DaniWeb Assembly Marketplace
Linear Mode
•
•
•
•
api apple asm assembly x86 programming hla demo blogger blogging c c++ ccna cocoa code coding competition compiler compilers computer debugging developer development errors evaluation framework gdata google high-performance innovation java languages linerider mcse microsystems networking news next object online open oriented planning platform practices programming python rss software step steps sun tools tutorials xml
- C++ Programming issue (C++)
- C++ programming on Fedora 5 with Eclipse but how? (C++)
- Nasm for 64 bit programming (Assembly)
- General Programming issue (Computer Science and Software Design)
Other Threads in the Assembly Forum
- Previous Thread: Assembly Language Resources
- Next Thread: help
