Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Arnaud Patard <apatard@mandriva.com>
To: adnan iqbal <adnan.iqbal@seecs.edu.pk>
Cc: linux-mips@linux-mips.org
Subject: Re: MIPS/Linux assembly issue
Date: Fri, 21 May 2010 14:21:47 +0200	[thread overview]
Message-ID: <m3d3wph2ck.fsf@anduin.mandriva.com> (raw)
In-Reply-To: <AANLkTikrUGzUykZJwoK3Jq9mEJa6l35jo5DXHae3vbIG@mail.gmail.com> (adnan iqbal's message of "Fri, 21 May 2010 16:46:36 +0500")

adnan iqbal <adnan.iqbal@seecs.edu.pk> writes:

> Hi all,

Hi,
>
> I am trying to compile/link/execute following very simple program in
> debian/MIPS (Tried on Qemu and Octeon). I am getting errors while executing
> the program. gdb also shows a strange behavior showing program entrypoint
> somehere in data segement. Any help getting this sorted out shall be
> appreciated.
>
> Regards
> Adnan
>
> Commands used to compile/link
> ----------------------------------------------------
> $ as hello.s -o hello.o
> $ld hello.o -o hello
> $ ./hello
>
>
> The code
> ---------------
>       .data
> str:
>         .asciiz "hello world\n"
>         .text
>         .globl __start

Please consider adding ".ent __start" here

>
> __start:
>         jal f2
>         la $4,str
>         li $2,4

It's wrong here. On o32, write syscall is 4004. Also the args are:
$4: file descriptor (here 0)
$5: string
$6: string length

>         syscall
>
>         ## terminate program via _exit () system call
>         li $2, 10

exit is 4001. 4010 is unlink. Look at /usr/include/asm/unistd.h on your
mips system.

>         syscall

Add .end __start here if you've added the .ent


Arnaud

  reply	other threads:[~2010-05-21 12:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-21 11:46 MIPS/Linux assembly issue adnan iqbal
2010-05-21 12:21 ` Arnaud Patard [this message]
2010-05-21 12:30 ` Wu Zhangjin
2010-05-25  5:33   ` adnan iqbal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3d3wph2ck.fsf@anduin.mandriva.com \
    --to=apatard@mandriva.com \
    --cc=adnan.iqbal@seecs.edu.pk \
    --cc=linux-mips@linux-mips.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox