Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
* [libre-riscv-dev] IMPORTANT - PLEASE REMOVE AND RE-CHECKOUT CROWDSUPPLY REPOSITORY Re: crowdsupply updates
From: Luke Kenneth Casson Leighton @ 2020-04-01 16:08 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDz9NCTWQp1ZGpuKWejdaGvM6Y=fHzzdk4HNs13SPMmzYQ@mail.gmail.com>

On Wed, Apr 1, 2020 at 5:02 PM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:

> when i have done so please can everyone destroy their working copy of
> the crowdsupply repository, re-checking-out a new one.

ok that's done: i had to edit the bare repository master file,
refs/head/master, to get it to "listen".  this could have resulted in
corruption of the wiki.

if you have write access, please ensure that you check out a NEW copy
of the crowdsupply git repository, otherwise if you did a "git pull"
recently it will be the *wrong master* and will cause massive
problems.

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] crowdsupply updates
From: Luke Kenneth Casson Leighton @ 2020-04-01 16:14 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDz9NCTWQp1ZGpuKWejdaGvM6Y=fHzzdk4HNs13SPMmzYQ@mail.gmail.com>

On Wed, Apr 1, 2020 at 5:02 PM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:

> https://libre-riscv.org/index/Updates/March_2020/
>
> yehowshua i removed the update because it wasn't discussed.

please, please, don't put the contents of crowdsupply updates onto the
website.  yes create *links* to the updates (and a copy of the
summary) *when they are published*, and also, for drafts, put a
warning, " preliminary: this is a draft, being edited, NOT PUBLISHED"
message (and link to the source) but please, really, *do not* put the
actual contents on the wiki.

firstly, they're duplicates.  which one gets edited?  which is the
canonical version?

secondly, it makes crowdsupply look "unimportant"

thirdly, joshua has - a number of times - seen updates that i've
written elsewhere, and silently *not published what i wrote* on
crowdsupply, as a result.  this is perfectly reasonable of him to
decide to do.

fourthly, the website does *not* have an associated "updates mailing
list".  there's something like 600 subscribers to the crowdsupply
pre-launch campaign, and if the page goes onto the wiki, we *do not
get a notification sent out to all those 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] crowdsupply updates
From: Immanuel, Yehowshua U @ 2020-04-01 16:18 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwePf-d8HuLwBfkAVLASN=0_Y-e2PN==KMd-O4VqgQs+Q@mail.gmail.com>

I had meant to remove it yesterday.

My apologies,
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] [Bug 274] New: Investigate how BSV performs Formal Verification and what can be Applied to FPUs
From: bugzilla-daemon @ 2020-04-01 16:26 UTC (permalink / raw)
  To: libre-riscv-dev

http://bugs.libre-riscv.org/show_bug.cgi?id=274

            Bug ID: 274
           Summary: Investigate how BSV performs Formal Verification and
                    what can be Applied to FPUs
           Product: Libre-SOC's first SoC
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: CONFIRMED
          Severity: minor
          Priority: ---
         Component: Formal Verification
          Assignee: lkcl@lkcl.net
          Reporter: yimmanuel3@gatech.edu
                CC: libre-riscv-dev@lists.libre-riscv.org
   NLnet milestone: ---

I believe BSV can generate formally verified adders.
I will soon take a look at how it handles formal verification.
This is mainly a research/investigation bug.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] crowdsupply updates
From: Immanuel, Yehowshua U @ 2020-04-01 16:33 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <D53B3AD5-1260-43AB-B830-F07F5A955A6E@gatech.edu>

On this note however, do you think its a good idea to put a link to crowd supply?

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] POWER simulator
From: Immanuel, Yehowshua U @ 2020-04-01 17:04 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDyxqCXF8wuV36WWeML_wPSPA8KoSYgRP3uGxigKtSzc2g@mail.gmail.com>

I’m guessing this is in reference to parsing the PDF?
As in - what we should expect labor-wise?

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] name change announcement on crowdsupply
From: Jacob Lifshay @ 2020-04-01 17:31 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwGR75mkCPBb8Q2T8mAQOr7r-C=Hds=yBU-3ABgB=mohA@mail.gmail.com>

On Wed, Apr 1, 2020, 03:58 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:

> On Wed, Apr 1, 2020 at 2:51 AM Jacob Lifshay <programmerjake@gmail.com>
> wrote:
>
> > On Tue, Mar 31, 2020 at 11:15 AM Luke Kenneth Casson Leighton
> > <lkcl@lkcl.net> wrote:
> > >
> > > 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"?
> >
> > I moved the example code to the Kazan repo.
>
> great
>
> > I did notice that we *forgot* to announce we changed our name from
> > Libre-RISCV to Libre-SOC on any crowdsupply updates -- we should do
> > that and change the crowdsupply description page to match.
>
> that'll be tricky, the url has to stay the same.  changing
> description, yes should be ok.
>

Wouldn't it work for the old url to just redirect to the new one? We can
ask if they support that.

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] crowdsupply updates
From: Luke Kenneth Casson Leighton @ 2020-04-01 17:39 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <F73D0B9C-DE54-4C41-B445-7AA114E6047F@gatech.edu>

