From: Andrew Haley <aph@redhat.com>
To: "kernel coder" <lhrkernelcoder@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Trampoline implementation for MIPS
Date: Fri, 29 Sep 2006 08:17:00 -0000 [thread overview]
Message-ID: <17692.54941.544514.958655@zebedee.pink> (raw)
In-Reply-To: <f69849430609290015y3d236574s853f7f17d6eda9c1@mail.gmail.com>
kernel coder writes:
> hi,
> I'm having some trouble while understanding the generated assembly
> code for trampoline by mips back-end.
>
> Following is the code for which i'm trying to undertsand the generated
> trampoline code.
>
> int foo(int (*f)()){
> (*f)();
> }
> main(){
> int i;
> int g(){printf("hello,%d",i);}
> foo(g);
> }
>
> Parts of generated assembly code which are confusing are
>
That looks like all of it! The trouble is that we don't know what
you don't know. Firstly, did you read
http://people.debian.org/~aaronl/Usenix88-lexic.pdf
I have redirected this reply to gcc-help.
Andrew.
parent reply other threads:[~2006-09-29 8:17 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <f69849430609290015y3d236574s853f7f17d6eda9c1@mail.gmail.com>]
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=17692.54941.544514.958655@zebedee.pink \
--to=aph@redhat.com \
--cc=gcc-help@gcc.gnu.org \
--cc=lhrkernelcoder@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).