Re: Linux X demo

Rod Pemberton wrote:
"santosh" <santosh.k83@xxxxxxxxx> wrote in message
news:f7n54g$mv1$1@xxxxxxxxxxx

On Thursday 19 Jul 2007 1:13 pm, Rod Pemberton
<do_not_have@xxxxxxxxxxx> wrote in message <f7n4kc$lgc$1@xxxxxxxx>:


"Herbert Kleebauer" <klee@xxxxxxxxx> wrote in message
news:469F016B.ED17442@xxxxxxxxxxxx

Leave it as a homework for the want-to-be low level Linux
X programmer to correct the code.


Herbert,

You mean well, but I have to ask. Who's going to do that?
Seriously,
doesn't "move.l r1,r5", etc., guarantee that no x86 programmer
will ever use the code you just posted...

No entirely...

i.e., Does anyone want to learn another assembly language (yours)
to do x86
assembly? How does one assemble it? How does one port it? Does
anyone
want to port it just to assemble it? If it's x86, why does it look
like a mix of 68000, AT&T, and who knows what else?

You're giving me flashbacks of Randall's teaching tool HLA: C
collided with
Pascal. After many surgeries and a jolt it lives... Grrr! Convert
your
assembler to AT&T syntax and it might be useful to others. Is your
assembler even available to others? I don't recall ever seeing a
link.

<http://137.193.64.130/windela.zip>

Or search the group for more links.
IIRC instructions are implemented only uptil the 486, and the compile
crashed for me on Linux.



It seems he has another called ass486.zip...

For windela.c, OUCH! It had a 156 warnings (DJGPP), some of which appear to
be serious. It appears he's not familiar with:

gcc -Wall -pedantic -c

OpenWatcom (wcc386 -wx) returned 48 warnings and 13 errors... It appears
that OW even had problems parsing parts of the file.

So, my observations about how to compile or port HK x86 code are still
valid...

I found I had to rename the file to a lower-case ".c" before it would compile with gcc (Linux). Upper case ".C" implies C++, or some nonsense. Compiled and worked fine for me. (yeah, "-Wall -pedantic" makes gcc complain... so don't)

I just started a post, and my browser quit (bad language)... It included a "quickstart" guide - file extension must be ".mac", start daniela/windela/lindela with no parameters, give the "first name" - no extension - when prompted. So easy, even a HLA user could do it! :) Watch in amazement as the thing makes an executable from that line-noise. One last step, "chmod +x myfile" (daniela/windela/lindela likes to name files ".com"... not really a problem...)

I'll have more to say about Herbert's example. My usual M.O. is to disassemble his executable into Nasmese, and work from there. This gives *ugly* results. This example is so beautifully formatted and commented that it deserves better than that! A "hand translation" will be tedious, but I think it may be worth it. Not immediately. Herbert speaks a strange language, but he does beautiful work!

With some recombinant surgery, and a sufficiently powerful jolt, lindela and ndisasm might be fused into a "converter"... doubt if it'd be worth it.

Best,
Frank
.

Relevant Pages

  • Re: Linux X demo
    ... Leave it as a homework for the want-to-be low level Linux ... X programmer to correct the code. ... doesn't "move.l r1,r5", etc., guarantee that no x86 programmer ... How does one assemble it? ...
    (alt.lang.asm)
  • Re: Linux X demo
    ... Leave it as a homework for the want-to-be low level Linux ... X programmer to correct the code. ... doesn't "move.l r1,r5", etc., guarantee that no x86 programmer ... How does one assemble it? ...
    (alt.lang.asm)
  • Re: Linux X demo
    ... X programmer to correct the code. ... Does anyone want to learn another assembly language to do x86 ... How does one assemble it? ... How does one port it? ...
    (alt.lang.asm)
  • Re: x64 Calling convetion(ABI) issues.
    ... despite the similarity between x86 and AMD64 as assembly syntax, ... >> fit in a register, ... >>> assemble code) have some problems. ...
    (microsoft.public.development.device.drivers)
  • Re: memmove crash
    ... Pointers and ints are not the same size on all systems. ... system doesn't compile on yours, then I think I definately want to go back to assembly language. ... I can take an assembly program and recompile it on any other x86 linux system and it will compile and work without a problem, whereas if you take a C program that compiles on one person's x86 linux system, it may or may not compile on another's. ... If a program assembles and works on one x86 linux system, it will assemble and work on another x86 linux system just the same. ...
    (alt.lang.asm)