All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Sergey Fedorov <serge.fdrv@gmail.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
	"Sergey Fedorov" <sergey.fedorov@linaro.org>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Richard Henderson" <rth@twiddle.net>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Andreas Färber" <afaerber@suse.de>,
	"Peter Crosthwaite" <crosthwaite.peter@gmail.com>
Subject: Re: [Qemu-devel] [PATCH v3 4/4] tcg: rework tb_invalidated_flag
Date: Mon, 18 Apr 2016 16:34:53 +0100	[thread overview]
Message-ID: <CAFEAcA9yZ4oA_duRkYMG3a-3K4xCWuJzm3BfkrVpJ6yb0goX9A@mail.gmail.com> (raw)
In-Reply-To: <5714F7C4.6040306@gmail.com>

On 18 April 2016 at 16:05, Sergey Fedorov <serge.fdrv@gmail.com> wrote:
> @@ -507,14 +510,12 @@ int cpu_exec(CPUState *cpu)
>                  }
>                  tb_lock();
>                  tb = tb_find_fast(cpu);
> -                /* Note: we do it here to avoid a gcc bug on Mac OS X when
> -                   doing it in tb_find_slow */
>
> Is this still true? Would it make more sense to push the patching down
> to the gen_code?
>
>
> This comment comes up to the commit:
>
> commit 1538800276aa7228d74f9d00bf275f54dc9e9b43
> Author: bellard <bellard@c046a42c-6fe2-441c-8c8c-71466251a162>
> Date:   Mon Dec 19 01:42:32 2005 +0000
>
>     workaround for gcc bug on PowerPC

We no longer support building on PPC OSX hosts, and haven't
for some time -- the earliest OSX we support is 10.5, which is
x86-only. So I think we can probably safely dump the gcc bug
workaround, as long as we're clear in commit messages that we're
doing so.

Looking at that commit, it seems to be related to changing the
value of T0 inside the tb_find_slow() function; at that point
in QEMU's history, T0 was a variable which was tied to a specific
host CPU register via gcc's 'asm("registername")' syntax; it's
highly likely that the gcc bug was specific to handling of that
kind of register variable anyway.

thanks
-- PMM

  reply	other threads:[~2016-04-18 15:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-14 20:45 [Qemu-devel] [PATCH v3 0/4] tcg: Misc clean-up patches Sergey Fedorov
2016-04-14 20:45 ` [Qemu-devel] [PATCH v3 1/4] tcg: code_bitmap is not used by user-mode emulation Sergey Fedorov
2016-04-14 20:45 ` [Qemu-devel] [PATCH v3 2/4] tcg: reorganize tb_find_physical loop Sergey Fedorov
2016-04-14 20:45 ` [Qemu-devel] [PATCH v3 3/4] cpu-exec: elide more icount code if CONFIG_USER_ONLY Sergey Fedorov
2016-04-14 20:45 ` [Qemu-devel] [PATCH v3 4/4] tcg: rework tb_invalidated_flag Sergey Fedorov
2016-04-18 14:09   ` Alex Bennée
2016-04-18 15:05     ` Sergey Fedorov
2016-04-18 15:34       ` Peter Maydell [this message]
2016-04-18 17:17       ` Alex Bennée
2016-04-18 17:51         ` Sergey Fedorov
2016-04-21 14:35           ` Sergey Fedorov
2016-04-21 15:55             ` Alex Bennée
2016-04-21 16:16               ` Sergey Fedorov
2016-04-21 17:18                 ` Sergey Fedorov
2016-04-21 21:54                   ` Alex Bennée
2016-04-22  9:49                     ` Sergey Fedorov

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=CAFEAcA9yZ4oA_duRkYMG3a-3K4xCWuJzm3BfkrVpJ6yb0goX9A@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=afaerber@suse.de \
    --cc=alex.bennee@linaro.org \
    --cc=crosthwaite.peter@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=serge.fdrv@gmail.com \
    --cc=sergey.fedorov@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.