qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3] trivial: Remove some pre-TCG CPUArchState members
Date: Wed, 21 Nov 2012 08:51:50 -0800	[thread overview]
Message-ID: <50AD06A6.3000602@twiddle.net> (raw)
In-Reply-To: <1351805797-31899-1-git-send-email-rth@twiddle.net>

Ping.

On 2012-11-01 14:36, Richard Henderson wrote:
> Best I can figure, these temporaries were used by the dyngen
> code generator, last seen in qemu 0.9.0.  Certainly there are
> no references to these members remaining.
> 
> Built x86_64 and i686 hosts.
> 
> 
> r~
> 
> 
> Richard Henderson (3):
>   target-alpha: Remove t0, t1 from CPUAlphaState
>   target-m68k: Remove t1 from CPUM68KState
>   target-sparc: Remove t0, t1 from CPUSPARCState
> 
>  target-alpha/cpu.h | 7 -------
>  target-m68k/cpu.h  | 3 ---
>  target-sparc/cpu.h | 1 -
>  3 files changed, 11 deletions(-)
> 

  parent reply	other threads:[~2012-11-21 16:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-01 21:36 [Qemu-devel] [PATCH 0/3] trivial: Remove some pre-TCG CPUArchState members Richard Henderson
2012-11-01 21:36 ` [Qemu-devel] [PATCH 1/3] target-alpha: Remove t0, t1 from CPUAlphaState Richard Henderson
2012-11-01 21:36 ` [Qemu-devel] [PATCH 2/3] target-m68k: Remove t1 from CPUM68KState Richard Henderson
2012-11-01 21:36 ` [Qemu-devel] [PATCH 3/3] target-sparc: Remove t0, t1 from CPUSPARCState Richard Henderson
2012-11-21 16:51 ` Richard Henderson [this message]
2012-11-21 17:09   ` [Qemu-devel] [PATCH 0/3] trivial: Remove some pre-TCG CPUArchState members Andreas Färber
2012-11-21 18:23     ` Richard Henderson
2012-11-21 18:42       ` Peter Maydell
2012-11-22  7:57 ` [Qemu-devel] [Qemu-trivial] " Stefan Hajnoczi

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=50AD06A6.3000602@twiddle.net \
    --to=rth@twiddle.net \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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).