Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
* Re: [libre-riscv-dev] LD/ST now a bit better. extra NLNet budgets
From: Luke Kenneth Casson Leighton @ 2020-06-11 19:41 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <ABC5750B-6FEB-429B-A3DE-5DCC95C0574E@gatech.edu>

On Thursday, June 11, 2020, Yehowshua <yimmanuel3@gatech.edu> wrote:

> >
> > a full half of that first EUR 50,000 budget was allocated to
> > Kazan.
>
> On the note of Kazan, what is currently being done there?


nothing for the moment as we need all hands that have some nmigen
experience on the POWER9 core.


> I contacted Anton from Embox, he worked on the Etna-viv drivers
> and he recently joined the mailing list.
>
> Anton, don’t be shy to say hi :)


hi anton, great to know you're around, we have a budget for 3D driver work
if you're interested?

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

* Re: [libre-riscv-dev] LD/ST now a bit better. extra NLNet budgets
From: Yehowshua @ 2020-06-11 19:32 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDztP=w8qcBc8SiDX8O7WGOcMAsRQY4ibea=hoBzvzJbXg@mail.gmail.com>

> 
> a full half of that first EUR 50,000 budget was allocated to
> Kazan.

On the note of Kazan, what is currently being done there?
I contacted Anton from Embox, he worked on the Etna-viv drivers 
and he recently joined the mailing list.

Anton, don’t be shy to say hi :)

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

* [libre-riscv-dev] LD/ST now a bit better. extra NLNet budgets
From: Luke Kenneth Casson Leighton @ 2020-06-11 19:18 UTC (permalink / raw)
  To: Libre-RISCV General Development

hi folks,

i have the LD/ST CompUnit FSM closer to acceptably operational.  i had
to add some very bad hacks in to get it to work, and also into the
L0CacheBuffer.  luckily the prototype L0CacheBuffer is not intended
for heavy production, it's there as a stop-gap measure.

also we have three additional tasks that have been verbally approved,
kindly, by Michiel from NLNet:

* nmigen and yosys funding: EUR 10,000
* POWER9 core funding: EUR 8,000
* SoC Documentation funding: EUR 6,000

we were running particularly low on the development of the POWER9
core, because (a) it is more complex than RV64GC (b) the core is
covered by the original (first) NLNet Grant, applied for in Nov 2018,
and (c) a full half of that first EUR 50,000 budget was allocated to
Kazan.

this is good news for everyone who has completed tasks in the past 2
months on the POWER9 core because now it will be possible (once the
MoU is signed) to give you donations for completing them.

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 11jun2020
From: Luke Kenneth Casson Leighton @ 2020-06-11 17:38 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <20200611182707.6a39dbeddfcdbc8a506e8223@platen-software.de>

On Thursday, June 11, 2020, Tobias Platen <libre-soc@platen-software.de>
wrote:

> today: reading src/soc/scoreboard/addr_split.py and thinking how to
> imlement memory interface


look up what i wrote yesterday, i recommended expanding the existing
LDSTSplitter from bits to bytes.

it was accidental that it did bits of data :)



