* [libre-riscv-dev] [Bug 259] New: can't set "parent bug budget"
From: bugzilla-daemon @ 2020-03-15 22:21 UTC (permalink / raw)
To: libre-riscv-dev
http://bugs.libre-riscv.org/show_bug.cgi?id=259
Bug ID: 259
Summary: can't set "parent bug budget"
Product: Libre-RISC-V Website
Version: unspecified
Hardware: PC
OS: Linux
Status: CONFIRMED
Severity: enhancement
Priority: ---
Component: website
Assignee: lkcl@lkcl.net
Reporter: lkcl@lkcl.net
CC: libre-riscv-dev@lists.libre-riscv.org
NLnet milestone: ---
http://bugs.libre-riscv.org/show_bug.cgi?id=248
jacob wassup here, i can only set a parent bugnumber when the NLNet milestone
is 2019-10-02?
--
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] LibreSOC - RISCV and POWER dual architecture feasibility
From: Jacob Lifshay @ 2020-03-15 22:10 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <d4305c62f6c80a0be1a34019bc36000341689b76.camel@fibraservi.eu>
On Sun, Mar 15, 2020, 15:04 Staf Verhaegen <staf@fibraservi.eu> wrote:
> Immanuel, Yehowshua U schreef op zo 15-03-2020 om 19:52 [+0000]:
> > >
> > > Later (for Libre-SOC v2 or v3), it might be a good idea to add support
> for
> > > x86 and x86_64 user-mode since the patents for the base ISA will have
> > > expired by then. This would help give us an advantage since it would
> allow
> > > us to run legacy software.
> >
> >
> > Isn’t x86 kinda big - like a 1000+ instructions? How would this impact
> our power target…
> >
> > But other than that, I’m all for adding x86 support.
>
> If you consider implementing x86 instruction set you also need to
> consider the risk of patent lawsuits being filed at you...
>
that's true, but if you only implement the parts where all the patents have
expired, then they'll have a hard time suing you for patent infringement.
Jacob
_______________________________________________
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] LibreSOC - RISCV and POWER dual architecture feasibility
From: Staf Verhaegen @ 2020-03-15 22:04 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <8C348DCE-274B-476B-8F61-C1BB5F1C3EC1@gatech.edu>
[-- Attachment #1.1: Type: text/plain, Size: 874 bytes --]
Immanuel, Yehowshua U schreef op zo 15-03-2020 om 19:52 [+0000]:
> >
> > Later (for Libre-SOC v2 or v3), it might be a good idea to add support for
> > x86 and x86_64 user-mode since the patents for the base ISA will have
> > expired by then. This would help give us an advantage since it would allow
> > us to run legacy software.
>
>
> Isn’t x86 kinda big - like a 1000+ instructions? How would this impact our power target…
>
> But other than that, I’m all for adding x86 support.
If you consider implementing x86 instruction set you also need to
consider the risk of patent lawsuits being filed at you...
Risc-V instruction set is specially designed to only use features which
are not patented or for which the patents have expired. I did not dive
in the open licensing terms but I assume that includes patent licenses.
greets,
Staf.
[-- Attachment #2: Type: text/plain, Size: 177 bytes --]
_______________________________________________
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 216] LOAD STORE buffer needed
From: bugzilla-daemon @ 2020-03-15 21:19 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-216-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=216
--- Comment #12 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
jacob i'm extending the LD/ST-address-conflict matrix to unary-overlap in the
last LSB 4 bits of the address.
an unary map (LD byte == 0b0000 0000 0000 0001, LD dword = 0b0000 0000 1111
1111)
then shifted up by the LSBs of the address, and split into two (if there is
a misalignment), means that two bit-level comparisons detect if the LDs overlap
in the last 4 bits of the address.
the current system already compares bits 4 thru 11 as an *binary* address.
by combining with the unary system it gives a full guaranteed detection
of overlap, based not just on the address but on the length of the operation.
however that leaves the top bits (11 thru 39 or 48, whatever we decide the VM
page size to be).
and that can be taken care of by a 4 or 8 entry mini-L1-cache-aka-LD/ST-buffer
however what is nice is that the mini-L1-cache can:
a) use the fact that the address-conflict matrix has *already* detected
(compared) addresses in bits 0-11
b) find those addresses which *are* equal (in bits 4 and above)
c) make sure the upper bits (11+) are also equal
d) use a merge of the *unary* maps of bits 0..3 to detect which LDs/STs are
covering the same L1 cache line, for all addresses detected in (b+c)
the unary map "merge" is where a popcount will tell us which is the best one to
put straight through to the L1 cache. if all 16 bits (when merged) are set, we
know that's a full cache line.
the nice thing is, it's not actually that complicated. we don't want to make
the *entire* L1 cache line this (hence a mini-pre-L1-cache) because it would
mean a popcount function on absolutely every single line of the L1 cache, and a
lot more besides.
plus, an "optimisation" is that for those address bits 4-11, well, because
we've already compared them, instead of doing the comparison again, we can use
the *conflict matrix row number* as a substitute. i think.
i have to check that.
--
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] LibreSOC - RISCV and POWER dual architecture feasibility
From: Luke Kenneth Casson Leighton @ 2020-03-15 20:05 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <7E1C43EE-2E5C-4CD5-8711-54404C19CFA8@gatech.edu>
On Sun, Mar 15, 2020 at 8:00 PM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:
>
> > x86 and x86_64 user-mode since the patents for the base ISA will have
> > expired by then
>
> Did you hear THAT intel?
haha :)
_______________________________________________
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] LibreSOC - RISCV and POWER dual architecture feasibility
From: Immanuel, Yehowshua U @ 2020-03-15 20:00 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDw69SJ-66_Ar4mkGXsxnEa9ofUrD0uhYuy-U5GpLckVZA@mail.gmail.com>
> x86 and x86_64 user-mode since the patents for the base ISA will have
> expired by then
Did you hear THAT intel?
Soto voice: Watch out
_______________________________________________
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] LibreSOC - RISCV and POWER dual architecture feasibility
From: Luke Kenneth Casson Leighton @ 2020-03-15 19:57 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <8C348DCE-274B-476B-8F61-C1BB5F1C3EC1@gatech.edu>
On Sun, Mar 15, 2020 at 7:53 PM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:
> But yeah, the main thought in my head for sticking with a single ISA is power consumption.
it's all at the translation (decoder), phase, yehowsua. the choice
of ISA is a 33rd bit, and once decoded to that "internal" format,
it's... nothing.
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
* [libre-riscv-dev] [Bug 178] first coriolis2 tutorial, workflow and "test project" page
From: bugzilla-daemon @ 2020-03-15 19:57 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-178-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=178
--- Comment #211 from Tobias Platen <hacks2019@platen-software.de> ---
200 for me looks good
--
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] LibreSOC - RISCV and POWER dual architecture feasibility
From: Luke Kenneth Casson Leighton @ 2020-03-15 19:56 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD7fz6_KfymY5kMTFojHQsrmTGC2XZ958F1ju7s6tg-91A@mail.gmail.com>
On Sun, Mar 15, 2020 at 7:44 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> On Sun, Mar 15, 2020, 12:33 Immanuel, Yehowshua U <yimmanuel3@gatech.edu>
> wrote:
>
> > Who knows, I could be wrong. Maybe people really would find a use for dual
> > ISAs - but up front, to investor for example, and to me, it looks
> > unnecessary.
>
>
> In my opinion, dual ISAs is a significant advantage that basically no one
> else has, since it allows us to run both Power and RISC-V software at full
> speed, it's also useful for on a test server where people need to test both
> Power and RISC-V software (where QEMU isn't good enough).
from a commercial perspective, given that there doesn't exist any
mass-volume products that use RISC-V (just a lot of noise and a lot of
talk), it's not as attractive as it seems.
if however we assume that RISC-V *will* take off in mass-volume,
*then* it might become attractive.
however given that the RISC-V Foundation's reputation is now shot to
shit, and people know - loud and clear - that they are "Fake Open
Source", i highly doubt whether mass-commercial
*end-user-programmable* RISC-V systems will actually take off any time
in the next 8 to 12 years.
> Later (for Libre-SOC v2 or v3), it might be a good idea to add support for
> x86 and x86_64 user-mode since the patents for the base ISA will have
> expired by then. This would help give us an advantage since it would allow
> us to run legacy software.
now that *would* be good.
as we saw with the China ICT "Loongson G" architecture, even just the
base ISA having *partial* x86 hardware ISA support would give a
massive speed-boost of an emulated application.
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] LibreSOC - RISCV and POWER dual architecture feasibility
From: Immanuel, Yehowshua U @ 2020-03-15 19:52 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD7fz6_KfymY5kMTFojHQsrmTGC2XZ958F1ju7s6tg-91A@mail.gmail.com>
> Later (for Libre-SOC v2 or v3), it might be a good idea to add support for
> x86 and x86_64 user-mode since the patents for the base ISA will have
> expired by then. This would help give us an advantage since it would allow
> us to run legacy software.
Isn’t x86 kinda big - like a 1000+ instructions? How would this impact our power target…
But other than that, I’m all for adding x86 support.
But yeah, the main thought in my head for sticking with a single ISA is power consumption.
Also, we should develop our codebase such that we can easily generate RTL that can target RISCV or POWER…
Like ``python3 builds.py —target RISCV64`` for example.
In other words, we should be able to parametrize by architecture:
or perhaps:
``python3 builds.py —target RISCV64+POWER``
This seems like a good feature and will probably encourage sustainable programming practices.
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] LibreSOC - RISCV and POWER dual architecture feasibility
From: Luke Kenneth Casson Leighton @ 2020-03-15 19:51 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <884F8FEE-60FF-4580-A2E7-8AAA40A6DB6B@gatech.edu>
On Sun, Mar 15, 2020 at 7:33 PM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:
>
> OK.
>
> So to sum up - we have limited funding currently, and we want to have
> something to show hopefully by October -
we're *going* to meet the tapeout deadline in October. exactly what
with will be cut - in a draconian and clinical fashion - to *make*
that goal achievable.
> progress on RISCV is already well underway.
was.
*was* underway, until the RISC-V Foundation fucked us over, yes.
> Lets make this prominent on the website - that we’re currently doing Dual ISAs.
>
> Once we do get a lot of more funding, I would eventually like to move to only supporting one architecture which seems to be POWER right now. I say this because I believe supporting DUAL ISA down the road will cause more headaches than its worth.
well, once it's done it's done.
> Not that it isn’t possible, but its notably non-trivial and adds little value to most customers.
honestly i think you're right. if we were doing ARM or x86 Dual ISA,
i'd say it had "real value".
> We can explain this to our backers - people can be flexible - especially over a cup of tea.
>
> However for right now, the risk minimizing move (if I understand everything correctly) is to maintain the position of supporting both ISA with incremental additions of POWER.
basically, so as not to be critically dependent on investment.
one of the biggest mistakes that any entrepreneurial team can make is
to make plans that ASSUME - as a critical dependency - the "existence
of VC funding".
> Who knows, I could be wrong. Maybe people really would find a use for dual ISAs - but up front, to investor for example, and to me, it looks unnecessary.
if an investor drop USD $10m onto the project, tomorrow, RISC-V goes.
if they *don't*, then we carry on with the plan that we have, and that
*most likely* means an incremental bootstrap process by way of RV32
(Minerva), RV64, RV64GC *and then* POWER *and then* SimpleV
why?
each of those is a *SMALL* incremental step.
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] LibreSOC - RISCV and POWER dual architecture feasibility
From: Jacob Lifshay @ 2020-03-15 19:43 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <884F8FEE-60FF-4580-A2E7-8AAA40A6DB6B@gatech.edu>
On Sun, Mar 15, 2020, 12:33 Immanuel, Yehowshua U <yimmanuel3@gatech.edu>
wrote:
> Who knows, I could be wrong. Maybe people really would find a use for dual
> ISAs - but up front, to investor for example, and to me, it looks
> unnecessary.
In my opinion, dual ISAs is a significant advantage that basically no one
else has, since it allows us to run both Power and RISC-V software at full
speed, it's also useful for on a test server where people need to test both
Power and RISC-V software (where QEMU isn't good enough).
Later (for Libre-SOC v2 or v3), it might be a good idea to add support for
x86 and x86_64 user-mode since the patents for the base ISA will have
expired by then. This would help give us an advantage since it would allow
us to run legacy software.
Jacob
_______________________________________________
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] LibreSOC - RISCV and POWER dual architecture feasibility
From: Immanuel, Yehowshua U @ 2020-03-15 19:37 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDy4_=oHhz+nBZbjfUdbdVu-bHswHz+=QJhctOEzuWW0Yg@mail.gmail.com>
> i've added this source code - wholesale - into the soc repo:
> https://github.com/lambdaconcept/minerva
Note, I’ve spoken to Jean Francois Nguyen, the developer of Minerva.
He said that he can’t guarantee the pipeline dependencies are correctly implmented and
has done little to no formal verification on Minerva.
He said Minerva was just more of a proof of concept for nMigen.
So please keep that in mind.
@Luke, what did you want to use Minerva for?
On the other hand, VexRISCV is pretty well tested - although its in Chisel…
Maybe someone would care to translate it to nMigen.
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] LibreSOC - RISCV and POWER dual architecture feasibility
From: Immanuel, Yehowshua U @ 2020-03-15 19:32 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDy4_=oHhz+nBZbjfUdbdVu-bHswHz+=QJhctOEzuWW0Yg@mail.gmail.com>
OK.
So to sum up - we have limited funding currently, and we want to have something to show hopefully by October - progress on RISCV is already well underway.
Lets make this prominent on the website - that we’re currently doing Dual ISAs.
Once we do get a lot of more funding, I would eventually like to move to only supporting one architecture which seems to be POWER right now. I say this because I believe supporting DUAL ISA down the road will cause more headaches than its worth. Not that it isn’t possible, but its notably non-trivial and adds little value to most customers.
We can explain this to our backers - people can be flexible - especially over a cup of tea.
However for right now, the risk minimizing move (if I understand everything correctly) is to maintain the position of supporting both ISA with incremental additions of POWER.
Who knows, I could be wrong. Maybe people really would find a use for dual ISAs - but up front, to investor for example, and to me, it looks unnecessary.
What are your thoughts on this?
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] LibreSOC - RISCV and POWER dual architecture feasibility
From: Luke Kenneth Casson Leighton @ 2020-03-15 19:25 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzbsbqT1yekdOpPWw08KGAYzavUJvDyV=tXeknxOT9Ctw@mail.gmail.com>
On Sun, Mar 15, 2020 at 7:24 PM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
>
> On Sun, Mar 15, 2020 at 7:20 PM Immanuel, Yehowshua U
> <yimmanuel3@gatech.edu> wrote:
> >
> > Or, is the internal format some sort of intermediate that both RISCV and POWER instructions map down to?
>
> yeees.
now you've got it.
and that internal format is trivial. single-bit wires.
to do a 32-bit to 32-bit translator is a MASSIVE piece of silicon that
has to preserve every nuance of the instructions...
oh... err... and once it's translated to POWER, it has to go through
*another* translation process, to be decoded into the internal format?
errr no.
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] LibreSOC - RISCV and POWER dual architecture feasibility
From: Luke Kenneth Casson Leighton @ 2020-03-15 19:24 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <098A8F9F-04F1-4E14-9A94-F69CCC3D8D3E@gatech.edu>
On Sun, Mar 15, 2020 at 7:20 PM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:
>
> Or, is the internal format some sort of intermediate that both RISCV and POWER instructions map down to?
yeees.
_______________________________________________
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] LibreSOC - RISCV and POWER dual architecture feasibility
From: Luke Kenneth Casson Leighton @ 2020-03-15 19:23 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <75CA4609-370F-455E-A88D-50E3766D45D7@gatech.edu>
On Sun, Mar 15, 2020 at 7:17 PM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:
> > no it doesn't, at all. here's the ISA tables:
> > https://libre-riscv.org/openpower/isatables/
>
> So RISCV is ONLY in software at this point - that is no RISCV on the actual hardware?
i've added this source code - wholesale - into the soc repo:
https://github.com/lambdaconcept/minerva
> And I know I seem a little pushy - but I have to be able to justify RISCV support upfront.
> To put it differently, if you can convince me of the value of retaining RISCV, then you can convince anyone.
i spent five months on adding SimpleV to spike.
*we do not have a working simulator for powerpc let alone have one
that has SV added to*
simple math.
estimated time to develop RISC-V SV hardware: about 4 man-months
estimate time to develop POWER SV hardware: at least ONE MAN-YEAR
because we DO NOT HAVE A SIMULATOR.
it's real simple.
if however we get USD $10m funding it's not an issue because we can
find a ton of people.
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] LibreSOC - RISCV and POWER dual architecture feasibility
From: Immanuel, Yehowshua U @ 2020-03-15 19:20 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <75CA4609-370F-455E-A88D-50E3766D45D7@gatech.edu>
Or, is the internal format some sort of intermediate that both RISCV and POWER instructions map down to?
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] LibreSOC - RISCV and POWER dual architecture feasibility
From: Immanuel, Yehowshua U @ 2020-03-15 19:16 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzeLs0br0dqzxdAWCovEBA0hyxBo89SPHykr3S7nTzBFg@mail.gmail.com>
> no it doesn't, at all. here's the ISA tables:
> https://libre-riscv.org/openpower/isatables/
So RISCV is ONLY in software at this point - that is no RISCV on the actual hardware?
And I know I seem a little pushy - but I have to be able to justify RISCV support upfront.
To put it differently, if you can convince me of the value of retaining RISCV, then you can convince anyone.
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] LibreSOC - RISCV and POWER dual architecture feasibility
From: Luke Kenneth Casson Leighton @ 2020-03-15 19:11 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <16F24775-E25B-4E31-A1D4-145EB65FB1D8@gatech.edu>
On Sun, Mar 15, 2020 at 6:21 PM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:
>
> > I’m still not clear how keeping RISCV compatibility helps us?
> > It seems to me like excuses to keep RISCV around than an actual need to continue with it.
>
> Unless we’re breaking down POWER instructions into RISCV operations internally - which DOES make sense to me.
no it doesn't, at all. here's the ISA tables:
https://libre-riscv.org/openpower/isatables/
those are an *internal* format (each row).
mapping to that exact same internal format by creating a RISC-V
decoder is a matter of about... 3 to 4 days work.
converting RISC-V to POWER ISA by way of a *DIRECT* conversion is an
extremely complex task, one which would normally only be considered in
software. look at how many lines of code there are in say qemu JIT
translation and it tells you what you need to know.
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] LibreSOC - RISCV and POWER dual architecture feasibility
From: Luke Kenneth Casson Leighton @ 2020-03-15 19:07 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <1BB9EA49-275B-4365-963E-9FC21D574BB7@gatech.edu>
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Sun, Mar 15, 2020 at 6:20 PM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:
>
> > massively - and provided us with a way to test it, so that when it
> > comes to implementing it in hardware, the *hardware* can be verified
> > immediately.
>
> So it sounds like the only benefit of RISCV was the RISCV spike emulator which allowed us to test our SimpleV proposal.
it was much more than that: the formal testing, the emulation, the
bootloading, the buildroot - replicating all of these is almost a
YEAR's work.
we're doing silicon *in october*... with *no working powerpc software
simulator* let alone working hardware.
again, to emphasise: we *need* to do an "incremental approach". not
having the pieces of the puzzle to be able to leapfrog from stone to
stone in small increments means that we are dead in the water until
those pieces are in place.
> I’m still not clear how keeping RISCV compatibility helps us?
we made a promise to our backers (including at least one sponsor who
is donating USD 500 a month).
> It seems to me like excuses to keep RISCV around than an actual need to continue with it.
on one hand we have financial backers on whom we depend.
on the other: if we bootstrap our way up the "ladder" by way of RISC-V
*FIRST*, we can "cross bootstrap" to POWER in SIDEWAYS small
increments.
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
* [libre-riscv-dev] [Bug 242] OpenPOWER simulation unit tests are needed
From: bugzilla-daemon @ 2020-03-15 19:00 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-242-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=242
--- Comment #1 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
see http://bugs.libre-riscv.org/show_bug.cgi?id=241#c7
https://github.com/lioncash/DolphinPPCTests
https://github.com/JustinCB/macemu/blob/master/SheepShaver/src/kpx_cpu/src/test/test-powerpc.cpp
(thanks lauri)
--
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] LibreSOC - RISCV and POWER dual architecture feasibility
From: Immanuel, Yehowshua U @ 2020-03-15 18:26 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <16F24775-E25B-4E31-A1D4-145EB65FB1D8@gatech.edu>
Although, even if we have POWER -> RISCV uOPS, we still don’t need RISCV64 compatibility.
Its just unnecessary from a customer standpoint and extra labor - I’m still not seeing the benefit.
For a MVP, we should do the minimum - which at this point, seems to be just POWER.
If its a matter of original NLNET proposals, its probably easier to request permission for changes in architectural promises than trying to deliver everything(I’m sure NLNET know that unforeseen obstacles can and will pop up)…
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] LibreSOC - RISCV and POWER dual architecture feasibility
From: Immanuel, Yehowshua U @ 2020-03-15 18:21 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <1BB9EA49-275B-4365-963E-9FC21D574BB7@gatech.edu>
> I’m still not clear how keeping RISCV compatibility helps us?
> It seems to me like excuses to keep RISCV around than an actual need to continue with it.
Unless we’re breaking down POWER instructions into RISCV operations internally - which DOES make sense to me.
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] LibreSOC - RISCV and POWER dual architecture feasibility
From: Immanuel, Yehowshua U @ 2020-03-15 18:19 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDyaCDW575g4V7NQbiXhp+wLJR+EqaYjNHfHgpjnS7ENnQ@mail.gmail.com>
> massively - and provided us with a way to test it, so that when it
> comes to implementing it in hardware, the *hardware* can be verified
> immediately.
So it sounds like the only benefit of RISCV was the RISCV spike emulator which allowed us to test our SimpleV proposal.
I’m still not clear how keeping RISCV compatibility helps us?
It seems to me like excuses to keep RISCV around than an actual need to continue with it.
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
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