From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] using a stage chain in a stage
Date: Thu, 4 Jun 2020 02:20:18 +0100
Message-ID: <CAPweEDwvg1bQ9MLxrk660J9v_DwssibnkYtyFJ_Mqvf-6NN_cg@mail.gmail.com> (raw)
In-Reply-To: <CAC2bXD6Znt5PPj6n22eRV-fnGt6kdRotWFKeX2uxDcm3T57rLw@mail.gmail.com>
On Thursday, June 4, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:
> I'm trying to build the div pipe, however, the ispec and ospec need to
> be different than the currently existing code since that is FP
> specific, there needs to be additional io signals that are not
> included in all the FP*Data classes. Additionally, I don't want to
> just overwrite the existing FPDiv pipe code since I'm not planning on
> adding FP div support right away, and the code needs to be refactored
> somewhat since the FPdiv pipe code is currently generic over being
> 16/32/64-bit at compile-time and the new code will need to be able to
> dynamically switch between them at runtime, once FP is added again.
ah we're not doing dynamic partitioning. we are doing 64 bit only,
standard POWER9 and will refactor later.
>
> Luke, or whoever's available, can you give me an example of a
> combinatorial stage chain that is used inside a single stage without
> being wired as the inputs and outputs, along with getting all the
> pipekls stuff connected properly?
i placed a cookie cut version here already:
https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/fu/div/pipeline.py;hb=HEAD
ctx will automatically pick up the context, which contains op, which is the
operand data structure. you should stick with CompALUSubset for now.
> Somewhat unrelated, I moved all the unused code out of the fpdiv
> folder and into the unused folder
ah good, ok.
l.
--
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next prev parent reply index
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 0:52 Jacob Lifshay
2020-06-04 1:20 ` Luke Kenneth Casson Leighton [this message]
2020-06-04 1:30 ` Jacob Lifshay
2020-06-04 1:37 ` Luke Kenneth Casson Leighton
2020-06-04 1:32 ` Luke Kenneth Casson Leighton
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=CAPweEDwvg1bQ9MLxrk660J9v_DwssibnkYtyFJ_Mqvf-6NN_cg@mail.gmail.com \
--to=lkcl@lkcl.net \
--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