From: CH Gowri Kumar <gkumar@csa.iisc.ernet.in>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Newbie questions
Date: Fri, 08 Nov 2002 19:03:40 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805369@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805370@msgid-missing>
hello all,
I am a post-graduate student trying to write a JIT compiler for .NET CLR
on Linux,IA-64.
I have some queries related to IA-64 assembly programming
I plan to write the JIT this way:
I generate the native code directly (instead of assembly language and
then using assembler)for a particular method and jump to the address
of the starting memory location where I have generated the native code. I
have written a small program to check whether such a thing is feasible,
which is as follows:
#include<unistd.h>
int main()
{
__asm__("
mov r32\x18
mov r15\x1025
break 0x100000"
);
}
I wrote the above program and compiled it and found the appropriate codes
for the instructions using objdump -d and wrote the following program
char sc[] ="\x0a"
"\x10"
"\x00"
"\x18\x00\x21\x00\x92\x00\x00\x42\xe0\x11\x00\x20\x84\x0a";
main()
{
void (*fp)(void);
fp = (void*)sc;
fp();
}
But this program on execution gives me the error:
"Illegal instruction (core dumped)"
(A similar program for IA-32 worked well.)
I couldn't figure out what could be the problem.
I also tried using "br instruction" approach instead of the function
pointer approach, but couldn't succeed.
Can anyone explain why it is failing or atleast give me pointers where to
look for?
Thanks in advance.
Gowri Kumar
next prev parent reply other threads:[~2002-11-08 19:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-08 19:01 [Linux-ia64] Newbie questions Matthew Wilcox
2002-11-08 19:03 ` CH Gowri Kumar [this message]
2002-11-08 19:07 ` Stephane Eranian
2002-11-08 19:09 ` David Mosberger
2002-11-11 2:56 ` Saxena, Sunil
2002-11-11 18:45 ` David Mosberger
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=marc-linux-ia64-105590709805369@msgid-missing \
--to=gkumar@csa.iisc.ernet.in \
--cc=linux-ia64@vger.kernel.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