> tomorrow: nothing (I won't be at home tomorrow)
>
> --
> Tobias Platen <libre-soc[at]platen-software[dot]de>
>
> _______________________________________________
> libre-riscv-dev mailing list
> libre-riscv-dev@lists.libre-riscv.org
> http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
>


-- 
---
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

* Re: [libre-riscv-dev] daily kan-ban update 11jun2020
From: Tobias Platen @ 2020-06-11 16:27 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <CAPweEDx6Ztom8Phya75UioMGRcf1aVWnNhK=L1fp7rKKmQ-YqQ@mail.gmail.com>

today: reading src/soc/scoreboard/addr_split.py and thinking how to imlement memory interface
tomorrow: nothing (I won't be at home tomorrow)

-- 
Tobias Platen <libre-soc[at]platen-software[dot]de>

_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] daily kan-ban update 11jun2020
From: Luke Kenneth Casson Leighton @ 2020-06-11 15:59 UTC (permalink / raw)
  To: Libre-RISCV General Development

today:

dealing with yet more complexity in CompALUMulti and investigating ST
followed by LD issues in LDSTCompUnit

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

* Re: [libre-riscv-dev] daily kan-ban update 10jun2020
From: Jacob Lifshay @ 2020-06-11  3:43 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDyVXouopWhf3scdPC-JOWA5iaB-27aQDgaW-yaAH2vVNw@mail.gmail.com>

yesterday:
created setup stage of div pipeline
today:
working on div pipeline

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 10jun2020
From: Luke Kenneth Casson Leighton @ 2020-06-10 23:07 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <20200610154208.6149ece519d76954f1dd9fa1@platen-software.de>

On Wednesday, June 10, 2020, Tobias Platen <libre-soc@platen-software.de>
wrote:

> morning: nothing
> now: working on LDSTSplitter


tobias: my recommendation is, look at adding the 2nd argument to LenExpand
(cover=8) in LDSTSplitter, and multiply the bitwidth of the data in/out by 8

you can use LenExpand.rexp_o as a byte mask where appropriate.

basically the idea is to turn LDSTSplitter from its embarrassing splitting
of *bits* of data into dealing with *bytes* of data.

the actual FSM is perfectly functional.

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

* Re: [libre-riscv-dev] why developers love rust on stackoverflow blog
From: Hendrik Boom @ 2020-06-10 22:35 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <C74C65BE-A62C-4C1B-BE13-4BAFBA10A7EF@getmailspring.com>

On Wed, Jun 10, 2020 at 02:28:31PM -0700, Cole Poirier wrote:
> As someone who's only been programming for ~2-3 years, I actually find
> rust much, much easier to use than python, because it's complier
> assisted programming. Dramitically easier for someone like myself with
> so little 'blank-page' programming experience to both get started and be
> productive long term. And oh the types, so beautiful, yet so much more
> productive and easy for me than 'typeless' python, as jacob mentioned above.

I learned to appreciate static typing when I was writing complex data 
structures in PL/1 in the 1960's -- it didn't have it.  A pointer was a 
pointer, and it would just believe it pointed to whatever you said it 
pointed to when you used it.

A learned to *love* statis typing when  got to use Algol 68 a few years 
later, in the mid 1070's..

It was a long time before I had it available to me again.  
I found it again in Modula 3.

-- hendrik

> 
> Cole
> 
> _______________________________________________
> 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 373] New: Investigate the possibility of implementing parts of OPENCAPI to supplement Wisbone vB4
From: bugzilla-daemon @ 2020-06-10 22:25 UTC (permalink / raw)
  To: libre-riscv-dev

https://bugs.libre-soc.org/show_bug.cgi?id=373

            Bug ID: 373
           Summary: Investigate the possibility of implementing parts of
                    OPENCAPI to supplement Wisbone vB4
           Product: Libre-SOC's first SoC
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: CONFIRMED
          Severity: enhancement
          Priority: ---
         Component: Specification
          Assignee: lkcl@lkcl.net
          Reporter: colepoirier@gmail.com
                CC: libre-riscv-dev@lists.libre-riscv.org
   NLnet milestone: ---

> I have an ignorant question about wishbone. Is it possible that there is
> functionality in OpenCAPI that would be beneficial to extend wishbone
> with, and not time prohibitive (not for Oct 2020 tapeout but for the
> quad-core gpu capable version)? This is assuming that implementing a
> part of OpenCAPI in wishbone is legally permitted, which I am also
> ignorant of.

http://lists.libre-riscv.org/pipermail/libre-riscv-dev/2020-June/007972.html

-- 
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] wishbone does not have byte-enable (but it does have user-tags)
From: Luke Kenneth Casson Leighton @ 2020-06-10 21:50 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <1BB14FE2-03DB-4CA5-B07A-D4EFCAE64D15@getmailspring.com>

On Wed, Jun 10, 2020 at 10:33 PM Cole Poirier <colepoirier@gmail.com> wrote:
>
> On Jun 9 2020, at 1:17 pm, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> > On Tue, Jun 9, 2020 at 8:18 PM Cole Poirier <colepoirier@gmail.com> wrote:
> >> I have an ignorant question about wishbone. Is it possible that there is
> >> functionality in OpenCAPI that would be beneficial to extend wishbone
> >> with,
> >
> > honestly absolutely no idea.  someone else might know.
>
> Worth me raising a new bug report about this? Potentially for a deferred
> discussion on comp.arch or with some POWER devs?

yes good idea.

_______________________________________________
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] wishbone does not have byte-enable (but it does have user-tags)
From: Cole Poirier @ 2020-06-10 21:33 UTC (permalink / raw)
  To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAPweEDxjXcJUNACMx7d73LT1fJV3+fw1anEcG8GXqaiH=Z+oUA@mail.gmail.com>

On Jun 9 2020, at 1:17 pm, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> On Tue, Jun 9, 2020 at 8:18 PM Cole Poirier <colepoirier@gmail.com> wrote:
>> I have an ignorant question about wishbone. Is it possible that there is
>> functionality in OpenCAPI that would be beneficial to extend wishbone
>> with,
> 
> honestly absolutely no idea.  someone else might know.

