* Re: [libre-riscv-dev] AMD ISAs
From: Luke Kenneth Casson Leighton @ 2020-06-09 23:21 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <1448919C-8B02-48C8-9B0D-9C03C64E1765@gatech.edu>
On Wed, Jun 10, 2020 at 12:15 AM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> All of AMDs ISA are open here.
> https://gpuopen.com/documentation/amd-isa-documentation/ <https://gpuopen.com/documentation/amd-isa-documentation/>
>
> It may be worthwhile trying to make our GPU “appear” to be an AMD device.
the problem with doing so is that the processor effectively becomes
"Dual ISA". everyone that we've talked to with significant experience
in processor design has raised eyebrows at the complexity involved in
a dual-ISA design.
it is not an insurmountable issue: it just should in no way be
underestimated, for the trade-off of not having to write any kinds of
drivers.
in addition, we need to consider that the level of instruction
compression (which reduces shared L1 I-Cache usage) anticipated
through the hardware-level compression in SimpleV will be completely
unobtainable for AMDGPU ISA interoperability... because we will be
forced *to* have AMDGPU ISA interoperability.
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] AMD ISAs
From: Yehowshua @ 2020-06-09 23:23 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDxzzWyAo5s2tM=-MuBkQ7FBBC1_Br-z9m2ON-x=E3p-6g@mail.gmail.com>
> On Jun 9, 2020, at 7:21 PM, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
>
> in addition, we need to consider that the level of instruction
> compression (which reduces shared L1 I-Cache usage) anticipated
> through the hardware-level compression in SimpleV will be completely
> unobtainable for AMDGPU ISA interoperability... because we will be
> forced *to* have AMDGPU ISA interoperability.
This is a valid point.
I’ll get back to you on this.
I feel like there is a good way to do 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] AMD ISAs
From: Jacob Lifshay @ 2020-06-09 23:25 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <5B866D98-D803-4268-A0BC-3246E604BA33@gatech.edu>
On Tue, Jun 9, 2020, 16:17 Yehowshua <yimmanuel3@gatech.edu> wrote:
> We could have a fake "PCIE AMD-like GPU" that AMD drivers talk to.
> This device then issues instructions on the CPU/GPU hybrid.
>
we would run into issues with AMD's (and other's) patents, I'm pretty sure
they haven't licensed the patents necessary to implement an AMD-compatible
GPU.
Also, that would defeat the purpose of a lot of what we're implementing
with a Power compatible ISA, having the CPU and GPU be the same processor,
and having an extensible design such that someone could add their own
custom operations on top of our code if they wanted.
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] daily kan-ban update 09jun2020
From: Cole Poirier @ 2020-06-10 0:38 UTC (permalink / raw)
To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAPweEDxTQS-h-uqTfPkpfLmisMOpE7RL-F0bMLpw-510nNTeeg@mail.gmail.com>
On Jun 9 2020, at 2:48 pm, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> On Tue, Jun 9, 2020 at 10:01 PM Cole Poirier <colepoirier@gmail.com> wrote:
>>
>> On Jun 9 2020, at 1:15 pm, Luke Kenneth Casson Leighton
>> <lkcl@lkcl.net> wrote:
>>
>> > with michael having added the qemu-execution thing, you should now
>> > first be able to add a "twi" (or tdi) instruction unit test to that,
>> > first.
>>
>> This is filling in the pseudo-code for the soc/decoder/isa/caller.py?
>
> yeees... however the first thing to do is write the unit test. then
> you have a means by which the code in caller.py py will be... called.
> without writing the unit test, you have no way to call that code,
> therefore how can you know if what you write is correct?
>
>> > this will allow you to check that the *simulator* is correct.
>>
>> How do I use qemu to verify that the simulator is correct?
>
> well, first we recall that it was michael who added the code, under
> the recent bugreport from monday. so we do this:
>
> $ git log > /tmp/f
>
> then, we open up that file, and grep "Michael". that shows this line:
> commit 613b15043fc7302c8ad4495b6bff65063eb1c0e3
> Author: Michael Nolan <mtnolan2640@gmail.com>
> Date: Mon Jun 8 13:36:57 2020 -0400
>
> Restore test_sim.py, begin modifying it for testing against qemu
>
> that looks about right, doesn't it? (i don't know the answer, either,
> however i am simply following a deductive reasoning trail, from
> evidence left by michael).
>
> so let's do a git diff
>
> $ git diff 613b15 3a0b0f
>
> and that shows (just as the comment says) a file called test_sim.py.
> from the top of the diff it shows that that test_sim.py file is in
> soc/simulator/test_sim.py
>
> so now we know where that file is.
>
>> Sorry I've
>> looked on the bug report and the wiki? Is there a wiki page with the
>> procedure? If not, what's the procedure I should follow?
>
> you need to think through a process of deducing this information for yourself.
>
> looking at that file, it's a unit test, isn't it? and it has the
> exact same "run_tst_program" pattern that's in the test_pipe_caller.py
> programs, doesn't it?
>
> therefore, logically, if we put instructions in a unit test listing,
> we expect them to be run, yes?
>
> and if you look at test_sim.py's "run_tst_program()" function, we can
> see that it has two aspects: the first being that the simulator's
> "run_tst" function is called, and the second that the qemu
> run_program() function is called.
>
> each of those will modify their respective register files, and
> qemu_register_compare walks through them and compares them, doesn't
> it?
>
> this really isn't hard to deduce!
>
> therefore to test twi, we add a new unit test to that file, and run
> it. now, it *may* fail (because it's a trap, and we don't actually
> know how qemu will react to that). we'll cross that bridge when we
> come to it, ok? we expect at least the PC to be changed to 0x700, so
> will have to work out how to get the PC out of qemu.
>
>
> in essence, here, there is a series - a chain - of logical deductive
> reasoning that allows us, from a few well-known sources that we have
> access to, to find the information that was sought.
>
> being able to do this, regardless of the size of the codebase and
> regardless of whether quotes documentation quotes exists, is an
> absolutely essential and critically important skill.
>
> it is however important that you appreciate and have confidence that
> you *can* in fact deploy such techniques (or others like it) in order
> to find what you seek.
>
> when this particular technique has failed me (due to the codebase size
> being over a quarter of a million lines) i have been known to print it
> out entirely on double-sided double-column pages (where an 80 char
> limit has been absolutely essential in meeting that), and literally
> going through absolutely every single page in the course of a day,
> speed-reading flicking one by one, to get a "subconscious" handle on
> the codebase that then allows me to go "i've seen that before" and
> stand a chance of being able to find it relatively quickly.
>
> l.
Thank you, I appreciate the walkthrough and the story about going the
old fashioned paper way. I thought that I had to do something in qemu
itself, which would have been outside the bounds of this deductive
reasoning process, as I have a tendency to get lost in forums and
documentation when dealing with complex, always buggy to some extent,
software like qemu. So I wanted to see if we had prior art pertaining to
qemu simulation. I think I should have taken the deductive reasoning
about the codebase approch for my other questions. I'm fighting my "aaah
I don't understand," and with your reminder and guide here will be able
to do so better next time.
> powerpc64-linux-gnu-gdb -interpreter=mi
> ~-data-list-register-names
> ^done,register-names=
>["r0","r1","r2","r3","r4","r5","r6","r7","r8","r9","r10","r11","r12","r13","r14","r15","r16","r17","r18","r19","r20","r21","r22","r23","r24","r25","r26","r27","r28","r29","r30","r31","f0","f1","f2","f3","f4","f5","f6","f7","f8","f9","f10","f11","f12","f13","f14","f15","f16","f17","f18","f19","f20","f21","f22","f23","f24","f25","f26","f27","f28","f29","f30","f31","pc","msr","cnd","lr","cnt","xer","fpscr","mq"
> ah HA! one of those is the condition register!
Very cool and helpful. I think I over-stressed my self while working on
the presentation yesterday, which has caused me to inadvertantly 'take'
today off. Will be back and well rested to take on these challenges of
deductive reasoning, especially in using gtkwave to understand the ALU
signaling, tomorrow :)
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] Request for input and technical expertise for Systèmes Libres Amazon Alexa IOT Pitch 10-JUN-2020
From: Cole Poirier @ 2020-06-10 0:43 UTC (permalink / raw)
To: Libre-RISCV General Development; +Cc: libre-riscv-dev
In-Reply-To: <20200609220134.62zcg7rrepvg6fr5@topoi.pooq.com>
On Jun 9 2020, at 3:01 pm, Hendrik Boom <hendrik@topoi.pooq.com> wrote:
> Looked at it today. Seems somewhat OK, but on a few pages there's too
> much text to read for the short time the page is on-screen.
Thanks for taking a look Hendrick. Yes, sorry, the video is far too
fast, it was just done so I could show you what the pitch looked like in
it's more marketing-friendly form. Yehowshua is working on getting the
presentation embedded on systemeslibres.org, where it will hopefully be
interactive like other slide decks, so one can navigate at their desired pace.
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] Request for input and technical expertise for Systèmes Libres Amazon Alexa IOT Pitch 10-JUN-2020
From: Yehowshua @ 2020-06-10 0:44 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <350B924A-EEAE-48CC-B17F-15B11CE8CC8C@getmailspring.com>
It actually already works - it is a huge WIP:
https://systemeslibres.org/prez/assets/player/KeynoteDHTMLPlayer.html#0 <https://systemeslibres.org/prez/assets/player/KeynoteDHTMLPlayer.html#0>
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] AMD ISAs
From: Yehowshua @ 2020-06-10 0:59 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD6i1O_8WpqiOLM8xa-j0B_MLu3e_5vFGEa=OwnRpyha2Q@mail.gmail.com>
> Also, that would defeat the purpose of a lot of what we're implementing
> with a Power compatible ISA, having the CPU and GPU be the same processor,
> and having an extensible design such that someone could add their own
> custom operations on top of our code if they wanted.
Noted. Well, it was an interesting idea while it lasted.
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] Request for input and technical expertise for Systèmes Libres Amazon Alexa IOT Pitch 10-JUN-2020
From: Hendrik Boom @ 2020-06-10 2:46 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <136E1A11-5A0A-45E3-9E7C-3463E66906F6@gatech.edu>
On Tue, Jun 09, 2020 at 08:44:35PM -0400, Yehowshua wrote:
> It actually already works - it is a huge WIP:
> https://systemeslibres.org/prez/assets/player/KeynoteDHTMLPlayer.html#0 <https://systemeslibres.org/prez/assets/player/KeynoteDHTMLPlayer.html#0>
Much easier to read in this format. but there's some du[lication, and, of course,
it's obviously not finished.
-- hendrik
>
> Yehowshua
> _______________________________________________
> 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 324] create POWER9 DIV pipeline
From: bugzilla-daemon @ 2020-06-10 7:00 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-324-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=324
--- Comment #8 from Jacob Lifshay <programmerjake@gmail.com> ---
Created the setup stage that translates from the input data to the format
expected by DivPipeCore but didn't create tests yet, am going to be done for
today. Still have to double check that I got the number of fractional bits
correct.
--
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] why developers love rust on stackoverflow blog
From: Jacob Lifshay @ 2020-06-10 8:21 UTC (permalink / raw)
To: Libre-RISCV General Development
There's lots of good quotes about Rust:
https://stackoverflow.blog/2020/06/05/why-the-developers-who-use-rust-love-it-so-much/?cb=1
I particularly like this quote (italics translated to asterisks):
> daboross: “As a library author, the complex trait/generic system means I
can craft intricate, yet easy to use interfaces. These interfaces *cannot
be used incorrectly*, which means I don’t have to perform runtime checks,
and my users don’t have to even *think* about problem cases, because they
*can’t write them*.
I definitely agree, and the lack of good interfaces is one of my biggest
pain points with Python.
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
* [libre-riscv-dev] [Bug 324] create POWER9 DIV pipeline
From: bugzilla-daemon @ 2020-06-10 11:00 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-324-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=324
--- Comment #9 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jacob Lifshay from comment #8)
> Created the setup stage that translates from the input data to the format
> expected by DivPipeCore but didn't create tests yet, am going to be done for
> today. Still have to double check that I got the number of fractional bits
> correct.
fantastic. as you can probably see i'm slowly going through the
test_pipe_caller.py code removing code-duplication. for now i recommend
cookie-cutting fu/alu/test_pipe_caller.py in its entirety, because i
noticed that these use OE/Rc.
* divdu RT,RA,RB (OE=0 Rc=0)
Special Registers Altered:
CR0 (if Rc=1)
SO OV OV32 (if OE=1)
that means they're exactly like fixedarith, for *both* input and output
data, so you can straight-cookie-cut alu test_pipe_caller.py
i will drop in an fu/compunits/test/test_div_compunit.py
--
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] AMD ISAs
From: Luke Kenneth Casson Leighton @ 2020-06-10 11:28 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <61B9CEC8-2BDB-472C-B426-217736E803CE@gatech.edu>
On Wed, Jun 10, 2020 at 1:59 AM Yehowshua <yimmanuel3@gatech.edu> wrote:
> > Also, that would defeat the purpose of a lot of what we're implementing
> > with a Power compatible ISA, having the CPU and GPU be the same processor,
> > and having an extensible design such that someone could add their own
> > custom operations on top of our code if they wanted.
>
> Noted. Well, it was an interesting idea while it lasted.
it's worth going over. in a similar way, we exhaustively evaluated
different ISAs to consider: MIPS, OpenRISC1200, and so on. AMDGPU did
have the advantage of MIAOW being a subset implementation of that ISA:
still as you can see it's not enough, because of the strong
simplification advantages of a hybrid CPU.
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 324] create POWER9 DIV pipeline
From: bugzilla-daemon @ 2020-06-10 11:32 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-324-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=324
--- Comment #10 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Luke Kenneth Casson Leighton from comment #9)
> that means they're exactly like fixedarith, for *both* input and output
> data, so you can straight-cookie-cut alu test_pipe_caller.py
dropped in a copy for you (the one that was there already needed
updating).
--
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] why developers love rust on stackoverflow blog
From: Luke Kenneth Casson Leighton @ 2020-06-10 12:06 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD7hs6uom2a161ikAb_p3HzLsd_WbNoKE+EMwYH5jYdkVw@mail.gmail.com>
On Wed, Jun 10, 2020 at 9:22 AM Jacob Lifshay <programmerjake@gmail.com> wrote:
> I definitely agree, and the lack of good interfaces is one of my biggest
> pain points with Python.
yep. except... in a large well-maintained collaborative and useful
project, you need unit tests, regardless of what language the code is
in.
and if that language is python, well-written and properly
comprehensive unit tests will inherently find you any interface
problems pretty much instantly - just not at compile-time, because
there isn't one [except if you use cython].
and if they're _not_ found, that's indicative of a failure of the
whole team - including the contributing userbase - to write (or
contribute) sufficiently comprehensive unit tests. *not* of the
language itself.
rust, i get it: there's a strong reliance on the compiler, and on the
definition of types, in ways that have not been done in other
langugages. in my mind, the alarm bells there are to imagine that
because the language provides that safety net, therefore
"automatically unit tests are not necessary to write, because the
compiler will catch everything for me".
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] why developers love rust on stackoverflow blog
From: Luke Kenneth Casson Leighton @ 2020-06-10 12:44 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDxRMgb0ge+uErC+zjepjKtwDKyzk7KqahEvLatyP7Zziw@mail.gmail.com>
On Wed, Jun 10, 2020 at 1:06 PM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
> rust, i get it: there's a strong reliance on the compiler, and on the
> definition of types, in ways that have not been done in other
> langugages.
which has me thinking: is there any way that we could improve things
for python... however _without_ interfering with the code-compactness,
readability and speed of initial development?
one thing i noticed with python type-checking: i found it to be an
absolute nuisance - a hindrance far greater than its value.
the increased function definitions and type definitions frequently
require functions to be expanded from a single horizontal line into a
vertical multi-line definition, running the definition off the page.
the typechecking itself often means that using the Liskov Substitution
Principle is interfered with, because the initial declaration of the
types no longer fit the use to which the over-rides are put.
of course, that *is* the whole point of having the type-checking: to
ensure that the types of base classes and LSP *are* declared!
so i have no clue, here.
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 09jun2020
From: Luke Kenneth Casson Leighton @ 2020-06-10 13:16 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <AA873F66-49EE-44AA-AB63-3EC496CCF1DA@getmailspring.com>
> On Jun 9 2020, at 2:48 pm, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> Thank you, I appreciate the walkthrough and the story about going the
> old fashioned paper way. I thought that I had to do something in qemu
> itself, which would have been outside the bounds of this deductive
> reasoning process, as I have a tendency to get lost in forums and
> documentation when dealing with complex, always buggy to some extent,
> software like qemu.
hence the discussion in the bugreport (which you raised a couple days
ago?) about running actually against a POWER9 native. skipping qemu
and running the programs directly, calling gdb on them. exactly how
we'll do that, i have no idea yet, because it may require a huge
runtime, or possibly even virtualisation (to be able to run bare-metal
binaries directly). have to see.
> So I wanted to see if we had prior art pertaining to
> qemu simulation. I think I should have taken the deductive reasoning
> about the codebase approch for my other questions.
it took me several years to work it out.
> I'm fighting my "aaah
> I don't understand," and with your reminder and guide here will be able
> to do so better next time.
>
> > powerpc64-linux-gnu-gdb -interpreter=mi
> > ~-data-list-register-names
> > ^done,register-names=
> >["r0","r1","r2","r3","r4","r5","r6","r7","r8","r9","r10","r11","r12","r13","r14","r15","r16","r17","r18","r19","r20","r21","r22","r23","r24","r25","r26","r27","r28","r29","r30","r31","f0","f1","f2","f3","f4","f5","f6","f7","f8","f9","f10","f11","f12","f13","f14","f15","f16","f17","f18","f19","f20","f21","f22","f23","f24","f25","f26","f27","f28","f29","f30","f31","pc","msr","cnd","lr","cnt","xer","fpscr","mq"
>
> > ah HA! one of those is the condition register!
>
> Very cool and helpful.
i added them to test_sim.py - it causes test_sim.py unit tests to fail
(not your problem) because qemu defaults CR to 0x20000002 at start-up.
we can "fix" that by initialising the simulator CR to the same value.
> I think I over-stressed my self while working on
> the presentation yesterday, which has caused me to inadvertantly 'take'
> today off.
been there... :)
_______________________________________________
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 361] all test_pipe_caller.py needs RA=0 tests
From: bugzilla-daemon @ 2020-06-10 13:26 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-361-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=361
--- Comment #1 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
in ALUHelpers, (fu/test/common.py) immediate-zero checking is also needed
--
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 10jun2020
From: Luke Kenneth Casson Leighton @ 2020-06-10 13:30 UTC (permalink / raw)
To: Libre-RISCV General Development
yesterday:
* started on L0CacheBuffer and LenExpander, need to offset / shift /
mask LD/ST data
* added means to get CR/XER etc to test_sim.py (qemu-simulator comparator)
today:
* started code-morph of */test_pipe_caller.py and test_*_compunit.py
to get them to use common code. ultimately to be able to separate sim
and HDL to behind a common API (then add qemu and native execution as
well)
later:
* more on L0CacheBuffer.
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 10jun2020
From: Tobias Platen @ 2020-06-10 13:42 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <CAPweEDyVXouopWhf3scdPC-JOWA5iaB-27aQDgaW-yaAH2vVNw@mail.gmail.com>
morning: nothing
now: working on LDSTSplitter
_______________________________________________
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 184] new mailing lists proposal for libre-soc.org
From: bugzilla-daemon @ 2020-06-10 13:53 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-184-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=184
--- Comment #20 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
just checking by subscribing to libre-soc-misc, should they be
libre-soc-misc@lists.libre-soc.org
or
libre-soc-misc@libre-soc.org
i kiiinda prefer the convention of a separate domain name
--
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 371] code removed by commit 12297566322355ce5fed2e2a5460bea54f69e79e
From: bugzilla-daemon @ 2020-06-10 14:22 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-371-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=371
Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|FIXED |---
Status|RESOLVED |IN_PROGRESS
--- Comment #6 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Tobias Platen from comment #5)
> I changed my editor settings to that it that auto-detects when a file was
> changed by an external program.
great.
can you also restore this:
class DataMergerRecord(Record):
"""
{data: 128 bit, byte_enable: 16 bit}
"""
def __init__(self, name=None):
layout = (('data', 128),
('en', 16))
Record.__init__(self, Layout(layout), name=name)
#FIXME: make resetless
--
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 371] code removed by commit 12297566322355ce5fed2e2a5460bea54f69e79e
From: bugzilla-daemon @ 2020-06-10 14:34 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-371-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=371
--- Comment #7 from Tobias Platen <libre-soc@platen-software.de> ---
those lines are already present in the code, at least on my local code which I
recently git pulled.
--
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 371] code removed by commit 12297566322355ce5fed2e2a5460bea54f69e79e
From: bugzilla-daemon @ 2020-06-10 14:39 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-371-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=371
--- Comment #8 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Tobias Platen from comment #7)
> those lines are already present in the code, at least on my local code which
> I recently git pulled.
yes. which means that you overwrote some code which is *not* present.
can you please carefully examine the commit and restore all of the code.
also, i am reverting the recent commit because it does not work.
from soc.scoreboard.addr_split import LDSTSplitter
ImportError: cannot import name 'LDSTSplitter' from 'soc.scoreboard.addr_split'
(/home/lkcl/src/libresoc/soc/src/soc/scoreboard/addr_split.py)
--
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 371] code removed by commit 12297566322355ce5fed2e2a5460bea54f69e79e
From: bugzilla-daemon @ 2020-06-10 14:40 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-371-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=371
Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|IN_PROGRESS |RESOLVED
Resolution|--- |FIXED
--- Comment #9 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
excellent, you found it. closing again.
--
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] why developers love rust on stackoverflow blog
From: Hendrik Boom @ 2020-06-10 15:09 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <CAPweEDyyM0gyeGj_Aq3_jhokBCQWA_dw7cFaZfNOT-T7Q_J1CQ@mail.gmail.com>
On Wed, Jun 10, 2020 at 01:44:46PM +0100, Luke Kenneth Casson Leighton wrote:
> On Wed, Jun 10, 2020 at 1:06 PM Luke Kenneth Casson Leighton
> <lkcl@lkcl.net> wrote:
>
> > rust, i get it: there's a strong reliance on the compiler, and on the
> > definition of types, in ways that have not been done in other
> > langugages.
>
> which has me thinking: is there any way that we could improve things
> for python... however _without_ interfering with the code-compactness,
> readability and speed of initial development?
There is definitely a trade-off between speed of initial development and speed of
development.
-- 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
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