qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [6967] Temporary workaround for ppc on ppc
Date: Thu, 2 Apr 2009 20:18:38 +0300	[thread overview]
Message-ID: <f43fc5580904021018t4437321bud53541e673a3de09@mail.gmail.com> (raw)
In-Reply-To: <E1LpBXs-0001bP-FG@cvs.savannah.gnu.org>

On 4/2/09, malc <av1474@comtv.ru> wrote:
> Revision: 6967
>           http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=6967
>  Author:   malc
>  Date:     2009-04-02 01:16:39 +0000 (Thu, 02 Apr 2009)
>  Log Message:
>  -----------
>  Temporary workaround for ppc on ppc
>
>  target-ppc/translate.c puts values of type opcode_t into .opcodes
>  section, using GCC extension to do so, and hoping that this will make
>  them appear contiguously and in the source order in the resulting
>  executable. This assumption is not safe and is known to be violated
>  with certain versions of GCC, certain flags passed to it and on
>  certain platforms (gcc 4.3.0, -O and PPC/PPC64 for instance)

I've always wondered if the section hack was a very clever one or too
clever one, this makes it clear.

The section uses could be removed by moving the opcode tables towards
the end of file and making the handler functions use normal C
declarations or aided with a macro. That separates the function and
its table entry a lot, but I guess we don't want to use the #include
trick this time?

  reply	other threads:[~2009-04-02 17:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-02  1:16 [Qemu-devel] [6967] Temporary workaround for ppc on ppc malc
2009-04-02 17:18 ` Blue Swirl [this message]
2009-04-02 18:03   ` malc
2009-04-02 18:18     ` Blue Swirl
2009-04-02 21:01       ` malc
2009-06-08 17:23 ` Mark McLoughlin
2009-06-08 18:26   ` malc

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