Worth me raising a new bug report about this? Potentially for a deferred
discussion on comp.arch or with some POWER devs?

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] Fwd: programmerjake mentioned you in Intel Details Lakefield With Hybrid Technology
From: Cole Poirier @ 2020-06-10 21:32 UTC (permalink / raw)
  To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAPweEDy5_MQ8Hwtja4VZ3dceXxZUEvOKN752B8=f=VbufVh8Mg@mail.gmail.com>

> Dear lkcl,
> 
> programmerjake has mentioned you in a post.
>
> 800MHz base clock? that's slow enough that it might be comparable to
> Libre-SOC's quadcore processor in multithreaded performance!
> [USER="27541"]lkcl[/

Wouldn't that be something?! To beat intel's low-end low-power
processors on our first product!

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] daily kan-ban update 09jun2020
From: Cole Poirier @ 2020-06-10 21:30 UTC (permalink / raw)
  To: Libre-RISCV General Development; +Cc: libre-riscv-dev
In-Reply-To: <12b09b34-68d9-5b10-d2fb-8948802698e8@gmail.com>

On Jun 10 2020, at 11:53 am, Michael Nolan <mtnolan2640@gmail.com> wrote:
> While I don't remember exactly how I did it, I think I placed a 
> breakpoint on the instruction after the end of the program and had
> qemu 
> continue until it hit the breakpoint. Since trapping will never
> trigger 
> that breakpoint I don't know what will happen. I suspect it will
> require 
> a more creative solution though.

Thanks for the insight Michael!!

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] why developers love rust on stackoverflow blog
From: Cole Poirier @ 2020-06-10 21:28 UTC (permalink / raw)
  To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAC2bXD50xqgk=cX5oO3E_JOSaA+_S=O5PtFMPGT2wYbCUxc0tw@mail.gmail.com>

As someone who's only been programming for ~2-3 years, I actually find
rust much, much easier to use than python, because it's complier
assisted programming. Dramitically easier for someone like myself with
so little 'blank-page' programming experience to both get started and be
productive long term. And oh the types, so beautiful, yet so much more
productive and easy for me than 'typeless' python, as jacob mentioned above.

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 184] new mailing lists proposal for libre-soc.org
From: bugzilla-daemon @ 2020-06-10 21:25 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 #21 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #20)
> 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

I Agree. I prefer libre-soc-misc@libre-soc.org

-- 
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] daily kan-ban update 10jun2020
From: Cole Poirier @ 2020-06-10 21:23 UTC (permalink / raw)
  To: Libre-RISCV General Development; +Cc: libre-riscv-dev
In-Reply-To: <20200610154208.6149ece519d76954f1dd9fa1@platen-software.de>

Yesterday: Only emails and commenting on bug reports

Today: Work on TRAP pipeline unit tests

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] Fwd: programmerjake mentioned you in Intel Details Lakefield With Hybrid Technology
From: lkcl . @ 2020-06-10 20:43 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <20200610185137.600051a0e337@www.phoronix.com>

interesting! and very funny :)

---------- Forwarded message ----------
From: *Phoronix Forums* <phoronix@phoronix.com>
Date: Wednesday, June 10, 2020
Subject: programmerjake mentioned you in Intel Details Lakefield With
Hybrid Technology
To: luke.leighton@gmail.com


Dear lkcl,

programmerjake has mentioned you in a post.

The discussion is located at:
https://www.phoronix.com/forums/node/1185648

Here is the message that has been posted:
***************
800MHz base clock? that's slow enough that it might be comparable to
Libre-SOC's quadcore processor in multithreaded performance!
[USER="27541"]lkcl[/
***************

All the best,
Phoronix Forums

To unsubscribe from this topic, please visit this page:
https://www.phoronix.com/forums/member/27541/subscriptions
_______________________________________________
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: Michael Nolan @ 2020-06-10 18:53 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <CAPweEDxTQS-h-uqTfPkpfLmisMOpE7RL-F0bMLpw-510nNTeeg@mail.gmail.com>

On 6/9/20 5:48 PM, Luke Kenneth Casson Leighton wrote:
>
> 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.

While I don't remember exactly how I did it, I think I placed a 
breakpoint on the instruction after the end of the program and had qemu 
continue until it hit the breakpoint. Since trapping will never trigger 
that breakpoint I don't know what will happen. I suspect it will require 
a more creative solution though.

--Michael


_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] [Bug 324] create POWER9 DIV pipeline
From: Jacob Lifshay @ 2020-06-10 18:29 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <bug-324-13-VE2bmwYKAL@https.bugs.libre-soc.org/>

On Wed, Jun 10, 2020, 04:33 <bugzilla-daemon@libre-soc.org> wrote:

> 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).
>

Thanks!

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] why developers love rust on stackoverflow blog
From: Jacob Lifshay @ 2020-06-10 18:24 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDxRMgb0ge+uErC+zjepjKtwDKyzk7KqahEvLatyP7Zziw@mail.gmail.com>

On Wed, Jun 10, 2020, 05:07 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:

> 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.
>

agreed, however unit tests can't catch everything except in trivial cases
or maybe languages where they use typing to limit the number of possible
inputs to a testable level.

>
> 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].
>

it will potentially find interface problems, however, it definitely won't
find problems where someone is misusing an interface in ways that don't
cause the tests to visibly fail, which is much more likely with Python than
with Rust.

There is also the factor that in a large and complex codebase such as
libre-soc's that is often lacking in documenting the expected types
everywhere, you often have to look through several files before you can
figure out what interface that some variable in the code your writing
conforms to. That was certainly the case for me when trying to figure out
what fields are included and what they mean for self.i.ctx.op, since there
was so much indirection that pyls wasn't able to give very useful
information, it thought op was a Signal since it didn't realize opkls was
set. At least in Rust, you have to define which traits your types implement
(basically a codified version of what interfaces you're allowed to use in
whatever code is using that type, that even applies to type variables in
generic contexts), also the compiler knows which concrete types are used
everywhere, so you can easily look up the type's definition, even for
autogenerated code.

>
> 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.
>

there is a practical limit on how many unit tests there can be, at some
point, you just have to give up on testing all possible edge cases for any
non-trivial code. Having the compiler prove at compile time that some
conditions are met (yes, the type system is Turing complete) by all code
that calls your functions or uses your types definitely makes it easier to
know that your code will work.

>
> 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".
>

the compiler will catch quite a lot, however there is still a strong focus
on unit tests -- the language is designed to make writing unit tests really
easy:
just decorate a test function with #[test] and it will be automatically
added to the list of tests that the build tools will run. Additionally, the
build tools will automatically compile and test all example code in the doc
comments, each code example can be set to run as a normal doc test, a test
that code shouldn't compile (the build tools will verify it produces a
compile error), or code that the compiler should ignore for some reason
(such as not being written in Rust). There are also several other supported
testing methods that aren't used as often. You can also use a little macro
magic to test example code in external markdown documentation using the
same doc test magic. I use that macro stuff in the algebraics library to
test the example code in the README.md file:
https://salsa.debian.org/Kazan-team/algebraics/-/blob/v0.2.0/src/lib.rs#L21

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] LDST compunit semi operational
From: Luke Kenneth Casson Leighton @ 2020-06-10 17:27 UTC (permalink / raw)
  To: Libre-RISCV General Development

i've managed to get the addresses split into LSBs and MSBs, and use the
lower 3 bits in conjunction with the Data Length for a bitmap mask on
writing, and as a corresponding bytemap mask for read.

this via the dummy / nonproduction L0CacheBuffer, which does not cope with
misalignment crossing a 64 bit boundary.

fortunately, nmigen Memory can be passed an *array* of write-enable lines,
and so can wishbone.

i could really use some help on this code as it is particularly complex and
also critical to get right.

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 318] fix LDSTCompUnit
From: bugzilla-daemon @ 2020-06-10 17:20 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-318-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=318

--- Comment #23 from Cesar Strauss <cestrauss@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #22)
> can you take a look when you have a moment?  it may just be the case
> that TstL0CacheBuffer needs to be initialised with the right parameters,
> to give it a 64-bit width rather than the current (old) values of only
> a 16-bit underlying memory.

Sure, I'll start later today.
As it happens, tomorrow is a holiday.
I'll have the full day free to work on the project.

-- 
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 318] fix LDSTCompUnit
From: bugzilla-daemon @ 2020-06-10 16:44 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-318-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=318

--- Comment #22 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
cesar, hi,

i've managed to get L0CacheBuffer semi-operational: it won't cope
with mis-aligned LD/ST.  the boundary (memory granularity) is 64-bit,
and if you try to read 8 bytes that are starting 32-bits in, that'll
fail.

but... that's not the issue that needs looking at (because it's to
be sorted for when we have the DualPortSplitter).

the issue that needs looking at is to confirm that compldst_multi.py's
unit tests are properly functional: i'm just not confident that they
are.

can you take a look when you have a moment?  it may just be the case
that TstL0CacheBuffer needs to be initialised with the right parameters,
to give it a 64-bit width rather than the current (old) values of only
a 16-bit underlying memory.

-- 
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:   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