Linux OpenRISC platform development
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH v6 2/6] sim: cgen: add MUL2OFSI and MUL1OFSI functions (needed for OR1K l.mul[u])
Date: Wed, 18 Oct 2017 20:09:28 +0000	[thread overview]
Message-ID: <94eb2c0534042260b1055bd7d1ff@google.com> (raw)

Stafford Horne writes:
 > From: Peter Gavin <pgavin@gmail.com>
 > 
 > sim/common/ChangeLog:
 > 
 > 2012-03-14  Peter Gavin  <pgavin@gmail.com>
 > 	    Stafford Horne  <shorne@gmail.com>
 > 
 > 	* cgen-ops.h (MUL2OFSI): New function, 2's complement overflow
 > 	flag.
 > 	(MUL1OFSI): New function, 1's complement overflow flag.

LGTM

             reply	other threads:[~2017-10-18 20:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-18 20:09 Doug Evans [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-10-13 12:36 [OpenRISC] [PATCH v6 0/6] sim port for OpenRISC Stafford Horne
2017-10-13 12:36 ` [OpenRISC] [PATCH v6 2/6] sim: cgen: add MUL2OFSI and MUL1OFSI functions (needed for OR1K l.mul[u]) 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=94eb2c0534042260b1055bd7d1ff@google.com \
    --to=dje@google.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox