qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: "Dr. David Alan Gilbert" <dave@treblig.org>,
	peter.maydell@linaro.org, laurent@vivier.eu
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH 2/7] linux-user: i386/signal: Remove unused fp structs
Date: Sun, 5 May 2024 10:35:14 -0700	[thread overview]
Message-ID: <0b1375d2-ee39-4225-a3c2-c95abd69968d@linaro.org> (raw)
In-Reply-To: <20240505171444.333302-3-dave@treblig.org>

On 5/5/24 10:14, Dr. David Alan Gilbert wrote:
> The structs 'target_fpxreg' and 'target_xmmreg' are unused since
> Paolo's:
> 
> Commit 2796f290b546 ("linux-user: i386/signal: support FXSAVE fpstate on
> 32-bit emulation")
> 
> Signed-off-by: Dr. David Alan Gilbert <dave@treblig.org>
> ---
>   linux-user/i386/signal.c | 10 ----------
>   1 file changed, 10 deletions(-)

I have

https://lore.kernel.org/qemu-devel/20240409050302.1523277-1-richard.henderson@linaro.org/

which cleans this up.  I need to refresh and resubmit.


r~

> 
> diff --git a/linux-user/i386/signal.c b/linux-user/i386/signal.c
> index 990048f42a..9bf602b388 100644
> --- a/linux-user/i386/signal.c
> +++ b/linux-user/i386/signal.c
> @@ -34,16 +34,6 @@ struct target_fpreg {
>       uint16_t exponent;
>   };
>   
> -struct target_fpxreg {
> -    uint16_t significand[4];
> -    uint16_t exponent;
> -    uint16_t padding[3];
> -};
> -
> -struct target_xmmreg {
> -    uint32_t element[4];
> -};
> -
>   struct target_fpx_sw_bytes {
>       uint32_t magic1;
>       uint32_t extended_size;



  reply	other threads:[~2024-05-05 17:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-05 17:14 [PATCH 0/7] Remove some unused structures Dr. David Alan Gilbert
2024-05-05 17:14 ` [PATCH 1/7] linux-user: cris: Remove unused struct 'rt_signal_frame' Dr. David Alan Gilbert
2024-05-05 17:33   ` Richard Henderson
2024-05-05 17:14 ` [PATCH 2/7] linux-user: i386/signal: Remove unused fp structs Dr. David Alan Gilbert
2024-05-05 17:35   ` Richard Henderson [this message]
2024-05-05 18:33     ` Dr. David Alan Gilbert
2024-05-05 17:14 ` [PATCH 3/7] linux-user: sparc: Remove unused struct 'target_mc_fq' Dr. David Alan Gilbert
2024-05-20 13:22   ` Dr. David Alan Gilbert
2024-05-05 17:14 ` [PATCH 4/7] hw/usb/dev-network: Remove unused struct 'rndis_config_parameter' Dr. David Alan Gilbert
2024-05-06  7:37   ` Philippe Mathieu-Daudé
2024-05-05 17:14 ` [PATCH 5/7] hw/arm/bcm2836: Remove unusued struct 'BCM283XClass' Dr. David Alan Gilbert
2024-05-06  7:40   ` Philippe Mathieu-Daudé
2024-05-05 17:14 ` [PATCH 6/7] target/ppc: Remove unused struct 'mmu_ctx_hash32' Dr. David Alan Gilbert
2024-05-05 18:52   ` BALATON Zoltan
2024-05-10 12:43     ` BALATON Zoltan
2024-05-10 12:49       ` Dr. David Alan Gilbert
2024-05-05 17:14 ` [PATCH 7/7] net/can: Remove unused struct 'CanBusState' Dr. David Alan Gilbert
2024-05-06  7:43   ` Philippe Mathieu-Daudé
2024-06-07 14:04 ` [PATCH 0/7] Remove some unused structures Dr. David Alan Gilbert
2024-06-17 12:59   ` Michael Tokarev

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=0b1375d2-ee39-4225-a3c2-c95abd69968d@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=dave@treblig.org \
    --cc=laurent@vivier.eu \
    --cc=peter.maydell@linaro.org \
    --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).