All of lore.kernel.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH v2 4/5] or1k: Initial support for FPU
Date: Wed, 3 Jul 2019 10:43:01 -0500	[thread overview]
Message-ID: <20190703154301.GY18316@gate.crashing.org> (raw)
In-Reply-To: <20190703033351.11924-5-shorne@gmail.com>

Hi Stafford,

On Wed, Jul 03, 2019 at 12:33:50PM +0900, Stafford Horne wrote:
> +    case 'd':
> +      if (REG_P (x))
> +	  if (GET_MODE (x) == DFmode || GET_MODE (x) == DImode)
> +	    fprintf (file, "%s,%s", reg_names[REGNO (operand)],
> +				    reg_names[REGNO (operand) + 1]);
> +	  else
> +	    fprintf (file, "%s", reg_names[REGNO (operand)]);
> +      else

The coding conventions says to use braces around nested conditionals.

> @@ -212,6 +214,7 @@ enum reg_class
>  #define REG_CLASS_CONTENTS      \
>  { { 0x00000000, 0x00000000 },	\
>    { SIBCALL_REGS_MASK,   0 },	\
> +  { 0x7ffffefe, 0x00000000 },	\

Above you said r0, r30, r31 are excluded, but this is r0, r8, r30, or
in GCC register numbers, 0, 8, and 31?  You probably should mention r8
somewhere (it's because it is the last arg, this avoid problems, I guess?),
and the 30/31 thing is confused some way.  Maybe it is all just that one
documentation line :-)

> +;  d - double pair base registers (excludes r0, r30 and r31 which overflow)


Segher

  reply	other threads:[~2019-07-03 15:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-03  3:33 [OpenRISC] [PATCH v2 0/5] OpenRISC updates for 10 (fpu, fixes) Stafford Horne
2019-07-03  3:33 ` [OpenRISC] [PATCH v2 1/5] or1k: Fix code quality for volatile memory loads Stafford Horne
2019-07-03  3:33 ` [OpenRISC] [PATCH v2 2/5] or1k: Fix issues with msoft-div Stafford Horne
2019-07-03  3:33 ` [OpenRISC] [PATCH v2 3/5] or1k: Add mrori option, fix option docs Stafford Horne
2019-07-03 14:49   ` Segher Boessenkool
2019-07-03 21:49     ` Stafford Horne
2019-07-03 22:26       ` Segher Boessenkool
2019-07-03 22:39         ` Stafford Horne
2019-07-03  3:33 ` [OpenRISC] [PATCH v2 4/5] or1k: Initial support for FPU Stafford Horne
2019-07-03 15:43   ` Segher Boessenkool [this message]
2019-07-03 19:09     ` Richard Henderson
2019-07-03 22:19       ` Stafford Horne
2019-07-03 22:35         ` Segher Boessenkool
2019-07-03 22:09     ` Stafford Horne
2019-07-03  3:33 ` [OpenRISC] [PATCH v2 5/5] or1k: only force reg for immediates Stafford Horne

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=20190703154301.GY18316@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=openrisc@lists.librecores.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.