Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: bugzilla-daemon@libre-riscv.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 267] The efficiency of adder/subtractor
Date: Tue, 07 Apr 2020 13:36:20 +0000
Message-ID: <bug-267-13-ntG2UEEEY9@http.bugs.libre-riscv.org/> (raw)
In-Reply-To: <bug-267-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=267

--- Comment #7 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to Jock Tanner from comment #4)
> Very roughly speaking, N-bit ripple-carry adder takes a*N transistors and
> b*N time for calculation, while straight-out carry-lookahead adder takes a^N
> transistors and b time. AFAIK in practical ALU design they always make a
> compromise between the two. And I just wonder what kind of compromise could
> be suitable for *reconfigurable*, high-speed ALU.
> 
> I imagine something cascadable, like 74181 bit-slice ALUs + 74182 carry
> generators [2], but with 'plexors in between. But the speed of such a design
> may be questionable.

I haven't checked which specific design yosys produces for an adder, but I know
there are divide and conquer carry lookahead designs that have area of
O(N*log(N)) and delay of O(log(N)) when ignoring delay due to wire length, so
that's much better than the above a^N value.

I found a paper with an overview of different carry lookahead adder designs:
https://www.ijrte.org/wp-content/uploads/papers/v7i5s4/E10920275S419.pdf

In fact, I'm planning on using the same kind of recursive divide and conquer
structure for purposes other than addition such as finding the first set bit or
a prefix-sum.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

  parent reply index

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26 22:05 [libre-riscv-dev] [Bug 267] New: " bugzilla-daemon
2020-03-26 23:10 ` [libre-riscv-dev] [Bug 267] " bugzilla-daemon
2020-04-07  5:23 ` bugzilla-daemon
2020-04-07  9:48 ` bugzilla-daemon
2020-04-07 11:39 ` bugzilla-daemon
2020-04-07 11:48 ` bugzilla-daemon
2020-04-07 13:15 ` bugzilla-daemon
2020-04-07 13:36 ` bugzilla-daemon [this message]
2020-04-07 13:38 ` bugzilla-daemon
2020-04-07 14:44 ` bugzilla-daemon
2020-04-07 15:14   ` whygee
2020-04-07 15:25     ` Jacob Lifshay
2020-04-07 15:46       ` whygee

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=bug-267-13-ntG2UEEEY9@http.bugs.libre-riscv.org/ \
    --to=bugzilla-daemon@libre-riscv.org \
    --cc=libre-riscv-dev@lists.libre-riscv.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

Libre RISC-V Mailing list Archives (accessible via public-inbox)

Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev

Example config snippet for mirrors


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git