public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Jim Wilson <jimw@sifive.com>
Cc: gdb-patches@sourceware.org, Monk Chiang <monk@andestech.com>
Subject: Re: [PATCH 06/24] RISC-V: Add fp support.
Date: Mon, 19 Apr 2021 00:08:00 -0400	[thread overview]
Message-ID: <YH0CINuYysuX5p86@vapier> (raw)
In-Reply-To: <20210417175831.16413-7-jimw@sifive.com>

On 17 Apr 2021 10:58, Jim Wilson wrote:
> Add F and D instruction support.

substance looks fine, just style nits

tests ?

> +execute_d (SIM_CPU *cpu, unsigned_word iw, const struct riscv_opcode *op)
> +{
> ...
> +  static const int round_modes[] =
> +  {
> +      sim_fpu_round_near, sim_fpu_round_zero,
> +      sim_fpu_round_down, sim_fpu_round_up,
> +      sim_fpu_round_default, sim_fpu_round_default,
> +      sim_fpu_round_default
> +  };

hanging indent should be 2 spaces, not 4

> +      u32 |= (cpu->fpregs[rs1].w[1] & 0x80000000) ^ (cpu->fpregs[rs2].w[1] & 0x80000000);

line is too long -- wrap to 80 cols.  i didn't check every line ... this one
just stood out.  so please give it a double check.

> +      switch (sim_fpu_is (&sfa))
> +	{
> +	case SIM_FPU_IS_NINF:
> +	  cpu->regs[rd] = 1;
> +	  break;
> +	case SIM_FPU_IS_NNUMBER:
> +	  cpu->regs[rd] = 1 << 1;

i'm a little surprised all these bits don't have constants for them.  but i
guess binutils wouldn't normally have broken out the FPU state into headers ?

> +static sim_cia
> +execute_f (SIM_CPU *cpu, unsigned_word iw, const struct riscv_opcode *op)
> +{
> ...
> +  static const int round_modes[] =
> +  {
> +      sim_fpu_round_near, sim_fpu_round_zero,
> +      sim_fpu_round_down, sim_fpu_round_up,
> +      sim_fpu_round_default, sim_fpu_round_default,
> +      sim_fpu_round_default
> +  };

use 2 space hanging indent

> +    case MATCH_FCVT_L_S:
> +      TRACE_INSN (cpu, "fcvt.l.s %s, %s",
> +		  rd_name, frs1_name);
> +      cpu->regs[rd] = (int64_t) cpu->fpregs[rs1].S[0];
> +      goto done;
> +    case MATCH_FCVT_LU_S:
> +      TRACE_INSN (cpu, "fcvt.lu.s %s, %s",
> +		  rd_name, frs1_name);
> +      cpu->regs[rd] = (uint64_t) cpu->fpregs[rs1].S[0];
> +      goto done;
> +    case MATCH_FCVT_S_L:
> +      TRACE_INSN (cpu, "fcvt.s.l %s, %s",
> +		  frd_name, rs1_name);
> +      cpu->fpregs[rd].S[0] = (float) ((int64_t) cpu->regs[rs1]);
> +      goto done;
> +    case MATCH_FCVT_S_LU:
> +      TRACE_INSN (cpu, "fcvt.s.lu %s, %s",
> +		  frd_name, rs1_name);
> +      cpu->fpregs[rd].S[0] = (float) cpu->regs[rs1];

these raw casts all feel ... wrong.  are the semantics guaranteed to match
between whatever the host CPU is (e.g. x86_64) and the target (e.g. riscv) ?
or it just seems to mostly work so we aren't going to squint too hard at it ?

> --- a/sim/riscv/sim-main.h
> +++ b/sim/riscv/sim-main.h
>  
> +typedef union FRegisterValue
> +{
> +  uint64_t     v[2];
> +  uint32_t     w[4];
> +
> +  int64_t      V[2];
> +  int32_t      W[4];
> +
> +  float        S[4];
> +  double       D[2];
> +
> +} FRegister;

trim that trailing blank line
-mike

  reply	other threads:[~2021-04-19  4:08 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-17 17:58 [PATCH 00/24] RISC-V sim: Update from riscv-gnu-toolchain Jim Wilson
2021-04-17 17:58 ` [PATCH 01/24] RISC-V sim: Fix fence.i Jim Wilson
2021-04-17 20:36   ` Mike Frysinger
2021-04-17 17:58 ` [PATCH 02/24] RISC-V sim: Fix for jalr Jim Wilson
2021-04-19  3:41   ` Mike Frysinger
2021-04-17 17:58 ` [PATCH 03/24] RISC-V sim: Atomic fixes Jim Wilson
2021-04-19  3:56   ` Mike Frysinger
2021-04-21 23:00     ` Jim Wilson
2021-04-22  0:09       ` Mike Frysinger
2021-04-22  3:12         ` Jim Wilson
2021-04-17 17:58 ` [PATCH 04/24] RISC-V sim: More atomic fixes Jim Wilson
2021-04-19  3:57   ` Mike Frysinger
2021-04-17 17:58 ` [PATCH 05/24] RISC-V sim: Fix stack pointer alignment Jim Wilson
2021-04-19  3:58   ` Mike Frysinger
2021-04-21 22:39     ` Jim Wilson
2021-04-17 17:58 ` [PATCH 06/24] RISC-V: Add fp support Jim Wilson
2021-04-19  4:08   ` Mike Frysinger [this message]
2021-04-21 23:34     ` Jim Wilson
2021-04-17 17:58 ` [PATCH 07/24] RISC-V sim: Add link syscall support Jim Wilson
2021-04-19  4:09   ` Mike Frysinger
2021-04-21 23:36     ` Jim Wilson
2021-04-17 17:58 ` [PATCH 08/24] RISC-V sim: Add brk syscall Jim Wilson
2021-04-19  5:24   ` Mike Frysinger
2021-04-21 23:51     ` Jim Wilson
2021-04-17 17:58 ` [PATCH 09/24] RISC-V sim: Fix syscall fallback Jim Wilson
2021-04-21 23:38   ` Jim Wilson
2021-04-22  3:23     ` Mike Frysinger
2021-04-23 20:35       ` Jim Wilson
2021-04-17 17:58 ` [PATCH 10/24] RISC-V sim: Fix ebreak Jim Wilson
2021-04-19  4:20   ` Mike Frysinger
2021-04-17 17:58 ` [PATCH 11/24] RISC-V sim: Fix ebreak, part 2 Jim Wilson
2021-04-19  4:20   ` Mike Frysinger
2021-04-21 23:41     ` Jim Wilson
2021-04-17 17:58 ` [PATCH 12/24] RISC-V sim: Add compressed support Jim Wilson
2021-04-19  4:13   ` Mike Frysinger
2021-04-21 23:42     ` Jim Wilson
2021-04-17 17:58 ` [PATCH 13/24] RISC-V sim: Add gettimeofday Jim Wilson
2021-04-19  4:19   ` Mike Frysinger
2021-04-17 17:58 ` [PATCH 14/24] RISC-V sim: Add csrr*i instructions Jim Wilson
2021-04-19  4:26   ` Mike Frysinger
2021-04-17 17:58 ` [PATCH 15/24] RISC-V sim: Improve cycle and instret counts Jim Wilson
2021-04-19  4:25   ` Mike Frysinger
2021-04-22  2:26     ` Jim Wilson
2021-04-17 17:58 ` [PATCH 16/24] RISC-V sim: Check sbrk argument Jim Wilson
2021-04-19  5:33   ` Mike Frysinger
2021-04-17 17:58 ` [PATCH 17/24] RISC-V sim: Fix tracing typo Jim Wilson
2021-04-19  4:26   ` Mike Frysinger
2021-04-17 17:58 ` [PATCH 18/24] RISC-V sim: Improve branch tracing Jim Wilson
2021-04-19  4:27   ` Mike Frysinger
2021-04-17 17:58 ` [PATCH 19/24] RISC-V sim: Improve tracing for slt* instructions Jim Wilson
2021-04-19  4:27   ` Mike Frysinger
2021-04-17 17:58 ` [PATCH 20/24] RISC-V sim: Set brk to _end if possible Jim Wilson
2021-04-19  5:41   ` Mike Frysinger
2021-04-22  2:45     ` Jim Wilson
2021-04-17 17:58 ` [PATCH 21/24] RISC-V sim: Fix mingw builds Jim Wilson
2021-04-19  4:12   ` Mike Frysinger
2021-04-17 17:58 ` [PATCH 22/24] RISC-V sim: Support compressed FP instructions Jim Wilson
2021-04-19  4:27   ` Mike Frysinger
2021-04-17 17:58 ` [PATCH 23/24] RISC-V sim: Add zicsr support Jim Wilson
2021-04-19  5:13   ` Mike Frysinger
2021-04-17 17:58 ` [PATCH 24/24] RISC-V sim: Fix divw and remw Jim Wilson
2021-04-19  5:10   ` Mike Frysinger
2021-04-17 20:38 ` [PATCH 00/24] RISC-V sim: Update from riscv-gnu-toolchain Mike Frysinger
2021-04-19  2:33   ` Jim Wilson
2021-04-19  3:23     ` Mike Frysinger
2021-04-19  4:32       ` Jim Wilson
2021-04-19  3:42 ` Mike Frysinger
2021-04-19  4:37   ` Jim Wilson
2021-04-21 15:47 ` Andrew Burgess
2021-04-21 17:49   ` Andrew Burgess

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=YH0CINuYysuX5p86@vapier \
    --to=vapier@gentoo.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jimw@sifive.com \
    --cc=monk@andestech.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).