| |
| |
| |
|
Page: 1 2
Comments:
<0> i think so the writer of the book put it
<1> ok.
<2> what kind of asm is that?
<0> ok thank you it should be PutLInt
<0> i wrote it wrong
<0> it is in %include "io.mac"
<0> thank you very much it took me half an hour to find the error (move/mov) thing
<0> i need a break
<0> is it logical to learn asm at age 30 ?
<3> to me it's ok.
<0> ok i will try it to learn
<4> Has anyone tried to program a PIC? Like in one of those velleman kits.
<5> join #freebasic
<4> Only x86 asm here?
<5> mainly x86, a few people do have knowledge of other langs though
<6> not only x86 here and yes i program PIC
<5> i know z80
<4> How does one learn all specific addresses on different types on procs.?
<6> reading and doing
<4> Various routines and procedures that you need to prepare the program code with.
<4> Obviously there is no logic in this these procedures, since they change from machine to machine.
<4> Logic yes, but in learning them no.
<6> look at examples, for PIC microchip have a LOT of downloads, manuals, programming software and app notes
<7> hi
<7> Why need to compile ***embly to ELF format to run instead of plain binary?
<7> Please someone tell web site that explains purpose of ELF, loader, linker, etc. to run your ***embly codes
<3> seb-, don't know much about it myself. About ELF and PE under windows (portable executable format): a first goal is to describe the layout of program in memory consisting of an executable section (.text), an uninitialized-data section (.bss) and an initialized-data section (.data). The code section is read-only and relies on the fact that the hardware provide mechanisms for detecting write-violation to this section (through exceptions
<3> ->segfault). Concerning the 2 other sections, these are given memory regions so that accesses outside these regions are detected (again through exception if I recall). Please correct me if I say wrong things.
<3> seb-, A second goal is to provide a way for modularity using libraries, the ELF and PE formats permits the declaration of function entry points of libraries which are to be accessible to programs. And conversely libraries and programs are given a way to declare the need of other libraries to work. don't know if I express myself correctly..
<7> mElo_: thanks, if i understand you correctly.. ''linking'' combines multiple data, bss and text segments into one, this involves integrating function pieces together....i don't know if that is *everything* exectuables need
<3> Even in ***embly we need to work with ELF because the environment (OS) requires it. It doesn't know about raw binary executables.
<7> mElo_: that helps...to CPU doesn't need ELF but OS needs it!?
<3> yes
<7> mElo_: if we ran our code on bare metal we wouldn't need ELF! right?
<7> (no OS)
<3> it's all constrained by the OS, for the sake of portability/interoperability, protection.
<3> indeed yes.
<8> personally i like SMURF better
<3> SMURF?
<8> it's like a blue elf
<3> ok
<7> WHAT is the diff between a 'loader' and a 'linker' ?
<8> one links, other loads
<7> phrosty: linking means to combine code but what exactly does 'loading' mean?
<7> phrosty: "load" it where?
<8> no clue
<9> elf loader i guess
<8> i'm not familiar with asm on linux
<7> edcba: loader 'creates elf files' ?
<9> no
<9> it creates process from elf files :)
<3> seb-, the loader (ld-linux.so) reads an ELF file and prepares it for running.
<7> edcba: ahh! loader is used to *RUN* programs not CREATE them right!
<7> edcba: THANKS!
<10> seb-, also relocate virtual address in memory and other functions... main purpose is that to make programs running processes
<7> hkj2: thanks, that makes sense
<11> With IA32, if I have a C pointer's value, what is the format of the instruction to move the data it points to into eax ? Is it mov eax, [12345678] ?
<3> Olathe, yes.
<11> Alright, thanks.
<3> np
<12> possible to use nasm/intel syntax on *non-intel* chips?
Return to
#asm
or
Go to some related
logs:
kde todolist manager
#sdl
#linux
$IPT -t nat -A PREROUTING -i $IEXT
gentoo port forwarding
#gentoo
#web
how to build a bridge with popscicle sticks
tvtime cannot open capture device ati ubuntu
#lisp
|
|