On Wed, Apr 1, 2020 at 5:33 PM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:
>
> On this note however, do you think its a good idea to put a link to crowd supply?

yehyeh, i like the idea of the summaries and links to CS.
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] POWER simulator
From: Luke Kenneth Casson Leighton @ 2020-04-01 17:43 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <D76B1FAB-2F89-4E7F-8478-EBA92E63EB03@gatech.edu>

On Wed, Apr 1, 2020 at 6:05 PM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:
>
> I’m guessing this is in reference to parsing the PDF?

yep.  https://libre-riscv.org/openpower/isa/

> As in - what we should expect labor-wise?

took about 5 hours but there's now information missing, i cut too much out.

the  parser took about a day to get into shape.

putting in the decoder and a prototype regfile, another day.

first succesful instruction was today.

estimated... maybe... 3-4 more days and we should have the complete
set of integer instructions done.  not speed-optimised at all.

quirks such as what various SPRs mean and do, maybe another 2-3 days.

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] name change announcement on crowdsupply
From: Luke Kenneth Casson Leighton @ 2020-04-01 17:44 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD6tSrS0ctTXjmkgae7gvjLLq_PE4GyLEgy4msna-G4sGw@mail.gmail.com>

On Wed, Apr 1, 2020 at 6:31 PM Jacob Lifshay <programmerjake@gmail.com> wrote:

> Wouldn't it work for the old url to just redirect to the new one? We can
> ask if they support that.

will get a chance soon.

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] IMPORTANT - PLEASE REMOVE AND RE-CHECKOUT CROWDSUPPLY REPOSITORY Re: crowdsupply updates
From: Jacob Lifshay @ 2020-04-01 17:50 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDxHFmMGr4X6Hchyr_EH5=OBNjR_ZHVP+2mbR4ZSZ_9cJA@mail.gmail.com>

On Wed, Apr 1, 2020, 09:09 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:

> On Wed, Apr 1, 2020 at 5:02 PM Luke Kenneth Casson Leighton
> <lkcl@lkcl.net> wrote:
>
> > when i have done so please can everyone destroy their working copy of
> > the crowdsupply repository, re-checking-out a new one.
>
> ok that's done: i had to edit the bare repository master file,
> refs/head/master, to get it to "listen".  this could have resulted in
> corruption of the wiki.
>
> if you have write access, please ensure that you check out a NEW copy
> of the crowdsupply git repository, otherwise if you did a "git pull"
> recently it will be the *wrong master* and will cause massive
> problems.
>

Apparently, my master is at the same commit as the master on
https://git.libre-riscv.org/?p=crowdsupply.git;a=summary so I won't need to
re-clone.

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] IMPORTANT - PLEASE REMOVE AND RE-CHECKOUT CROWDSUPPLY REPOSITORY Re: crowdsupply updates
From: Luke Kenneth Casson Leighton @ 2020-04-01 17:59 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD4rvwU7-ZHBGXDq8o3QyyX9fTzFTYAoX51DGoeec0VBXw@mail.gmail.com>

On Wed, Apr 1, 2020 at 6:50 PM Jacob Lifshay <programmerjake@gmail.com> wrote:

> Apparently, my master is at the same commit as the master on
> https://git.libre-riscv.org/?p=crowdsupply.git;a=summary so I won't need to
> re-clone.

yes if you didn't git pull today it's fine.

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-04-01 18:40 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 #13 from Michael Nolan <mtnolan2640@gmail.com> ---
I've got something in decoder/selectable_int.py. It uses Power's bit ordering
so it should be good for the compiler but something to be aware of if it's used
anywhere else.

I'm not sure what to do about left shift and right shift. Should SelectableInt
(0x10, bits=8) << 4 equal SelectableInt(0x100, bits=12) or SelectableInt(0x00,
bits=8)

It's also unsigned only, I'm not sure how much that matters right now

-- 
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-04-01 19: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

Jacob Lifshay <programmerjake@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |programmerjake@gmail.com

--- Comment #14 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to Michael Nolan from comment #13)
> I've got something in decoder/selectable_int.py. It uses Power's bit
> ordering so it should be good for the compiler but something to be aware of
> if it's used anywhere else.
> 
> I'm not sure what to do about left shift and right shift. Should
> SelectableInt (0x10, bits=8) << 4 equal SelectableInt(0x100, bits=12) or
> SelectableInt(0x00, bits=8)

I would assume shift left is still shift left. You can check which pseudo-code
gets run by the slw instruction since it's what gcc produces for the <<
operator.

-- 
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-04-01 21:55 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 #15 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from comment #13)
> I've got something in decoder/selectable_int.py. It uses Power's bit
> ordering so it should be good for the compiler but something to be aware of
> if it's used anywhere else.

ahh superb.  ok.

> It's also unsigned only, I'm not sure how much that matters right now

as jacob pointed out, we can find out soon enough.

i do feel that we maay need to put carry-in and carry-out into the
Int class (somehow).  also, perhaps rewrite the pseudo-code fragments
to match those, then propose them back to the OpenPOWER Foundation.

just a thought.

