multiplication differences in HLA and gnu as
in [ASM]
|
Prev: Directly Reading/Writing to Disk
Next: remplace Ascii
From: Herbert Kleebauer on 6 Apr 2008 06:22 Evenbit wrote: > On Apr 3, 5:37 pm, Herbert Kleebauer <k...(a)unibwm.de> wrote: > > > > > No problem: For an HLL, one is allowed to do what he wants > > > with the syntax. > > > > What has this to do with HLL? The CPU defines the machine language > > and the assembler defines the assembler syntax. And any modification > > of the "Intel syntax" can only mean an improvement. > > Are you off your meds?? You are usually of agreement that HLA is > indeed an HLL. Sure, but I never would claim that changing the syntax of an assembler makes it a HLL. As long as you write a symbolic representation of machine code it is an assembler and it doesn't matter which syntax you use. But there are logical and illogical ways for a symbolic representation of machine code. And for me it is nearly impossible to find a modification of the so called "Intel syntax" which would make it more illogical. Which in other words means: Any modification of the "Intel syntax" can only mean an improvement.
From: Rod Pemberton on 7 Apr 2008 05:36 "Wolfgang Kern" <nowhere(a)never.at> wrote in message news:ftcoh7$9a0$2(a)newsreader2.utanet.at... > GRUB and LILO unfortunately don't know how to boot KESYS, so > I have to write my own Linux-loader, which asks me to analyse > this two to figure out how Linux starts up at all, because > nobody could tell me in detail how this should be done. > All answers I got so far: > "search for vmlinuz or initrd files in the whole volume" It won't help with LILO, but can't you add a multi-boot header (detected by GRUB) to KESYS? It's only 12 32-bit values... See section 3.1.1 here: http://www.gnu.org/software/grub/manual/multiboot/multiboot.html Anyway, determining how to boot an OS from different bootloaders might be a good question for alt.os.development (now cross-posted...). Rod Pemberton
From: Wolfgang Kern on 8 Apr 2008 06:01 Rod Pemberton replied: >> GRUB and LILO unfortunately don't know how to boot KESYS, so >> I have to write my own Linux-loader, which asks me to analyse >> this two to figure out how Linux starts up at all, because >> nobody could tell me in detail how this should be done. >> All answers I got so far: >> "search for vmlinuz or initrd files in the whole volume" > It won't help with LILO, but can't you add a multi-boot header (detected by > GRUB) to KESYS? It's only 12 32-bit values... See section 3.1.1 here: > http://www.gnu.org/software/grub/manual/multiboot/multiboot.html Thanks for this one, I downloaded the whole story to check how much work it will be to add one extra pre-boot-sector to satisfy GRUB. OTOH I cannot image to sell KESYS together with a GNU-licence. So I also downloaded GRUB2.0 source and I hope to not need all of the 3.5 MB in there. > Anyway, determining how to boot an OS from different bootloaders might be a > good question for alt.os.development (now cross-posted...). Ok. __ wolfgang
From: Evenbit on 8 Apr 2008 12:19
On Apr 6, 4:16 am, Betov <be...(a)free.fr> wrote: << snippage >> I believe that your wife has you all confused and mixed-up about the meaning of the words "fast" and "slow." ;) Nathan. |