* [libre-riscv-dev] [Bug 305] Create Pipelined ALU similar to alu_hier.py
From: bugzilla-daemon @ 2020-05-12 21:33 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-305-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=305
--- Comment #47 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
ok let's put the forms side-by-side, from fields.txt
#1.6.4 D-FORM
| OPCD | RT | RA| D |
# V3.0B 1.6.6 DX-FORM
| OPCD| RT| d1| d0| XO|d2
# 1.6.16 XO-FORM
| OPCD | RT| RA| RB |OE | XO |Rc |
and the shift ones are:
# 1.6.18 M-FORM
| OPCD | RS | RA | RB | MB | ME |Rc|
# 1.6.19 MD-FORM
| OPCD | RS | RA | sh | mb |XO|sh|Rc|
# 1.6.7 X-FORM
| OPCD | RT | RA | /// | XO | / |
so... well... i'm not actually seeing any 3-operand-input forms, there.
they're all 2-operand or 1-operand-plus-immediate.
note: 3-operand *input* not 3-operand *total including output operand*.
so i'm now wondering what on earth is going on, because we shouldn't need
to be reading reg3 at all.
any clues?
--
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
^ permalink raw reply
* [libre-riscv-dev] [Bug 307] look at installing a kan-ban board on top of bugzilla
From: bugzilla-daemon @ 2020-05-12 20:56 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-307-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=307
--- Comment #3 from Alain D D Williams <addw@phcomp.co.uk> ---
For this to work bugzilla needs to have the REST API option enabled.
Please can you, Luke, enable this or give me appropriate admin rights so that I
can do this.
Thanks
--
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
^ permalink raw reply
* [libre-riscv-dev] [Bug 291] HDL Workflow and Coriolis2 chroot automated setup scripts
From: bugzilla-daemon @ 2020-05-12 19:41 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-291-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=291
--- Comment #2 from Cole Poirier <colepoirier@gmail.com> ---
Luke, I was able to get the script to work to the point of correctly installing
and configuring the coriolis chroot such that it would open the coriolis window
diplaying the chicken, which when clicked on a few times displayed the coriolis
layout window as on the HDL workflow wiki. Unfortunately my script no longer
reaches this point of successful completion, and I am now consistently getting
stuck at this error:
```
-- CORIOLIS_TOP is set to
/home/ace/coriolis-2.x/Linux.x86_64/Release.Shared/install
-- Components of CORIOLIS_DIR_SEARCH:
-- /home/ace/coriolis-2.x/Linux.x86_64/Release.Shared/install
-- Found CORIOLIS_PYTHON:
--
/home/ace/coriolis-2.x/Linux.x86_64/Release.Shared/install/lib64/libpycrlcore.so
-- Configuring done
-- Generating done
-- Build files have been written to:
/home/ace/coriolis-2.x/Linux.x86_64/Release.Shared/build/unittests
Make/Ninja command: ['make', '-j4', 'install']
Scanning dependencies of target unittests
[ 50%] Building CXX object src/CMakeFiles/unittests.dir/unittests.cpp.o
[100%] Linking CXX executable unittests
[100%] Built target unittests
Install the project...
-- Install configuration: "Release"
-- Installing:
/home/ace/coriolis-2.x/Linux.x86_64/Release.Shared/install/bin/unittests
-- Set runtime path of
"/home/ace/coriolis-2.x/Linux.x86_64/Release.Shared/install/bin/unittests" to
""
Traceback (most recent call last):
File "./cgt", line 23, in <module>
helpers.showPythonTrace( sys.argv[0], e )
NameError: name 'helpers' is not defined
```
--
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
^ permalink raw reply
* Re: [libre-riscv-dev] PowerISA 3.1 (Power10) spec released
From: Luke Kenneth Casson Leighton @ 2020-05-12 15:56 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <20200512151152.lwyzfdye276xlprz@topoi.pooq.com>
On Tue, May 12, 2020 at 4:11 PM Hendrik Boom <hendrik@topoi.pooq.com> wrote:
> But it lacks technical detail about the mechanism you're proposing.
that's correct. the first step is to seek consensus that *a*
mechanism is needed - at all.
l.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] PowerISA 3.1 (Power10) spec released
From: Hendrik Boom @ 2020-05-12 15:11 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <CAPweEDxwujjbpoLe4kyNSW6j46khoV_4wzxtDfUgODSs0K51uA@mail.gmail.com>
On Tue, May 12, 2020 at 03:46:33PM +0100, Luke Kenneth Casson Leighton wrote:
> On Tue, May 12, 2020 at 2:55 PM Hendrik Boom <hendrik@topoi.pooq.com> wrote:
> >
> > On Tue, May 12, 2020 at 08:56:15AM +0100, Luke Kenneth Casson Leighton wrote:
> > >
> > > they're sufficiently busy that the core engineers (the ones in IBM,
> > > responsible for the POWER architecture) have not yet responded -
> > > publicly - to our ISAMUX/NS letter
> > > (https://libre-riscv.org/isa_conflict_resolution/isamux_isans/), and
> > > ISAMUX/NS is an extremely important part (absolutely mission-critical)
> > > of what we need to do.
> >
> > Just noticing that document is RISCV-oriented, and nowhere mentions POWER at
> > all.
>
> sorry, browser-auto-complete history: this one.
> https://libre-soc.org/openpower/isans_letter/
This one reads much better. It argues why standardising the way the PowerPC
ISA is essential.
But it lacks technical detail about the mechanism you're proposing. It mostly
rules out a lot of options you're not proposing. Perhaps that's elsewhere?
-- hendrik
>
> l.
>
> _______________________________________________
> libre-riscv-dev mailing list
> libre-riscv-dev@lists.libre-riscv.org
> http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] daily kan-ban update 12may2020
From: Luke Kenneth Casson Leighton @ 2020-05-12 15:03 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <E3BB5FF8-7777-4731-82BA-F9E3670E423C@gatech.edu>
On Tue, May 12, 2020 at 3:43 PM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> I’m currently attending Create-X startup school at Launch 2020 - for Systèmes Libres.
>
> I also got hired by Georgia Tech to help re-write the computer architecture class.
> The reason I mention this is that classes like these are very formative for students -
> and perhaps one of these students might contribute to Libre-SOC in the future.
that's a really good idea.
> With that in mind, I tried to incorporate concepts such as git, using nMigen, Cocotb, etc…
honestly, if they're learning verilog and VHDL as the primary HDL,
it's like teaching 1980s programming. i mean, it's _good_ that they
learn those - but move very very swiftly on.
something that might be really good to include as a teaching aid is
that online javascript logic simulation thing. just to get them the
absolute basics of logic gates.
even something as basic as "design a 4-bit adder at the gate level....
now redo it in VHDL, and now redo it in nmigen" would be a really
instructive and eye-opening exercise - particularly if first specified
as "for a first version you're allowed in VHDL and nmigen to do it
using the "add" operator, but the second version you are not: it must
be done with half and full adders, as modules".
that would hammer home to them the significance of even using
something as quotes basic quotes as the "add" operator in nmigen and
VHDL.
the next level up from that would be to say, "ok now do a 128-bit
adder", and they will struggle to create efficient-looking code in
VHDL, because they will end up cut/pasting 128 full-adders into the
file. the point of *that* exercise being to point out to them that
VHDL (and verilog) are *not* adequate modern languages (they never
were), and that nmigen you can use a *python for-loop* to create - and
link up - the 128 full-adders.
end-result: about 50 lines of python code instead of 300+ lines of
heavily-duplicated VHDL.
l.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] daily kan-ban update 12may2020
From: Luke Kenneth Casson Leighton @ 2020-05-12 14:53 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <dafc0660-613f-d9d4-ee5c-2f3ab0bb7475@gmail.com>
On Tue, May 12, 2020 at 3:29 PM Michael Nolan <mtnolan2640@gmail.com> wrote:
>
> Yesterday I modified the ALU tests to read the alu inputs as specified
> in the instruction instead of hardcoded register numbers.
great. i think we also worked out, it's kinda been a long-standing
convention that, instead of adding yet another 64 bit data path to
feed the ALU, the RB wires are used to feed in the immediate.
otherwise you have 64 wires for RA, 64 wires for RB, 64 wires for
RC/RS, and *another* 64 wires for an immediate.
so this is why i think you see the 6600, and RISC-V, and Power, and
many others, all never doing a 2nd reg (RB) *and* an immediate.
there's a *third* register - RC - in the case of POWER, because unlike
RISC-V which seems to be based around 2-64-bit-inputs (except FMAC),
and 1-64-bit-output, POWER seems to be based around a much more
complex 3-64-bit-datapaths-in and up to *two* 64-bit-datapaths-out....
*plus* Condition Registers in and out.
> I refactored
> the test to greatly reduce the amount of time it takes to run (went from
> ~1m to ~3s on my computer)
>
> Today I'd like to split out the shift and rotate instructions into their
> own separate FU
i think that will help make things clearer, and the actual ALU code in
each module a lot shorter.
l.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] PowerISA 3.1 (Power10) spec released
From: Luke Kenneth Casson Leighton @ 2020-05-12 14:46 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <20200512135532.jbfihzg5nr7qraac@topoi.pooq.com>
On Tue, May 12, 2020 at 2:55 PM Hendrik Boom <hendrik@topoi.pooq.com> wrote:
>
> On Tue, May 12, 2020 at 08:56:15AM +0100, Luke Kenneth Casson Leighton wrote:
> >
> > they're sufficiently busy that the core engineers (the ones in IBM,
> > responsible for the POWER architecture) have not yet responded -
> > publicly - to our ISAMUX/NS letter
> > (https://libre-riscv.org/isa_conflict_resolution/isamux_isans/), and
> > ISAMUX/NS is an extremely important part (absolutely mission-critical)
> > of what we need to do.
>
> Just noticing that document is RISCV-oriented, and nowhere mentions POWER at
> all.
sorry, browser-auto-complete history: this one.
https://libre-soc.org/openpower/isans_letter/
l.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] daily kan-ban update 12may2020
From: Yehowshua @ 2020-05-12 14:42 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDy9Kby79pBzaCQz6_Tt9hPcCkgBuGBj6S=eiALM0Ww9Zg@mail.gmail.com>
I’m currently attending Create-X startup school at Launch 2020 - for Systèmes Libres.
I also got hired by Georgia Tech to help re-write the computer architecture class. The reason I mention this is that classes like these are very formative for students - and perhaps one of these students might contribute to Libre-SOC in the future.
With that in mind, I tried to incorporate concepts such as git, using nMigen, Cocotb, etc…
https://comparch-resources.ece.gatech.edu <https://comparch-resources.ece.gatech.edu/>
Yehowshua
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] daily kan-ban update 12may2020
From: Michael Nolan @ 2020-05-12 14:28 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <CAPweEDy9Kby79pBzaCQz6_Tt9hPcCkgBuGBj6S=eiALM0Ww9Zg@mail.gmail.com>
Yesterday I modified the ALU tests to read the alu inputs as specified
in the instruction instead of hardcoded register numbers. I refactored
the test to greatly reduce the amount of time it takes to run (went from
~1m to ~3s on my computer)
Today I'd like to split out the shift and rotate instructions into their
own separate FU
--Michael
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] daily kan-ban update 12may2020
From: Tobias Platen @ 2020-05-12 14:00 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <CAPweEDy9Kby79pBzaCQz6_Tt9hPcCkgBuGBj6S=eiALM0Ww9Zg@mail.gmail.com>
On Tue, 12 May 2020 11:45:22 +0100
Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
Today I began reading the code that michael had written.
Tomorrow I will also have a short look into the PowerISA 3.1 spec.
> yesterday i pitched in with some commentary and review on the ALU side
> of the ALU that michael is doing. we need to back-reverse-engineer
> some implicit "well-known-in-the-industry" architectural design
> decisions related to how ALUs are fed immediates and register data
> (RA, RB, RC/RS), so as not to overwhelm the design with wires. it's
> looking like the "RB" port by general long-standing convention is also
> the "immediate data" port.
>
> also i did a small commentary on the Libre-SOC article being written
> by MarketNext, sigh they are used to using google docs, so we go with
> that before moving to the wiki. i also heard from roberto
> (powerpc-notebook) he has done an interview with charbax and wondered
> if we would like an introduction
> https://www.youtube.com/watch?v=7kM2zqTEHa8
>
> today i am going to start tying in the new LDSTCompUnit (currently
> going "busy" and staying there) and it will be the first time to try
> two simultaneous LDs (or STs). i also crystallised some of the
> waffling i did yesterday on bug #305 (ALU) after analysing the forms
> for fixedshift and fixedarith, realised it might be worth considering
> to split out shift into its own ALU.
>
> l.
>
> _______________________________________________
> libre-riscv-dev mailing list
> libre-riscv-dev@lists.libre-riscv.org
> http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
--
Tobias Platen <libre-soc[at]platen-software[dot]de>
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] PowerISA 3.1 (Power10) spec released
From: Hendrik Boom @ 2020-05-12 13:55 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <CAPweEDwEVr+hqdojsnn4LVP+w_dEjeK8Lw6t1wMwnBfuxkceMA@mail.gmail.com>
On Tue, May 12, 2020 at 08:56:15AM +0100, Luke Kenneth Casson Leighton wrote:
>
> they're sufficiently busy that the core engineers (the ones in IBM,
> responsible for the POWER architecture) have not yet responded -
> publicly - to our ISAMUX/NS letter
> (https://libre-riscv.org/isa_conflict_resolution/isamux_isans/), and
> ISAMUX/NS is an extremely important part (absolutely mission-critical)
> of what we need to do.
Just noticing that document is RISCV-oriented, and nowhere mentions POWER at
all.
Should it be changed to explicitly refer to the POWER architecture as one that
should acquire the CSR proposal?
-- hendrik
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 304] Define minimum viable interface set for 180nm ASIC
From: bugzilla-daemon @ 2020-05-12 12:14 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-304-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=304
--- Comment #5 from Yehowshua <yimmanuel3@gatech.edu> ---
OK. I'll try and have it finished by Thursday afternoon.
--
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
^ permalink raw reply
* [libre-riscv-dev] [Bug 304] Define minimum viable interface set for 180nm ASIC
From: bugzilla-daemon @ 2020-05-12 12:13 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-304-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=304
--- Comment #4 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
yehowshua i added a stub/starting-point ls180
https://git.libre-soc.org/?p=pinmux.git;a=blob;f=src/spec/ls180.py;h=77c5f1f7f7923cb8292499bac189ff1ce8f3b6ff;hb=aca6d68a6159136fe1f36c6430e2ffd07da13e8c
also added a stub / dummy LPC function:
https://git.libre-soc.org/?p=pinmux.git;a=blob;f=src/spec/pinfunctions.py;h=e46be8d114f00bbf571092c4e7a9ec5ece39d04b;hb=aca6d68a6159136fe1f36c6430e2ffd07da13e8c#l52
it will need its pin naming correcting, and also in ls180.py everything
including LPC moving to a single column.
we need to move quickly on this because Rudi is waiting for us
to communicate back to him the required peripheral set, and he
is experienced enough to know that we are well beyond the industry
standard time for making these decisions.
--
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
^ permalink raw reply
* [libre-riscv-dev] [Bug 304] Define minimum viable interface set for 180nm ASIC
From: bugzilla-daemon @ 2020-05-12 12:12 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-304-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=304
--- Comment #3 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
*** Bug 303 has been marked as a duplicate of this bug. ***
--
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
^ permalink raw reply
* [libre-riscv-dev] [Bug 303] define peripheral set for 180nm ASIC
From: bugzilla-daemon @ 2020-05-12 12:12 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-303-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=303
Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #2 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
whoops how did we end up creating 2 bugreports, #304 and #303?
*** This bug has been marked as a duplicate of bug 304 ***
--
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
^ permalink raw reply
* [libre-riscv-dev] [Bug 303] define peripheral set for 180nm ASIC
From: bugzilla-daemon @ 2020-05-12 12:11 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-303-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=303
Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|lkcl@lkcl.net |yimmanuel3@gatech.edu
--
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
^ permalink raw reply
* [libre-riscv-dev] [Bug 303] define peripheral set for 180nm ASIC
From: bugzilla-daemon @ 2020-05-12 12:11 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-303-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=303
--- Comment #1 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
yehowshua i added a stub/starting-point ls180
https://git.libre-soc.org/?p=pinmux.git;a=blob;f=src/spec/ls180.py;h=77c5f1f7f7923cb8292499bac189ff1ce8f3b6ff;hb=aca6d68a6159136fe1f36c6430e2ffd07da13e8c
also added a stub / dummy LPC function:
https://git.libre-soc.org/?p=pinmux.git;a=blob;f=src/spec/pinfunctions.py;h=e46be8d114f00bbf571092c4e7a9ec5ece39d04b;hb=aca6d68a6159136fe1f36c6430e2ffd07da13e8c#l52
it will need its pin naming correcting, and also in ls180.py everything
including LPC moving to a single column.
we need to move quickly on this because Rudi is waiting for us
to communicate back to him the required peripheral set, and he
is experienced enough to know that we are well beyond the industry
standard time for making these decisions.
--
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
^ permalink raw reply
* [libre-riscv-dev] daily kan-ban update 12may2020
From: Luke Kenneth Casson Leighton @ 2020-05-12 10:45 UTC (permalink / raw)
To: Libre-RISCV General Development
yesterday i pitched in with some commentary and review on the ALU side
of the ALU that michael is doing. we need to back-reverse-engineer
some implicit "well-known-in-the-industry" architectural design
decisions related to how ALUs are fed immediates and register data
(RA, RB, RC/RS), so as not to overwhelm the design with wires. it's
looking like the "RB" port by general long-standing convention is also
the "immediate data" port.
also i did a small commentary on the Libre-SOC article being written
by MarketNext, sigh they are used to using google docs, so we go with
that before moving to the wiki. i also heard from roberto
(powerpc-notebook) he has done an interview with charbax and wondered
if we would like an introduction
https://www.youtube.com/watch?v=7kM2zqTEHa8
today i am going to start tying in the new LDSTCompUnit (currently
going "busy" and staying there) and it will be the first time to try
two simultaneous LDs (or STs). i also crystallised some of the
waffling i did yesterday on bug #305 (ALU) after analysing the forms
for fixedshift and fixedarith, realised it might be worth considering
to split out shift into its own ALU.
l.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] daily kan-ban update 11may2020
From: Luke Kenneth Casson Leighton @ 2020-05-12 10:06 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <e9c73bc6-4709-3aa3-8e3e-2f061a352820@gmail.com>
On Mon, May 11, 2020 at 2:32 PM Michael Nolan <mtnolan2640@gmail.com> wrote:
> On 5/11/20 8:26 AM, Luke Kenneth Casson Leighton wrote:
> > btw i forgot to mention: here's what kan-ban is supposed to be :)
> > https://en.wikipedia.org/wiki/Kanban_(development)
> Well that explains some things. When I googled it I came up with the
> manufacturing version and was rather confused what that had to do with us.
i worked for a company that introduced the S/W Engineering version, it
went quite well: made progress (or lack of) quite obvious, and that
really helped to guide decisions.
> Yesterday (and saturday) I worked on the integer ALU adding support for
> shifts and rotates. Today I'd like to improve the ALU testbench some, so
i saw the massive speed-up. instead of a couple of minutes it's now a
few seconds.
> instead of blindly reading and writing registers based on hardcoded
> numbers it actually looks at the ones used by the instruction.
> (Basically, have it simulate the register file). I'd also like to add in
> support for carry, overflow, and condition registers.
saw the addition of the SPRs go by.
looks good, michael.
l.
> --Michael
>
>
>
> _______________________________________________
> libre-riscv-dev mailing list
> libre-riscv-dev@lists.libre-riscv.org
> http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 305] Create Pipelined ALU similar to alu_hier.py
From: bugzilla-daemon @ 2020-05-12 10:03 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-305-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=305
--- Comment #46 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Luke Kenneth Casson Leighton from comment #43)
> (In reply to Michael Nolan from comment #42)
>
> > I went through the tables and double checked, the *only* ALU instructions
> > that have 3 inputs are 2 registers and an immediate. It does not *need* 3
> > register inputs.
>
> yehyeh. ok.
>
> really... normally, what would happen is that anything that's significantly
> different like this would get put into its own Function Unit (into its own
> ALU Pipeline).
https://libre-soc.org/openpower/isa/fixedshift/
... actually... you know what? all of those are M-Form and MD-Form
whereas, quickly analysing these:
https://libre-soc.org/openpower/isa/fixedarith/
they're D-Form, DX-Form, XO-Form, and XO-Form.
some of the weird ones (addex) are Z23-Form, and the MAC ones are VA-Form
on balance therefore it kinda makes sense to split fixedshift out into
its own separate ALU / pipeline. aside from anything, it may turn out
to be the case that whilst add, sub etc. can be done in a single clock,
shift has a strong possibility of needing 2 (in really high speed
designs). that would be easier to do if they were separate pipelines.
--
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
^ permalink raw reply
* [libre-riscv-dev] [Bug 305] Create Pipelined ALU similar to alu_hier.py
From: bugzilla-daemon @ 2020-05-12 9:24 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-305-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=305
--- Comment #45 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
Ran 1 test in 1.662s
that's a little bit better :)
--
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
^ permalink raw reply
* Re: [libre-riscv-dev] PowerISA 3.1 (Power10) spec released
From: Luke Kenneth Casson Leighton @ 2020-05-12 9:09 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <20200512115042.484e26aeb757d9473b885979@gmx.com>
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Tue, May 12, 2020 at 9:49 AM Lauri Kasanen <cand@gmx.com> wrote:
>
> On Tue, 12 May 2020 09:33:52 +0100
> Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
>
> > i recall (and could be wrong about) seeing that there's different
> > bits, one covering instructions, one covering data. would need to
> > read them more closely. are you saying that the BE-for-instructions
> > bit will flip *data* order as well?
>
> I'm not that familiar with the low level details, I was speaking from
> the compliance POV. Aka BE instructions only is not enough to be
> compliant. If there are plans to support full BE, then it'd be fine.
ok so, combining page x "Linux Optional Features"
Big Endian (BE)
(LE is required for LCS. Linux supporting
LCS is 64b LE Linux.)
this basically defines - *defines* - the Linux Compliancy Subset - as
64 bit LE, with BE being optional
and page xi "Scalar Float Optional Features":
Little Endian (LE)
(BE is required for SFFS and SFS. Linux
supporting SFFS and SFS is 32b BE
Linux.)
this *defines* the "Scalar Fixed (+Float) Compliancy Subset" - both
SFFS and SFS - as *32-bit* BE, with **LE** being optional - the
*opposite* of the 64-bit case.
ah.
i recognise this pattern. i know what this is for.
* AIX compliance is for IBM internal support of AIX - running on IBM POWER9
* Linux compliance is for debian / fedora ppc64le - running on IBM POWER9
* SFFS compliance is for NXP Quorl (2.07B compliant) such as that used
in powerpc-notebook.org
* SFS compliance is for NXP MCP5xxx processors - 32-bit non-FP-based
embedded (32 to 300 mhz)
(there's probably other processor products out there which match with
those 4 levels, i just don't know what they are).
so they're recognising the various product ranges that already exist
in the various market(s). which is sensible.
what they haven't had time to do is take into full consideration our
design, which needs to be GNU/Linux compliant but not completely
overwhelm both us and the power consumption and the die area, only to
support instructions suited to high-end server and supercomputing
markets (VSX and VMX), placing even the Quad-Core ASIC into markets
it's *never going to be in*.
l.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] PowerISA 3.1 (Power10) spec released
From: Lauri Kasanen @ 2020-05-12 8:50 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <CAPweEDxqj+YZZyKXHL+=9uhGpRb5GEZeHtQw-Z=mx=_6ZCN3Sg@mail.gmail.com>
On Tue, 12 May 2020 09:33:52 +0100
Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> i recall (and could be wrong about) seeing that there's different
> bits, one covering instructions, one covering data. would need to
> read them more closely. are you saying that the BE-for-instructions
> bit will flip *data* order as well?
I'm not that familiar with the low level details, I was speaking from
the compliance POV. Aka BE instructions only is not enough to be
compliant. If there are plans to support full BE, then it'd be fine.
- Lauri
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] PowerISA 3.1 (Power10) spec released
From: Luke Kenneth Casson Leighton @ 2020-05-12 8:33 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <20200512112314.1e2bb6d08199e725106fe98a@gmx.com>
On Tue, May 12, 2020 at 9:22 AM Lauri Kasanen <cand@gmx.com> wrote:
> It's just a name though, even the doc says you can run Linux on the
> lower levels.
yes... you can.... however note the phrase "Linux Compliancy". this
means that they have plans for actual Compliance Test Suites. this in
turn will mean that
one option therefore is to have a software-driven emulator mode for
SIMD. this would be our responsibility to write and maintain.
> It's fine for libresoc to be at the int+fp level, and
> include optional features from above that are useful. I just wanted to
> point out the BE/LE requirement as it surprised me at least.
yeh - in the West it is just not known that the majority of S.E.Asia
industry runs on BE hardware that is often 40 years old (VME Bus).
> BE for instructions is not full BE, as data changes too.
i recall (and could be wrong about) seeing that there's different
bits, one covering instructions, one covering data. would need to
read them more closely. are you saying that the BE-for-instructions
bit will flip *data* order as well?
See Section 1.10 of Book I and its first two subsections. Also see
the description
of the ILE field of the LPCR in Section 2.2 of Book III and the
description of the
LE bit of the MSR in Section 4.2.1 of Book III.
p1122:
Interrupt Little-Endian (ILE)
The contents of the ILE bit are copied into
MSRLE by interrupts that set MSRHV to 0 (see
p1146:
63 Little-Endian Mode (LE)
0 The thread is in Big-Endian mode.
1 The thread is in Little-Endian mode.
if we are to flip the instruction stream to BE mode (to support the
SVP/C/VBLOCK capability) we definitely don't want data to flip as
well.
bottom line: if there *isn't* a separate bit for instructions-BE/LE
and data-BE/LE, we definitely need one.
l.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
page: next prev latest
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