* [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 272] functions needed in POWER simulator which match 3.0B spec
From: bugzilla-daemon @ 2020-03-31 12:57 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 #3 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
these are the functions, listed in 3.0B section 1.4.3 p6 - p7
ABS(x)
BCD_TO_DPD(x)
CEIL(x)
DOUBLE(x)
DPD_TO_BCD(x)
EXTS(x)
FLOOR(x)
GPR(x)
MASK(x, y)
MEM(x, y)
ROTL64(x, y)
ROTL32(x, y)
SINGLE(x)
SPR(x)
there's really not many of them.
--
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 11:42 UTC (permalink / raw)
To: Libre-RISCV General Development, Jean-Paul Chaput,
Marie-Minerve Louërat
In-Reply-To: <CAPweEDzxhDpfv8hH5nJnJn=RCMdVkk5RZAndxvo1z1jd2AQw5Q@mail.gmail.com>
*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.
if you're interested, i can kick some tires and see if there are
people in, say, the GNUStep community (and other locations) willing to
get pyobjc GNUStep support properly working, upstreamed, and suitable
for use as the main "glue" in coriolis2. replacing libboost as well
as Qt [1]
what do you think?
l.
[1] once pyobjc python bindings exist and work, you'd have *immediate*
dynamic runtime access to GNUStep GUI Objective-C bindings. aalllll
of theeeeem. GNUStep GUIs in python using pyobjc would be laughably -
and very unnervingly - trivial. oh and there's a high probability
that they'd also work on macosx, unmodified.
On Tue, Mar 31, 2020 at 10:38 AM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
>
> https://groups.google.com/forum/#!topic/gnu.gnustep.discuss/6QbWfmaMrck
> patches - 8 years ago (damnit, the changelog for 2.0.1 removed it)
>
> you see the sort of thing i mean? there *are* people who understand
> the power of dynamic objective runtime self-describing capability: and
> they're *never properly funded*.
>
> On Tue, Mar 31, 2020 at 10:32 AM Luke Kenneth Casson Leighton
> <lkcl@lkcl.net> wrote:
> >
> > and pyobjc:
> > https://pyobjc.readthedocs.io/en/latest/changelog.html
_______________________________________________
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 11:26 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <0E31F037-F564-4782-A76D-CBA0E435B7ED@gatech.edu>
On Sun, Mar 29, 2020 at 4:14 AM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:
> Yehowshua is a student at Georgia Tech currently pursuing a Masters in Computer Engineering - to graduate this summer. He had started working on LibreSOC in December and wanted to to get LibreSOC more funding so I could work on it full time.
added. robert's given us permission to mention his support of our
project. i implicitly understood that due to his high-profile online
presence that i couldn't say that he had been supporting us,
particularly with the ZC706 and the improvements to vga_lcd.
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 11:17 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <9e50160c-5105-7a0c-0add-851dd14abb41@gmail.com>
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Sat, Mar 28, 2020 at 6:07 PM Michael Nolan <mtnolan2640@gmail.com> wrote:
>
> On 3/26/20 5:03 PM, Luke Kenneth Casson Leighton wrote:
> >
> > if you prefer just reply to this message with a paragraph or two and i
> > will cut/paste it?
> >
> > l.
>
> The decoder we have is based on that of IBM's [microwatt reference
> design](https://github.com/antonblanchard/microwatt).
spotted the links, thanks 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] Public Inbox
From: Luke Kenneth Casson Leighton @ 2020-03-31 10:04 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD6q-ymob=HLewuKh5M+L1QdmmXSwnF-FX0CF+mru5G9Cw@mail.gmail.com>
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/
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
^ permalink raw reply
* Re: [libre-riscv-dev] Public Inbox
From: Luke Kenneth Casson Leighton @ 2020-03-31 9:49 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <24159B2E-12DC-42E4-931D-B562AF92C442@gatech.edu>
On Tue, Mar 31, 2020 at 5:31 AM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:
>
> Try this:
>
> http://inbox.libre-riscv.org/libre-riscv-dev/
oh - it _is_ black-on-whte. i think eric flipped the colours only on
public-inbox meta.
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: Luke Kenneth Casson Leighton @ 2020-03-31 9:48 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <3D47F1DA-6AA7-450C-BBE5-4CF69292090E@gatech.edu>
On Tue, Mar 31, 2020 at 5:27 AM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:
>
> Do you guys mind if I write a little CSS for it - like alternating greys for alternating messages, a sans font, and a little magic?
urrrr yes please... and for goodness sake flip to black-on-white, but
i do advocate please do keep the fixed-width fonts, i am getting tired
of variable-width fonts on everything, not least because ASCII tables
(which we often need to do, with lining up columns) is screwed.
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] pyobjc, gnu objective-c and gnustep
From: Luke Kenneth Casson Leighton @ 2020-03-31 9:38 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwz3n_jMS2NFFU=FJe4m82QqvG9XU2e9N474s7ZKj-VcA@mail.gmail.com>
https://groups.google.com/forum/#!topic/gnu.gnustep.discuss/6QbWfmaMrck
patches - 8 years ago (damnit, the changelog for 2.0.1 removed it)
you see the sort of thing i mean? there *are* people who understand
the power of dynamic objective runtime self-describing capability: and
they're *never properly funded*.
On Tue, Mar 31, 2020 at 10:32 AM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
>
> and pyobjc:
> https://pyobjc.readthedocs.io/en/latest/changelog.html
_______________________________________________
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 9:32 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzGM3KEeMQWh5_wvePa4bHJvDZJExdLCVjmaMije5Jzrg@mail.gmail.com>
and pyobjc:
https://pyobjc.readthedocs.io/en/latest/changelog.html
_______________________________________________
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 9:31 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <752371e7a9de77d78305af838989817bfec4fda8.camel@lip6.fr>
On Tue, Mar 31, 2020 at 9:17 AM Jean-Paul Chaput
<Jean-Paul.Chaput@lip6.fr> wrote:
>
> On Sat, 2020-03-28 at 17:13 +0000, Luke Kenneth Casson Leighton wrote:
> Funny, I remember well a student a while ago telling me that
> I should use XUL to write the graphical interface of Coriolis.
> I was already feeling like an old shmuck with my Qt...
sadly, in retrospect, it would have turned out to be a huge mistake.
i'm sorry to have to be the bearer of bad news, that i have been
unable to find *any* major libre software team with the intelligence
and resources to comprehend the strategic importance of DCOM.
historically, it is not a coincidence that there is a correlation
between microsoff's massive success (and that they used COM) and
Apple's massive success (and that they used Objective-J, Objective-C
and Objective-M), where each of those had - has - the same co-class
capability of COM actually built-in to the *compilers*, providing all
and any binaries right across the board with the exact same run-time
self-describing self-introspective object-orientated capacity that COM
gives.
hm.
that said, for long-term plans, you *might* want to look at GNU
Objective-C and the GNUstep GUI framework.
https://en.wikipedia.org/wiki/Objective-C#GNU,_GNUstep,_and_WinObjC
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: Jean-Paul Chaput @ 2020-03-31 8:17 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <CAPweEDyJKoUdHeDrQTHLWj7S42T=FDwj6bsnvCPoFHaf7bGy-Q@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 3271 bytes --]
On Sat, 2020-03-28 at 17:13 +0000, Luke Kenneth Casson Leighton wrote:
> On Sat, Mar 28, 2020 at 4:45 PM Jean-Paul Chaput
> <Jean-Paul.Chaput@lip6.fr> wrote:
>
> > The main reason here is still the lack of time. But there may be
> > another problem. My python interface allow to mirror in Python
> > the C++ function overload, but Python only allows one set of
> > parameters, is that true or I'm lagging on Python features again?
> > So how to describe a function with more than one parameter set?
>
> ah.
>
> right. with all the other things, i am going to focus on this one.
> it is a major, serious failing in the ENTIRETY of the free software
> community to COMPLETELY fail to comprehend this one, absolutely
> critical thing.
>
> microsoft DCOM got it right (co-classes). as a result i was the ONLY
> PERSON IN THE WORLD - i checked, emailing the IEXPLORE developer and
> he kindly replied - to use the full power of IEXPLORE.DLL DCOM
> bindings from python-comtypes. and by "full power" i mean "all 300
> objects, all 2,000+ functions, and all 20,000 properties".
>
> the only reason that was possible - including the c++ functions which
> had multiple overloads - was because of a property of DCOM called
> "co-classes".
>
> when the Mozilla Foundation decided "oh! we! know! we! will copy!
> DCOM! and call it! XPCOM! it'll be great!" they did NOT copy
> co-classes, and consequently fucked EVERYONE around for the next 15
> years who tried to develop third party xulrunner applications.
Funny, I remember well a student a while ago telling me that
I should use XUL to write the graphical interface of Coriolis.
I was already feeling like an old shmuck with my Qt...
> so if you *have* successfully mirrored multiple c++ function-overloads
> into python, GREAT! congratulations, you are amongst an absolute tiny
> minority of programmers who have comprehended this, where the majority
> are in systematic pathological failure and mental melt-down.
I did write it a long time ago, it is too complicated for what it
does. You can see an example in the PyHorizontal.cpp file and
look at PyHorizontal_create(). It is very dumb and tedious
programming. I intend to review it thoroughly when migrating
to Python 3. Basically it build the "signature" of the function
and is followed by a big "if" afterwards.
The Python "wrapper" is not something I'm very proud of as it
is only a big bunch of C macros. I'm not happy with the *way*
the code is generated, but on the other hand, I am happy with
the *generated* code and the fact that I can finely tune it.
I will try to make a more intensive use of C++ templates.
But not as much as in Boost as it becomes very, very slow to
compile (it's the reason why the Qt team abandoned it in favor
of another interface generator).
--
.-. 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
* Re: [libre-riscv-dev] Public Inbox
From: Jacob Lifshay @ 2020-03-31 5:20 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <24159B2E-12DC-42E4-931D-B562AF92C442@gatech.edu>
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.
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 4:43 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <24159B2E-12DC-42E4-931D-B562AF92C442@gatech.edu>
And this
```bash
git clone http://inbox.libre-riscv.org/libre-riscv-dev
```
Also this is me testing markdown capabilities of public inbox:
CSS sample
----------
```css
/*
* Firefox users: this goes in $PROFILE_FOLDER/chrome/userContent.css
* where $PROFILE_FOLDER is platform-specific
*
* cf. http://kb.mozillazine.org/UserContent.css
* http://kb.mozillazine.org/Profile_folder_-_Firefox
*
* Users of dillo can remove the entire lines with "moz-only"
* in them and place the resulting file in ~/.dillo/style.css
*/
@-moz-document url-prefix(https://public-inbox.org/meta/) { /* moz-only */
/*
* CC0-1.0 <https://creativecommons.org/publicdomain/zero/1.0/legalcode>
* Dark color scheme using 216 web-safe colors, inspired
* somewhat by the default color scheme in mutt.
* It reduces eyestrain for me, and energy usage for all:
* https://en.wikipedia.org/wiki/Light-on-dark_color_scheme
*/
* { background:#000 !important; color:#ccc !important }
/*
* Underlined links add visual noise which make them hard-to-read.
* Use colors to make them stand out, instead.
*/
a
{ color:#69f !important; text-decoration:none !important }
a:visited { color:#96f !important }
/* quoted text in emails gets a different color */
*.q { color:#09f !important }
/*
* these may be used with cgit <https://git.zx2c4.com/cgit/>, too.
* (cgit uses <div>, public-inbox uses <span>)
*/
*.add { color:#0ff !important } /* diff post-image lines */
*.del { color:#f0f !important } /* diff pre-image lines */
*.head { color:#fff !important } /* diff header (metainformation) */
*.hunk { color:#c93 !important } /* diff hunk-header */
/*
* highlight 3.x colors (tested 3.18) for displaying blobs.
* This doesn't use most of the colors available, as I find too
* many colors overwhelming, so the default is commented out.
*/
.hl.num { color:#f30 !important } /* number *
} /* moz-only */
```
_______________________________________________
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 4:31 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD4LzQSfX49KRdg1C3+6CGzTLU90uCyKG_0Qd5QjnBnmzA@mail.gmail.com>
Try this:
http://inbox.libre-riscv.org/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: Jacob Lifshay @ 2020-03-31 4:30 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <09F31DD2-0026-44C7-B702-6E08CE1D5B7C@gatech.edu>
On Mon, Mar 30, 2020, 21:22 Immanuel, Yehowshua U <yimmanuel3@gatech.edu>
wrote:
> Oh. I found it.
>
> http://inbox.libre-riscv.org/libre-riscv-dev/new.html
I just get 502 bad gateway.
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 4:27 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <1ED60264-2667-4980-800C-B86C339F0B25@gatech.edu>
Do you guys mind if I write a little CSS for it - like alternating greys for alternating messages, a sans font, and a little magic?
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: Immanuel, Yehowshua U @ 2020-03-31 4:25 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <09F31DD2-0026-44C7-B702-6E08CE1D5B7C@gatech.edu>
Looks like its oldest history is 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: Immanuel, Yehowshua U @ 2020-03-31 4:21 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <829465A0-552A-44CD-AED2-81E976D2191C@gatech.edu>
Oh. I found it.
http://inbox.libre-riscv.org/libre-riscv-dev/new.html
_______________________________________________
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 4:19 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <4C23AC26-6ECC-478D-B93E-A6C501F5AABD@gatech.edu>
> oh. i happened to so exactly that on http://inbox.libre-riscv.org however
Is that link supposed to look like this?
https://public-inbox.org/meta/
I’m guessing its broken?
Anyways, one the https git is fixed, I’ll go ahead and build my public inbox locally.
Maybe I’ll pop it on my heroku account(free dynamic site hosting for up to 5gigs with docker) until we can get font facing public inbox on libreriscv working.
Anyways, all in all, public inbox is amazing.
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] extremely busy crowdsupply update started
From: Jacob Lifshay @ 2020-03-31 4:18 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzjjQR-GtyRHoALd_MwV3J7vVmp-anbhxbzxbFJ7KkpNw@mail.gmail.com>
On Fri, Mar 27, 2020 at 1:47 AM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
>
> On Friday, March 27, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> >
> > I ended up with quite a bit more than a paragraph or two, hoping
> > that's ok since this is the first time simple-soft-float as appeared
> > in the CrowdSupply updates, and I've been working on it since june at
> > least. I'd appreciate a review by someone else to help catch errors. I
> > pushed my additions to crowdsupply.git.
>
>
> looks great jacob.
>
> were there any challenges or anything that was difficult or easy? it is
> "insights" that are the kind of thing that make updates interesting.
Added a little on that in the Kazan shader compiler section.
> oh, do mention the "rust library of the month" thing for example, and when
> that happened, and how what has been done expands on that since.
Added the mention, algebraics was the Crate of the Week back in October.
>
> also i suggest explicitly mentioning that these two libraries can be used
> by *anyone*, they are *not* specific to this project, and are exactly the
> kind of side-benefit that comes from sponsorship from NLNet. hm i might
> word that one if that's ok.
Seems as though you added that.
>
>
> oh, nearly forgot! can you also do a quick section on kazan, mentioning the
> intermediary milestone?
I ended up writing a whole new big section on the shader compiler IR.
We should probably copy a lot of that to our documentation.
At this point, we should probably split the update into multiple
separate updates or something, it's getting too long to easily 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 4:15 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwLo5gGn5E8mszQEYYBPbUJXgOEQTgXX7Ru1afEpGRVBA@mail.gmail.com>
https://git.libre-riscv.org/?p=libre-riscv-dev.git;a=tree
I can’t read the tree here :(
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 3:35 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <C4191A74-A82F-42E8-A1F1-075EF9135D33@gatech.edu>
On Tuesday, March 31, 2020, Immanuel, Yehowshua U <yimmanuel3@gatech.edu>
wrote:
> Is the public inbox live now?
a test one is. still TODO, set up the new lists, retire/freeze this one.
also running mb2maildir to grab the rest of the messages since the list
started.
If so, what is. the link?
https://git.libre-riscv.org/?p=libre-riscv-dev.git;a=summary
clone that, install public-inbox locally (or anywhere you like) and voila.
oh. i happened to so exactly that on http://inbox.libre-riscv.org however
it is not certain as to whether that is permanent, hence why it's not in
the wiki
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] Public Inbox
From: Immanuel, Yehowshua U @ 2020-03-31 2:40 UTC (permalink / raw)
To: Libre-RISCV General Development
Is the public inbox live now?
If so, what is. the link?
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] PPC on Talos and Playstation 3
From: Luke Kenneth Casson Leighton @ 2020-03-30 22:02 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <927534AC-082A-46D0-B2E1-111552EDFC93@gatech.edu>
On Mon, Mar 30, 2020 at 8:35 PM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:
> optional. however we'll need to add our own modes: Khronos / Vulkan Compliance.
>
> Ah. Gotcha. So do we even NEED to test on ppc64?
yes absolutely. otherwise, how will we know - for sure - that the HDL
is properly - and fully - ppc64 compliant?
> You can test 754 compliance on most anything.
except for PPC rounding modes and exception handling. except that
IEEE754 compliance is *NOT* fully and exactly defined. different
architectures have entirely different rules for rounding modes,
entirely different rules for NaN, and entirely different rules about
what and whether exceptions should be raised.
> If we opt out of the ppc mode -
ah no. we absolutely have to have compliance with the requirements
set by the OpenPOWER Foundation. otherwise we are not legally
permitted to use the name "POWER" associated with the project.
> then I imagine we don’t need PPC specific testing for the FPU.
> Is it possible to invoke PPC FPU mode through the instruction set?
it has to be enabled "by default".
we're negotiating with the OpenPOWER Foundation for the right to also
have a *Khronos* (Vulkan) Compliance Mode (as explained here:
https://libre-riscv.org/openpower/isans_letter/)
the fact that the "non IEEE mode" exists at all on POWER is a good sign.
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
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