qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>
Subject: Re: [Qemu-devel] Alpha build failure: dyngen picking out a nameless symbol
Date: Thu, 15 Nov 2007 22:50:31 +0000	[thread overview]
Message-ID: <200711152250.33783.paul@codesourcery.com> (raw)
In-Reply-To: <f43fc5580711151201m27889636l9b9945c561c90a59@mail.gmail.com>

> So gcc puts the zero constant to .rodata.cst8 and generates code to
> load the zero value from this location. This method is not supported
> by dyngen for Sparc, but ARM uses similar method for all (?)
> constants.

Not quite. ARM puts constant pools inline with the code, not in rodata. This 
is a fairly fundamental property of the arm architecture. Unlike most other 
risc architectures arm does not really have any other mechanism for loading 
addresses/large values.  Dyngen has a nontrivial amount of special code to 
handle this.

Paul

      reply	other threads:[~2007-11-15 22:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-14  7:04 [Qemu-devel] Alpha build failure: dyngen picking out a nameless symbol Shaddy Baddah
2007-11-14  8:10 ` [Qemu-devel] now ppc build failure: dyngen: empty code for op_splatw_T1_64 Shaddy Baddah
2007-11-14 13:13   ` [Qemu-devel] and now bus error for i386 guest Shaddy Baddah
2007-11-14 20:42     ` Blue Swirl
2007-12-04  4:21       ` Shaddy Baddah
2007-12-04 13:23       ` Shaddy Baddah
2007-12-04 18:54         ` Blue Swirl
2007-12-05 14:33           ` Shaddy Baddah
2007-12-05 21:36             ` Blue Swirl
2007-12-06  0:17               ` Shaddy Baddah
2007-12-06  9:10                 ` Blue Swirl
2007-12-06 15:19                   ` Blue Swirl
2007-11-15 20:01 ` [Qemu-devel] Alpha build failure: dyngen picking out a nameless symbol Blue Swirl
2007-11-15 22:50   ` 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=200711152250.33783.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).