From: Markus Gothe <markus.gothe@27m.se>
To: Thiemo Seufer <ths@networkno.de>
Cc: Hyon Lim <alex@alexlab.net>, linux-mips@linux-mips.org
Subject: Re: [SPAM] Re: MIPS assembly directives in GCC
Date: Thu, 01 Nov 2007 17:45:34 +0100 [thread overview]
Message-ID: <472A02AE.5060501@27m.se> (raw)
In-Reply-To: <20071101142625.GQ7712@networkno.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Thiemo Seufer wrote:
> Hyon Lim wrote:
>> I investigated kernel assembly source code in my kernel (2.6.10).
>> I found that there are a lot of assembly directives (e.g.,
>> .align, .set reorder, .cpload, .frame etc.). Is there any
>> documents which explains those directives? (not only I described
>> above. All of directives)
>
> Short of reading the assembler sourcecode I believe the best
> document is "See MIPS Run Linux".
>
>
> Thiemo
>
Use the source Luke (or Google)... I think if you'vent got a clue
about assembler (or anything else you're doing) you need to do some
research before asking, that's my not so humble opinion.
- --
_______________________________________
Mr Markus Gothe
Software Engineer
Phone: +46 (0)13 21 81 20 (ext. 1046)
Fax: +46 (0)13 21 21 15
Mobile: +46 (0)73 718 72 80
Diskettgatan 11, SE-583 35 Linköping, Sweden
www.27m.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHKgKr6I0XmJx2NrwRCNxEAJ9S1pVnCyBRismBGVoD/lBl119l2gCg0uDy
U4la1KpQWb3zAJfR/Y9Ph0U=
=lSeG
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2007-11-01 16:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-01 12:36 MIPS assembly directives in GCC Hyon Lim
2007-11-01 14:26 ` Thiemo Seufer
2007-11-01 16:45 ` Markus Gothe [this message]
2007-11-14 20:37 ` Jiju George T
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=472A02AE.5060501@27m.se \
--to=markus.gothe@27m.se \
--cc=alex@alexlab.net \
--cc=linux-mips@linux-mips.org \
--cc=ths@networkno.de \
/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