That requires masm to compile the project.
What I actually want is to see the disassembled code from my project (as
Intel Syntax assembly code) to look at how the win32 and win64 code is
optimized and then to fine tune the pascal source.
1. The objdump ("objdump.exe" and "x86_64-win64-objdump.exe") utility
from the binutils programs works and displays the code with the -Mintel
option as Intel syntax from the "*.o" files, however when I try to see
the line numbers (objdump.exe -l ...) and source code lines (objdump.exe
-S ...) it does not put them in the right places within the disassembled
code.
As an example, I used:
objdump.exe -d -Mintel -w -l -S -EL something.o > something.disassembled
2. The fpc "-al" flag generates a nice "*.s" assembler file during
compilation, where everything is in place, except it is not Intel syntax
assembly but AT&T.
Anyone had experience with something like this (display the disassembled
code of a project unit/object_file in Intel syntax, with source code lines)?
Thanks for any help
On 8/20/2012 22:37, Sergei Gorelkin wrote:
21.08.2012 5:38, ABorka пишет:
Is there a way to see the generated ".s" assembly files as Intel
syntax instead of the AT&T one?
The -Rintel flag does not seem to work, or I am doing something wrong.
Tried command line and fpc.cfg both, on win32 and win64, latest SVN .
-R switch controls parsing assembler blocks in the code.
The output format is set with -A (e.g. -Amasm will produce Intel syntax).
Regards,
Sergei
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
