qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "andrzej zaborowski" <balrogg@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] ARM host compile fix
Date: Fri, 30 May 2008 22:10:30 +0200	[thread overview]
Message-ID: <fb249edb0805301310i57b59ee0xdb47c5129fe8844e@mail.gmail.com> (raw)
In-Reply-To: <f43fc5580805301243s29f97e0gf2d54a39ed320f26@mail.gmail.com>

On 30/05/2008, Blue Swirl <blauwirbel@gmail.com> wrote:
> I needed this patch to get sparc-softmmu compile on ARM host.

Thanks for the patch. I guess it applies to all glibcs below 2.3 or
2.4 so I'll make this check a "<= 3" - I've only built for glibc 2.5.
I'll commit it tomorrow unless you do.

> It looks
>  like the code generator is not finished, tcg_abort() is called
>  immediately on start.

I think this is due to the recent change making code_gen_buffer
dynamic and requiring an absolute jump on ARM, which I had #if 0'ed in
tcg-target.c because I had not tested it.

TCG is a bit of a moving target and I'll be trying to keep arm host
support updated, but without putting an excessive effort in being
quick.

>
>  Also sparc-linux-user final link fails:
>  /src/qemu/cpu-exec.c:609: relocation truncated to fit: R_ARM_PC24
>  against symbol `code_gen_prologue' defined in COMMON section in
>  libqemu.a(exec.o)
>  collect2: ld returned 1 exit status

Yes, arm-linux-user fails with the same error because gcc doesn't
manage to make the call to code_gen_prologue.  One solution is to wrap
the #define tcg_qemu_tb_exec in tcg/tcg.h in an #ifndef, and override
it tcg/arm/tcg-target.h with the same kind of call as was used before
introduction of prologue/epilogue which was possibly more optimal.

Regards

  reply	other threads:[~2008-05-30 20:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-30 19:43 [Qemu-devel] ARM host compile fix Blue Swirl
2008-05-30 20:10 ` andrzej zaborowski [this message]
2008-05-30 20:21   ` Paul Brook
2008-05-30 20:25   ` Blue Swirl

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=fb249edb0805301310i57b59ee0xdb47c5129fe8844e@mail.gmail.com \
    --to=balrogg@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).