Doubly Linked List in Assembly Language
- Thread starter venom555
- Start date
s0ap
Regular Member
- Sep 23, 2008
- 218
- 847
You have to provide more details if you want someone to help. What platform? What is the data type of the list?
If this is your first time working with linked lists I would start in C as the memory can be a brain fuzzer, and dereferencing NULL is a non-starter.
If this is your first time working with linked lists I would start in C as the memory can be a brain fuzzer, and dereferencing NULL is a non-starter.
kellermanrivero
Newbie
- Apr 19, 2013
- 3
- 0
I think is better a code double link in C and use GCC to generate Assembly without optimizations. After that study assembly result to make more human coded.
Why would you do that in assembly language? why punish yourself like that.
It really depends on the architecture of the processor you are deploying it on, are you using MIPS or X86?
is your processor big endian or little endian?
I agree with JP1016 compile C++ code to assembly language from the command line and see what the compiler does
then make your optimizations after the code is compiled.
It really depends on the architecture of the processor you are deploying it on, are you using MIPS or X86?
is your processor big endian or little endian?
I agree with JP1016 compile C++ code to assembly language from the command line and see what the compiler does
then make your optimizations after the code is compiled.
sm754
Registered Member
- Mar 21, 2012
- 93
- 38
I haven't used assembly in a while, but in MASM a linked list struct would look something like this (assuming 32-bit):
Then, to use the structure, you'd need to allocate memory from the heap in whatever way is most convenient, and set the "prev" and "next" pointers to the addresses of the respective link structs in the list.
Code:
link STRUCT
prev DWORD 0 ; pointer to previous link
next DWORD 0 ; pointer to next link
; whatever data you need to store here
link ENDThen, to use the structure, you'd need to allocate memory from the heap in whatever way is most convenient, and set the "prev" and "next" pointers to the addresses of the respective link structs in the list.
