From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>
Subject: Re: [Qemu-devel] RFC: ARM prologue linkage fix
Date: Thu, 10 Jul 2008 17:33:07 +0100 [thread overview]
Message-ID: <200807101733.07790.paul@codesourcery.com> (raw)
In-Reply-To: <f43fc5580807100836v4f8b7a98y53c96eac664439e9@mail.gmail.com>
> > > I made a patch which allows sparc-linux-user target to be linked on an
> > > ARM host. Is this OK? Sparc32 helloworld program runs successfully,
> > > otherwise untested.
>
> Is this version OK then? Should I commit it?
Your comment is somewhat ambiguous (all targets use a direct jump, ARM just
has tighter restrictions on when that is possible). I suggest:
/* The prologue must be reachable with a direct jump. ARM has a limited
branch range (possibly also PPC and SPARC?) so place it in a section
close to code segment. */
Ok with that change.
Paul
prev parent reply other threads:[~2008-07-10 16:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 19:25 [Qemu-devel] RFC: ARM prologue linkage fix Blue Swirl
2008-07-08 20:43 ` Paul Brook
2008-07-10 15:36 ` Blue Swirl
2008-07-10 16:33 ` Paul Brook [this message]
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=200807101733.07790.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).