-- 
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-04-01 23:05 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 #16 from Michael Nolan <mtnolan2640@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #15)

> i do feel that we maay need to put carry-in and carry-out into the
> Int class (somehow).  also, perhaps rewrite the pseudo-code fragments
> to match those, then propose them back to the OpenPOWER Foundation.

Carry-in is addressed in the pseudocode, for instance:
adde:

RT <- (RA) + (RB) + CA

However, yes we'll probably need to add carry-out handling to the SelectableInt
class at some point

-- 
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-04-01 23:44 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 #17 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from comment #16)

> Carry-in is addressed in the pseudocode, for instance:
> adde:
> 
> RT <- (RA) + (RB) + CA

oh duh :)

> However, yes we'll probably need to add carry-out handling to the
> SelectableInt class at some point

carry out, yes.

however think ahead to PartitionedSignal.  it becomes more like the unit tests
logic, with multiple incoming carry bits and multiple outgoing carry bits.

this is where it becomes both interesting and also hair-raising to implement
SV.

not least: the regfile gets typecast to a union of arrays of byte, hword, word
and dword.  the "register" RA etc then simply become a pointer to the 64 bit (8
byte) offset into the SRAM of the regfile memory.

but... let's leave that for later :)

-- 
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] April fools pull request for Rust
From: Jacob Lifshay @ 2020-04-02  1:02 UTC (permalink / raw)
  To: Libre-RISCV General Development

Found this funny:

https://github.com/rust-lang/rust/pull/70645
_______________________________________________
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] submitted bugreport to upstream nmigen
From: Jacob Lifshay @ 2020-04-02  3:03 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwTnMvO2Ss1rD+gpoFUKtVKAVP6n_-4aU96doSn1sGgkA@mail.gmail.com>

On Wed, Apr 1, 2020 at 3:16 AM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
>
> On Wednesday, April 1, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> > This is the same issue encountered when trying to add gitlab CI support.
> >
> > https://github.com/nmigen/nmigen/issues/344
>
>
> we may just need to write our own run_simulation function for now.

I created a pull request that hopefully fixes this issue and
whitequark accepted it like 5 min later -- she's fast!

Rerunning nmutil CI build to find the next errors:
https://salsa.debian.org/Kazan-team/nmutil/-/jobs/642930

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] April fools pull request for Rust
From: Luke Kenneth Casson Leighton @ 2020-04-02  8:55 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD4B+K=9rzChHK6VpUwP8gMAxjP8CSG=n+r3FQ-BusEc_A@mail.gmail.com>

---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68

On Thu, Apr 2, 2020 at 2:02 AM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> Found this funny:
>
> https://github.com/rust-lang/rust/pull/70645

"wildly untasteful types", love it :)

_______________________________________________
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] virtual coffee again
From: Luke Kenneth Casson Leighton @ 2020-04-02  8:57 UTC (permalink / raw)
  To: Libre-RISCV General Development

https://openpowerfoundation.org/openpower-virtual-coffee-calls/

remember UTC so calculate without timezones.  0900 UTC and 2200 UTC.
0900 UTC is right now (3 mins)

---
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] virtual coffee again
From: Luke Kenneth Casson Leighton @ 2020-04-02  9:24 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwshY0rdEaEQw615M+MWe4J8QLQ56LLNyU2HwTsfesSqA@mail.gmail.com>

On Thu, Apr 2, 2020 at 9:57 AM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
>
> https://openpowerfoundation.org/openpower-virtual-coffee-calls/
>
> remember UTC so calculate without timezones.  0900 UTC and 2200 UTC.
> 0900 UTC is right now (3 mins)

very short, next one 2200 UTC.  better for USA. *remember it is UTC*
so it is 2300 UK time for example.

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] submitted bugreport to upstream nmigen
From: Luke Kenneth Casson Leighton @ 2020-04-02  9:27 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD4ngnfC14SJOLAsemKPgA79qUzEqqKY+0MK+uavfz_Zsg@mail.gmail.com>

On Thu, Apr 2, 2020 at 4:04 AM Jacob Lifshay <programmerjake@gmail.com> wrote:

> > we may just need to write our own run_simulation function for now.
>
> I created a pull request that hopefully fixes this issue and
> whitequark accepted it like 5 min later -- she's fast!

fantastic to hear that. must contact her and offer some € for nmigen
work.  in particular we need simulation of SR NAND latch and support
for it to output into yosys.

_______________________________________________
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-04-02 10:41 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 #18 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
alriiight, i added it in: just... used it, and it worked!
i did however have to modify EXTZ64 and EXTS64 to get them
to recognise SelectableInt, and, interestingly, was able to
"drop in" the fact that the sign-zero-extended int now has
a bit-width of 64.

-- 
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: Veera @ 2020-04-02 12:52 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <3EFE94C3-B808-47AA-8106-E28982D007F8@gatech.edu>

On Tue, Mar 31, 2020 at 06:02:56PM +0000, Immanuel, Yehowshua U wrote:
> 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

It archived only from when it started. To bring back previous ones we have
to import them from mailman2 mbox archive till date.

Regards,
Veera

_______________________________________________
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