* [libre-riscv-dev] [Bug 272] functions needed in POWER simulator which match 3.0B spec
From: bugzilla-daemon @ 2020-03-31 13:06 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-272-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=272
--- Comment #4 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
found some of the helpers, look great michael. i think i may just be able
to import them from helpers.py and, yes, assume they're globally imported.
should be fine.
btw some whitespace crept in again:
+
+ <
+ <
+ def assertHex(self, a, b):
+ msg = "{:x} != {:x}".format(a, b)
+ return self.assertEqual(a, b, msg)
+
--
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 269] auto-conversion / parser of POWER ISA Spec v3.0B
From: bugzilla-daemon @ 2020-03-31 13:21 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-269-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=269
--- Comment #3 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
okaay, i have this:
# Count Trailing Zeros Word
X-Form
* cnttzw RA,RS (Rc=0)
* cnttzw. RA,RS (Rc=1)
n <- 0
do while n < 32
if (RS)[63-n=] = 0b1 then
leave
n <- n + 1
RA <- EXTZ64(n)
which gets turned into:
n = 0
while n < 64:
if GPR(RS)[63 - n] == 1:
break
n = n + 1
RA = EXTZ64(n)
that may need to be "self.GPR(RS)" or just
"self.regfile.read_reg(RS")
hmmm nuts, it needs to be more like this, doesn't it?
r1_sel = yield pdecode2.e.read_reg1.data
operand1 = self.regfile.read_reg(r1_sel)
because we are pushing things through decode2. that's code from the
internal_ops simulator.
actually... y'know what? i'm inclined to suggest skipping decode2
for this, because the "Form" (X-Form, etc.) is *already* encoded in
the spec.
--
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] pyobjc, gnu objective-c and gnustep
From: Jean-Paul Chaput @ 2020-03-31 14:11 UTC (permalink / raw)
To: lkcl ., Libre-RISCV General Development, Marie-Minerve Louërat
In-Reply-To: <CAPweEDx=aGvp8KbhdipG5Lt=Uo9p7L2miEmP88FcAPFvQnnryw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 3118 bytes --]
On Tue, 2020-03-31 at 11:42 +0000, lkcl . wrote:
> *click* what the hell am i saying?? jean-paul, we've got a clear need
> for improvements to coriolis2, it is *really* easy to justify putting
> in an application for NLNet funding, here.
Hello Luke,
This is a complicated matter. As a team of one, I have limited resources,
so I must prioritize (and I know myself, I'm not very good at that).
Anyway, the short term goal is to have the 180nm circuit done and
working by October. In order to do that I/we must not "finish"
Coriolis, but put it to a point it can fulfil that objective.
I'm convinced it is doable, but we should go straight to the point,
because I'm sure that lots of unexpected issues will pop-up and
I will have to tackle them quickly.
My "development cycle" are alternate steps of "adding features" then
"improve code at constant features".
So, having more hands will really be a plus (as you already proposed in
an early mail). The problem is to have someone(s) with that triple skills
(ASIC, algorithmic, software) and it has been proven difficult on my
end. To have an example of the kind of code I get, you could take a
look to the whole capacitor stuff in coriolis/oroshi/python/
(and you will easily see where I modified the code with my unique
coding style). This was made by a good electrical engineer, but
with embryonic software knowledge. The code is to draw the layout
of one or a matrix of analog capacitors. The comments are made for
doxygen.
And besides, all of our students have already chosen their internship
(in the industry). I think we may have a good one in June.
And lastly, due to the Covid-19 and University shutdown we cannot
hire anybody, should we have a candidate.
I absolutely do not want to give you the impression that I do not
want more people working on Coriolis, quite the contrary.
But I want to expose the context as rightfully as it is.
The question being how to circumvent those initial conditions
to get more efficient people working on Coriolis?
I've taken a look at GNUstep, it seems a bit quite by there...
(maybe I was on the wrong site). For the record, WidowMaker is
one of the more memory efficient window manager I have ever seen
(still can work on my UltraSparc 1 / NetBSD).
However I will remove Boost as soon as possible, it has proven to
be a pebble in my shoes for too long. And migrating towards Python3.
I'm currently making my Python code a bit more PEP8 compliant then
backporting some of the work of Jock in soclayout. *But* I will keep
some style that you may find bad. Paradox is that the "comma" at the
start of line was showed to me by an early Python adopter back around
2000...
Best regards,
--
.-. J e a n - P a u l C h a p u t / Administrateur Systeme
/v\ Jean-Paul.Chaput@lip6.fr
/(___)\ work: (33) 01.44.27.53.99
^^ ^^ cell: 06.66.25.35.55 home: 09.65.29.83.38
U P M C Universite Pierre & Marie Curie
L I P 6 Laboratoire d'Informatique de Paris VI
S o C System On Chip
[-- 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 272] functions needed in POWER simulator which match 3.0B spec
From: bugzilla-daemon @ 2020-03-31 14:24 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-272-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=272
--- Comment #5 from Michael Nolan <mtnolan2640@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #3)
> these are the functions, listed in 3.0B section 1.4.3 p6 - p7
> there's really not many of them.
Just a note: SPR(x), GPR(x) and MEM(x, y) will need to be located outside
helpers.py so they can access their respective memories
--
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] pyobjc, gnu objective-c and gnustep
From: lkcl . @ 2020-03-31 14:30 UTC (permalink / raw)
To: Jean-Paul Chaput
Cc: Marie-Minerve Louërat, Libre-RISCV General Development
In-Reply-To: <e01a01fb87d745f34fa4b8e71445fb1777f308c6.camel@lip6.fr>
On Tue, Mar 31, 2020 at 3:11 PM Jean-Paul Chaput
<Jean-Paul.Chaput@lip6.fr> wrote:
> On Tue, 2020-03-31 at 11:42 +0000, lkcl . wrote:
> > *click* what the hell am i saying?? jean-paul, we've got a clear need
> > for improvements to coriolis2, it is *really* easy to justify putting
> > in an application for NLNet funding, here.
>
> Hello Luke,
>
> This is a complicated matter. As a team of one, I have limited resources,
> so I must prioritize (and I know myself, I'm not very good at that).
> Anyway, the short term goal is to have the 180nm circuit done and
> working by October.
yes absolutely. i wanted to think slightly beyond that.
> some style that you may find bad. Paradox is that the "comma" at the
> start of line was showed to me by an early Python adopter back around
> 2000...
sigh yes that was when i started using python. it predates common
usage of PEP8.
best,
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 272] functions needed in POWER simulator which match 3.0B spec
From: bugzilla-daemon @ 2020-03-31 14:31 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-272-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=272
--- Comment #6 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from comment #5)
> Just a note: SPR(x), GPR(x) and MEM(x, y) will need to be located outside
> helpers.py so they can access their respective memories
yes, see http://bugs.libre-riscv.org/show_bug.cgi?id=269#c3
--
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] Public Inbox
From: Jacob Lifshay @ 2020-03-31 15:33 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDyijsVrD5oRYzWn8PmL0=cHnsny=rRXoR8O7Uzri94ZVw@mail.gmail.com>
On Tue, Mar 31, 2020, 03:04 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:
> On Tue, Mar 31, 2020 at 6:20 AM Jacob Lifshay <programmerjake@gmail.com>
> wrote:
> >
> > On Mon, Mar 30, 2020, 21:31 Immanuel, Yehowshua U <yimmanuel3@gatech.edu
> >
> > wrote:
> >
> > > Try this:
> > >
> > > http://inbox.libre-riscv.org/libre-riscv-dev/
> >
> >
> > both accessing using a web browser and git fail with 502.
>
> err... are you able to get to: https://git.libre-riscv.org/
yes. Maybe it's my IP address that's making inbox.libre-riscv.org fail?
I'll try accessing it through tor from a few different exit nodes to see.
>
>
> and if so, the list is right there, as one of the repositories.
>
> 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] Public Inbox
From: Luke Kenneth Casson Leighton @ 2020-03-31 15:49 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD61UqQ1uFkWc7hWpnWg1CMgp8mU=M_n4unigSmCri26gw@mail.gmail.com>
On Tue, Mar 31, 2020 at 4:33 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
> yes.
ok if you're able to get to that, then you *will* be able to click on
the link-that-is-on-the-exact-same-server which
happens-to-be-listed-as-the-git-repo-for-public-inbox.
i'm not going to post that link to you, i'm describing it so that you
actually go looking at the page and click on it. this line:
"libre-riscv-dev.git Libre RISC-V Mailing list... No commits summary |
shortlog | log | tree"
> Maybe it's my IP address that's making inbox.libre-riscv.org fail?
> I'll try accessing it through tor from a few different exit nodes to see.
it may be IPv6 rather than IPv4 related.
i'm not going to spend sorting this out right now, as it's only a test
domain (needed to fix *another* problem) pending move to libre-soc.org
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] Public Inbox
From: Jacob Lifshay @ 2020-03-31 16:00 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzZSyWxnoUP9QLbOCFhmcQ8HVA0x8mifE8Gwr0hc2qCgQ@mail.gmail.com>
On Tue, Mar 31, 2020, 08:50 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:
> On Tue, Mar 31, 2020 at 4:33 PM Jacob Lifshay <programmerjake@gmail.com>
> wrote:
>
> > yes.
>
> ok if you're able to get to that, then you *will* be able to click on
> the link-that-is-on-the-exact-same-server which
> happens-to-be-listed-as-the-git-repo-for-public-inbox.
>
> i'm not going to post that link to you, i'm describing it so that you
> actually go looking at the page and click on it. this line:
>
> "libre-riscv-dev.git Libre RISC-V Mailing list... No commits summary |
> shortlog | log | tree"
>
that works, though as mentioned previously gitweb can't seem to be able to
access the repo files.
>
> > Maybe it's my IP address that's making inbox.libre-riscv.org fail?
> > I'll try accessing it through tor from a few different exit nodes to see.
>
> it may be IPv6 rather than IPv4 related.
>
It works through tor (IPv4?) and through my cell service (IPv6), however
doesn't work through my local wifi (IPv6). Changing browsers doesn't change
anything.
> i'm not going to spend sorting this out right now, as it's only a test
> domain (needed to fix *another* problem) pending move to libre-soc.org
ok, sounds good, though you should probably fix gitweb's access to the git
repo.
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] pyobjc, gnu objective-c and gnustep
From: Jacob Lifshay @ 2020-03-31 16:16 UTC (permalink / raw)
To: Libre-RISCV General Development; +Cc: Marie-Minerve Louërat
In-Reply-To: <CAPweEDwF93uc0157hxTHAOfDQg1VDDKUQjSXUQPBTTPS3OjE+Q@mail.gmail.com>
On Tue, Mar 31, 2020, 07:30 lkcl . <luke.leighton@gmail.com> wrote:
> On Tue, Mar 31, 2020 at 3:11 PM Jean-Paul Chaput
> <Jean-Paul.Chaput@lip6.fr> wrote:
> > some style that you may find bad. Paradox is that the "comma" at the
> > start of line was showed to me by an early Python adopter back around
> > 2000...
>
> sigh yes that was when i started using python. it predates common
> usage of PEP8.
>
This is one of the reasons I like Rust: because they use the same
consistent code style nearly everywhere and they have a tool (rustfmt) that
automatically thoroughly formats everything in that style. Additionally,
beginners are encouraged to use it. Even if there are some things I would
do differently if I were designing the code style today, having consistency
across all Rust code everywhere is a big enough benefit that I can live
with some things that aren't quite how I like.
I've had to deal with the gazillion different styles of C and C++ languages
and teaching materials that actively try to get beginners to come up with
their own style to their detriment. All it does is makes their code harder
to read.
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] Public Inbox
From: Immanuel, Yehowshua U @ 2020-03-31 18:02 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD7za+VB7AE2zoc-Uxuc_nwuJH0o+LuEmi3bHeByzn4CQw@mail.gmail.com>
At some point, we should migrate all the mboxes from mailman into public inbox, to take advantage of public inbox’s search feature.
Right now, public inbox only goes back until March 3 2020.
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] Public Inbox
From: Luke Kenneth Casson Leighton @ 2020-03-31 18:06 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <3EFE94C3-B808-47AA-8106-E28982D007F8@gatech.edu>
On Tue, Mar 31, 2020 at 7:03 PM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:
> Right now, public inbox only goes back until March 3 2020.
yep. i know. discuss here http://bugs.libre-riscv.org/show_bug.cgi?id=181
_______________________________________________
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] Public Inbox
From: Luke Kenneth Casson Leighton @ 2020-03-31 18:08 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDyeGtVQo+fnfbXMVXLUTJDT=2p=jp2nbgpT6udFqMCDJQ@mail.gmail.com>
doing a zen thing with the code-generator.
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] extremely busy crowdsupply update started
From: Luke Kenneth Casson Leighton @ 2020-03-31 18:09 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDxzxuYsppv37WY7BCiCAZmqt1tc1GPtLo0qC06uvqtkBw@mail.gmail.com>
build servers.
https://git.libre-riscv.org/?p=crowdsupply.git;a=blob;f=updates/023_2020mar26_decoder_emulator_started.mdwn;h=1fd0606f9a2be89dd2393cf569b87211092724fb;hb=3e5f9725d044001aceaf95482fcc101bdfa854ad#l785
could someone write something about the build servers?
thx.
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] extremely busy crowdsupply update started
From: Luke Kenneth Casson Leighton @ 2020-03-31 18:14 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwzdhxbnbfuHvri0qL80jx-84yL1fKfrfQiJOXyzZ3i5A@mail.gmail.com>
jacob the example's a bit big, it's the kind of thing that would be
great in its own update (which we move it to) with a full explanation.
could you put it in an "example" file in a repo somewhere, link to it,
and say "we'll do an update about the IR later"?
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] extremely busy crowdsupply update started
From: Cole Poirier @ 2020-03-31 18:35 UTC (permalink / raw)
To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAPweEDwzdhxbnbfuHvri0qL80jx-84yL1fKfrfQiJOXyzZ3i5A@mail.gmail.com>
On Mar 31 2020, at 11:09 am, Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
> build servers.
> https://git.libre-riscv.org/?p=crowdsupply.git;a=blob;f=updates/023_2020mar26_decoder_emulator_started.mdwn;h=1fd0606f9a2be89dd2393cf569b87211092724fb;hb=3e5f9725d044001aceaf95482fcc101bdfa854ad#l785
>
> could someone write something about the build servers?
>
> thx.
>
> l.
Sure I'll put in a short blurb and Jacob can add to it if he thinks it
necessary. Do I have the necessary access to the crowdsupply git repo?
Cole
_______________________________________________
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 272] functions needed in POWER simulator which match 3.0B spec
From: bugzilla-daemon @ 2020-03-31 18:35 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-272-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=272
--- Comment #7 from Michael Nolan <mtnolan2640@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #3)
> these are the functions, listed in 3.0B section 1.4.3 p6 - p7
>
> BCD_TO_DPD(x)
> DPD_TO_BCD(x)
The instructions that use these pseudocode functions (cbcdtd and cdtbcd) cause
the qemu power9 machine to trap to an exception handler. Should I bother trying
to implement them at the moment?
--
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 272] functions needed in POWER simulator which match 3.0B spec
From: bugzilla-daemon @ 2020-03-31 18:47 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-272-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=272
--- Comment #8 from Michael Nolan <mtnolan2640@gmail.com> ---
Status of each helper function in the document:
ABS(x) - Not found in pseudocode
BCD_TO_DPD(x) - Traps on QEMU
CEIL(x) - Not found in pseudocode
DOUBLE(x) - Float - needs softfloat library
DPD_TO_BCD(x) - Traps on QEMU
EXTS(x) - Implemented
FLOOR(x) - Not found in pseudocode
GPR(x) - Needs internal implementation
MASK(x, y) - Implemented
MEM(x, y) - Needs internal implementation
ROTL64(x, y) - Implemented
ROTL32(x, y) - Implemented
SINGLE(x) - Float - needs softfloat library
SPR(x) - Needs internal implementation
--
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 272] functions needed in POWER simulator which match 3.0B spec
From: bugzilla-daemon @ 2020-03-31 20:06 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-272-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=272
--- Comment #9 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from comment #7)
> (In reply to Luke Kenneth Casson Leighton from comment #3)
> > these are the functions, listed in 3.0B section 1.4.3 p6 - p7
> >
> > BCD_TO_DPD(x)
> > DPD_TO_BCD(x)
>
> The instructions that use these pseudocode functions (cbcdtd and cdtbcd)
> cause the qemu power9 machine to trap to an exception handler. Should I
> bother trying to implement them at the moment?
... naah :)
(In reply to Michael Nolan from comment #8)
> Status of each helper function in the document:
> SINGLE(x) - Float - needs softfloat library
let's leave this one for now. i'd like to focus on integer initially.
i am planning to do a "pre-prep" phase (which gets variables set up,
reading in advance from the regfile) and "post-cleanup" phase
(which writes out anything that was modified)
what we will need, however, is an indexable overloaded integer class.
(err, basically, the features of Signal).
in other words, due to the fact that you can do this:
RS[32:64] = product[0:32]
or
RS[0:32] = (RA)[0:32] + (RB)[0:32]
it means basically an integer class with operator overloads on
__add__ *and* it means adding a __getitem__ (in order to be able
to do the slice), and probably changing it to be this:
RS[0:32].eq(RA[0:32] + RB[0:32])
later, we will need a class for SimpleV anyway (so as to be able to change
bit-widths)
do you want to do that? it's basically a class:
class Int:
def __init__(self, value, width):
self.value = value
self.width = width
def __getitem__(self, idx):
if isinstance(idx, slice):
# TODO, convert slice to an &able mask,
# make sure that the length is that of the slice
else:
return Int((self.int & (1<<idx) >> idx, 1)
it will also need an "append" function - again, just like Signal can
use Cat().
it *might* - although performance will be absolutely terrible - be that
we are forced to individually slice bits into lists.
one other alternative, michael, is just... use Signal. it's got everything
needed.
ideas?
--
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] PPC on Talos and Playstation 3
From: Michael Nolan @ 2020-03-31 21:57 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <CAC2bXD68ze_ZNsHm_gECzFzQXT-E8td=ART0gD1Rp28Vb-EiqQ@mail.gmail.com>
On 3/30/20 3:52 AM, Jacob Lifshay wrote:
>
> From some searching I found a linux port for the WiiU, however, it only
> supports booting 1 core.
>
> https://gitlab.com/linux-wiiu/linux-wiiu#device-support
>
> The main benefit of Power Macs is the software's highly likely to work,
> whereas both the WiiU and PS3 are less likely to.
Yehowshua sent me a couple of links to some G5 powermacs:
a 2 socket PowerMac G5 for $130 (incl S+H)
an iMac G5 with dead/dying display for $81
(not including ebay links because I didn't think that was a great idea
on a public mailing list, will send via private email if you want)
Would LibreSoC be interested in buying either of these via me or one of
our other members?
--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
* [libre-riscv-dev] [Bug 272] functions needed in POWER simulator which match 3.0B spec
From: bugzilla-daemon @ 2020-03-31 22:02 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-272-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=272
--- Comment #10 from Michael Nolan <mtnolan2640@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #9)
> ... naah :)
> let's leave this one for now. i'd like to focus on integer initially.
That's what I figured
> later, we will need a class for SimpleV anyway (so as to be able to change
> bit-widths)
>
> do you want to do that? it's basically a class:
I can, sure.
>
> one other alternative, michael, is just... use Signal. it's got everything
> needed.
Doing it through signal would mean messing with yield and such wouldn't it?
Unless implementing the class turns out to be very difficult, I'd kinda like to
avoid 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] PPC on Talos and Playstation 3
From: Luke Kenneth Casson Leighton @ 2020-03-31 23:01 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <0a6fab6c-db49-1d8a-6f9d-e387af92eb75@gmail.com>
On Tuesday, March 31, 2020, Michael Nolan <mtnolan2640@gmail.com> wrote:
>
> Would LibreSoC be interested in buying either of these via me or one of
> our other members?
with access to the TALOS II server (which i can give you access to, and you
probably need it) these machines on ebay, unless they are POWER9 compliant,
are a bit of a distraction unfortunately, because they will be POWER8
(v2.07) or older.
the NEC processors from the powerpc-notebook project *might* be POWER9.
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
^ permalink raw reply
* [libre-riscv-dev] [Bug 272] functions needed in POWER simulator which match 3.0B spec
From: bugzilla-daemon @ 2020-03-31 23:07 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-272-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=272
--- Comment #11 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from comment #10)
> Doing it through signal would mean messing with yield and such wouldn't it?
> Unless implementing the class turns out to be very difficult, I'd kinda like
> to avoid that
sigh well as the PowerDecoder class is based around Signal we are kinda stuck
with yield and it is a pain.
i will attempt a pre and post process tomorrow which basically duplicates what
you did to get src1 2 etc out of the opcode.
once i have the regnums as integers i believe the class Int as defined, which
passes Int(value,len) around between ooerations rather than just value would do
the trick
--
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] extremely busy crowdsupply update started
From: Cole Poirier @ 2020-03-31 23:11 UTC (permalink / raw)
To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <E1EB3857-CBC3-4C0A-B4AD-3E35899605F8@getmailspring.com>
On Mar 31 2020, at 11:35 am, Cole Poirier <colepoirier@gmail.com> wrote:
> On Mar 31 2020, at 11:09 am, Luke Kenneth Casson Leighton
> <lkcl@lkcl.net> wrote:
>> could someone write something about the build servers?
>>
>> thx.
>>
>> l.
>
> Sure I'll put in a short blurb and Jacob can add to it if he thinks it
> necessary. Do I have the necessary access to the crowdsupply git repo?
>
> Cole
Sorry it turns out I don't have push access to the crowdsupply repo.
Luke, may I request push access to the crowdsupply repo. I remember that
in an email a few days ago you told I should give you a name for the
repo I want created for the environment setup scripts. Can you create
and also grant me push access to a repository named dev-env-setup?
Unless you can think of a more appropriate name.
Cole
_______________________________________________
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] PPC on Talos and Playstation 3
From: Immanuel, Yehowshua U @ 2020-04-01 0:23 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDy-YTOZRXvWVM_qboQx908mEEPLPMQq5RyZ3_uWw9qWbA@mail.gmail.com>
> the NEC processors from the powerpc-notebook project *might* be POWER9.
I looked into this - these are actually NXP processors. NXP T2080 to be precise.
The data sheet is a little unhelpful - not making it clear what POWER it is.
Anyways - the processor itself has some similarities to our goals. It might be a good idea to browse through its specs and see if we can match its pinouts down the road. Hopefully, by that time, powerpc-notebook is ready to go, and our processor could be just plug and play…
And I wanted to attach an image from the data sheet, but… too large at 88KB :(
_______________________________________________
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