* [libre-riscv-dev] [Bug 276] SR NAND Latch needed in nmigen
From: bugzilla-daemon @ 2020-04-04 11:05 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-276-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=276
--- Comment #12 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to whitequark from comment #11)
> > i presume that given that yosys already has $sr, only nmigen will need augmenting to produce $sr?
>
> There's no augmenting necessary. I gave you the code above (the
> `Instance("$sr"...)` that causes nMigen to emit a Yosys `$sr` cell.
fantastic! oh wait - i missed comment 8 (doh - how??)
http://bugs.libre-riscv.org/show_bug.cgi?id=276#c8
ok so the simulation(s) would be what need to recognise that.
could you let me know what amount you'd be happy to receive as a donation
from NLNet, for including $sr in cxxrtl?
also, i appreciate you suggested that we do the exploration, however that
would mean that someone else (other than you) receives money for doing so :)
as we'd very much like to support your work - and because we are a small
team there is such a lot else to do - would you be willing to add a
SRNAND latch example into cxxrtl for example?
--
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 137] NLNet 2019 Video Acceleration Proposal 2019-10-031
From: bugzilla-daemon @ 2020-04-04 10:57 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-137-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=137
--- Comment #17 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
Summary sentence for MoU
Video acceleration is a necessary component for any modern CPU and GPU. Given
the large amount of time the typical user spends on videos and its applications
like videoconferencing, a performant and power-efficient implementation is
necessary for wide adoption. With Zoom (etc.) now being critical to our modern
life, and full of security holes, full transparency in the video encode/decode
algorithms is more important than ever.
--
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] submitted bugreport to upstream nmigen
From: Frieder Paape @ 2020-04-04 8:15 UTC (permalink / raw)
To: Luke Kenneth Casson Leighton, Libre-RISCV General Development
In-Reply-To: <CAPweEDzDV0EiT=55jRz=O09+jqHC=1gZEogdNBmDu6=5vSdETQ@mail.gmail.com>
There is an api endpoint for jobs
<https://docs.gitlab.com/ee/api/jobs.html>. We could write a cronjob
which polls the api every day for new jobs and then saves the logs for
those jobs locally.
BUT I personaly think instead of investing time into workarounds because
we don't have gitlab hosted ourselves, we should rather invest time to
host it ourselves. Why not try to host it on the new talos 2 server.
Does it have a public IP? We will probably run into problems, but hey,
we are building a CPU on that architecture, it would look nice if we
host our development tools on such architecture as well. And if there
are larger problems we could bring them to IBM, which probably use
gitlab in high quantity and might have the muscle to ask for a quick
solution.
Hosting it on a donated x86 server I guess would be fine as well
Frieder
On 2020-04-03 23:48, Luke Kenneth Casson Leighton wrote:
> On Fri, Apr 3, 2020 at 9:22 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
>>> would you be happy for frieder to install gitlab on it? (the more
>>> people doing stuff in parallel the better).
>> Sure, though it doesn't have a public IP address and will be nearly
>> impossible to access publicly.
> tck... tck... *thinks*.... nginx reverse-proxy through libre-riscv.org
> shouuuld be able to fix that....
>
>> Also, I won't guarantee that
>> jacob-build-server will be up and running all the time or that I will
>> even respond quickly to issues (feel free to ssh in and power it off
>> if all else fails), so we shouldn't have it be a critical
>> time-sensitive dependency, such as hosting a website.
>>
>> We should probably still use debian salsa for building and setup some
>> kind of log scraper since it is publicly visible,
> there really should be a better way of doing that.
>
> frieder do you know how logs can be sent externally? (cole i see you
> investigated this somewhat).
>
> remember we do *not* have administrative control over salsa.
>
> 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 276] SR NAND Latch needed in nmigen
From: bugzilla-daemon @ 2020-04-04 8:15 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-276-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=276
--- Comment #11 from whitequark@whitequark.org ---
> i presume that given that yosys already has $sr, only nmigen will need augmenting to produce $sr?
There's no augmenting necessary. I gave you the code above (the
`Instance("$sr"...)` that causes nMigen to emit a Yosys `$sr` cell.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 269] auto-conversion / parser of POWER ISA Spec v3.0B
From: bugzilla-daemon @ 2020-04-04 3:04 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-269-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=269
--- Comment #15 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from comment #14)
> (In reply to Luke Kenneth Casson Leighton from comment #13)
>
> > can i leave that with you?
>
> yeah
star. technically once that base class is in place it should be possible to
go straight to dropping into internal_op.py
if you want to test out the new base class feel free to take one function from
one autogenerated file, as a test/dev case and hack something together that
works with interncal_op.
you will find however that much of decode2 is ignored (not useful). the opcode
*name* (not InternalOp), and you will need the Form name.
cry_in flags, add1, neg, etc. all ignored because the pseudocode on a case by
case already does that. however carry_out on the other hand we need something
for that.
i am still doing stuff (have to add % operator) i will keep ploughing through
to get all of them compiled.
please do us a favour and apart from test cases don't add the compiled .py
files to the repo :) yes they are .py however they are not the source code: the
pseudocode is!
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 269] auto-conversion / parser of POWER ISA Spec v3.0B
From: bugzilla-daemon @ 2020-04-03 22:55 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-269-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=269
--- Comment #14 from Michael Nolan <mtnolan2640@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #13)
> can i leave that with you?
yeah
--
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] finishing off the crowdsupply update
From: Luke Kenneth Casson Leighton @ 2020-04-03 21:52 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD43v5XvW2q7TSrDHQ2XSPavZqdNJ29uPqM1FLkxt0OFYw@mail.gmail.com>
On Fri, Apr 3, 2020 at 9:31 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
> Everything looks good to me!
likewise.
> So, I think the rest of what we need to do is:
>
> 1. Figure out if crowdsupply supports redirects for renaming our project.
> 2. Update the crowdsupply description of our project to reflect
> changing our name to Libre-SOC.
> 3. Publish our update. (only after above is complete, since that's
> when everyone will come look at the crowdsupply page).
everything is controlled by Joshua Lifton. i get a chance to *ask*
him if it's possible to change the redirects. i also have to remember
how to log in and...
oh, i just remembered, the description is in the crowdsupply wiki :)
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-03 21:48 UTC (permalink / raw)
To: Libre-RISCV General Development, Frieder Paape
In-Reply-To: <CAC2bXD4zCEh-TGckx1dpHEV2N6ARftkV-oseTCjE4NEt-mQwEA@mail.gmail.com>
On Fri, Apr 3, 2020 at 9:22 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
> > would you be happy for frieder to install gitlab on it? (the more
> > people doing stuff in parallel the better).
>
> Sure, though it doesn't have a public IP address and will be nearly
> impossible to access publicly.
tck... tck... *thinks*.... nginx reverse-proxy through libre-riscv.org
shouuuld be able to fix that....
> Also, I won't guarantee that
> jacob-build-server will be up and running all the time or that I will
> even respond quickly to issues (feel free to ssh in and power it off
> if all else fails), so we shouldn't have it be a critical
> time-sensitive dependency, such as hosting a website.
>
> We should probably still use debian salsa for building and setup some
> kind of log scraper since it is publicly visible,
there really should be a better way of doing that.
frieder do you know how logs can be sent externally? (cole i see you
investigated this somewhat).
remember we do *not* have administrative control over salsa.
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] parser precedence, code review / checking needed
From: Luke Kenneth Casson Leighton @ 2020-04-03 21:44 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD7hd1zUA1bkWUsJguOfukN56ZW2rVCRi+51cCumRScmkA@mail.gmail.com>
On Fri, Apr 3, 2020 at 9:08 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
> > ply has something called "precedence" which is a list-of-tuples that
> > helps resolve parser ambiguities.
>
> Just because something has a feature, doesn't mean that it's the best
> way to do it.
yeh i know :) ply was replaced by sly for good reasons. ply was - is
- FAST. it did not - does not - use classes because classes use up a
lot more memory and are slower. however with pretty much everyone now
possessing portable supercomputers, that's no longer so relevant.
the only reason i'm using it is because it's something i've worked
with about... five to eight times now. i forget :)
> As far as I can tell, it's working now.
fantastic. thank you. whew.
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 269] auto-conversion / parser of POWER ISA Spec v3.0B
From: bugzilla-daemon @ 2020-04-03 21:41 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-269-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=269
--- Comment #13 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Luke Kenneth Casson Leighton from comment #12)
> def cmpi(RA, RB): # pass in regs as parameters
> code
> blah
> return (RS,) # return modified params as results.
>
> duh.
ok can you take a look? (run pywriter.py again)
it does mean that we have to establish a "caller" system
which will also understand the number of parameters (called and returned).
in preparation for that, i got the auto-generated code to derive
from something called "ISACaller" - would you like to write that
class?
it should look up the instruction in the dictionary (ISACaller.instrs)
which you can see has been constructed (and appended at the bottom
of the derived class)
it contains the list of "variables" that need to be initialised
to zero (technically, uninitialised), the list of variables that
need to be "read" from the regfile (with a "yield") and, once
the function returns, the list of variables to be written to the
regfile.
to call a given function, you'll need those like this:
spec = self.instrs['cmpi']
actual_function, read_regs, uninit_regs, write_regs = spec
then merge read+unint (actually, move create_args() into
soc.decoder.isa.something and import it)
so: function_arg_names = create_args(read_regs+uninit_regs)
create function_args based on that list
and then call it:
result = actual_function(*function_args)
match the result with write_regs using zip:
for (fname, result) in zip(result, write_regs):
store result in GPR[fname]
can i leave that with you?
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 269] auto-conversion / parser of POWER ISA Spec v3.0B
From: bugzilla-daemon @ 2020-04-03 20:55 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-269-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=269
--- Comment #12 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
https://stackoverflow.com/questions/17862185/how-to-inject-variable-into-scope-with-a-decorator
nope. epic fail.
suddenly realised, it's real simple:
def cmpi(RA, RB): # pass in regs as parameters
code
blah
return (RS,) # return modified params as results.
duh.
--
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] parser precedence, code review / checking needed
From: Hendrik Boom @ 2020-04-03 20:41 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <CAC2bXD6FrkbjMvBWxWn=2F0cjtzHuOWJUtk2Cs_fOu1MYe8Xcw@mail.gmail.com>
On Fri, Apr 03, 2020 at 11:22:56AM -0700, Jacob Lifshay wrote:
> On Fri, Apr 3, 2020, 08:20 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> wrote:
...
> > +in_range <- (x | y) & (a | b)
> > +in_range <- (x + y) - (a + b)
> > +"""
> >
>
> since there are parenthesis, precedence between &, |, +, and - doesn't
> actually matter here, so it's not a good example. Traditionally + and -
> have the same precedence whereas & has higher precedence than | so a & b |
> c parses as (a & b) | c.
Presumably because the early logicians treated 'and' as being a multiplication
and 'or' as being an addition.
-- 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
* [libre-riscv-dev] [Bug 269] auto-conversion / parser of POWER ISA Spec v3.0B
From: bugzilla-daemon @ 2020-04-03 20:34 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-269-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=269
--- Comment #11 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from comment #10)
> (In reply to Luke Kenneth Casson Leighton from comment #9)
> > oh i know why. forgot to add __bool__. sorted. working now.
>
> Yeah the values look correct to me now.
>
>
> > when *not* using exec() but instead writing out the code-fragments to
> > an actual file, we need some pre- and post- functions which are called
> > before and after each function, that do the exact same thing.
> >
> > several ways to do that:
> >
> > 1) pass in a dictionary of variables that are
> > to be added to locals():
>
> This seems a little odd to me, but I'd be ok with it.
>
> > 2) make everything class-based (yuk) self.RA, self.RT, blah blah.
> >
> > this one i feel looks messy.
>
> I don't have a problem with this one, as it seems easier to understand to me
> than locals() or dropping variables into a module
>
> > 5) other
>
> It'd make the generated code a little messier, but couldn't we do what
> power_pseudo.py is currently doing and pass in a dict as a second argument?
then use it as d['RA'] = xxx etc.
i know from experience when working for Pine Digital (we did surpriiise
a python compiler) that dictionary accesses are a *lot* slower than attribute
accesses.
> This seems similar to option 2 in both pros and cons, in that the generated
> code isn't as nice looking but it's a bit easier to understand
*dinggg* lightbulb. decorators.
https://realpython.com/primer-on-python-decorators/#decorating-functions-with-arguments
i always tend to get confused with decorators so will write a quick test.
--
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] finishing off the crowdsupply update
From: Jacob Lifshay @ 2020-04-03 20:30 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <BBB39DD4-ADEC-4CDF-B5A2-7F95A95303DE@getmailspring.com>
On Fri, Apr 3, 2020 at 12:39 PM Cole Poirier <colepoirier@gmail.com> wrote:
>
> > On Fri, Apr 3, 2020 at 8:27 PM Cole Poirier <colepoirier@gmail.com> wrote:
> >> Hi Luke and Jacob, I have written a section about this, as well as some
> >> opinions of mine as to how this is going to benefit the project. Please
> >> take a look and make edits (i.e. large deletions) or give me feedback on
> >> what you think. I don't want to be overly verbose or flat our
> >> misleading, so your cutting of extraneous, incorrect, or irrelevant
> >> things is much appreciated.
> >
> > middle para is a repeat of the end of the 1st. cut. rest is great.
>
> Awesome! Thanks for your edits Luke :)
Everything looks good to me!
So, I think the rest of what we need to do is:
1. Figure out if crowdsupply supports redirects for renaming our project.
2. Update the crowdsupply description of our project to reflect
changing our name to Libre-SOC.
3. Publish our update. (only after above is complete, since that's
when everyone will come look at the crowdsupply page).
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] finishing off the crowdsupply update
From: Cole Poirier @ 2020-04-03 20:29 UTC (permalink / raw)
To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAPweEDyrDEkRLKwb+x-wq7jSz7+=gcDhkKVOVKTate4iU1T6pQ@mail.gmail.com>
On Apr 3 2020, at 12:44 pm, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> my friend phil taught me that one. without a first empty commit you
> simply cannot do a "diff" against that very first commit.
>
> l.
Wow, that's quite the useful piece of knowledge. My thanks to phil :)
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] submitted bugreport to upstream nmigen
From: Cole Poirier @ 2020-04-03 20:27 UTC (permalink / raw)
To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAPweEDyB2Rng3Mm10ymgyz0WwY7EKHGLVgb4FT_1Xm7gOWZNRg@mail.gmail.com>
On Apr 3 2020, at 12:24 pm, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> On Fri, Apr 3, 2020 at 7:26 PM Jacob Lifshay
> <programmerjake@gmail.com> wrote:
>
>> We can build it on any other gitlab installation, if all else fails,
>> we can
>> install gitlab on jacob-build-server.
>
> which has ridiculous resources (32 GB RAM for a start). plus, we have
> root access so can do backups etc.
>
> would you be happy for frieder to install gitlab on it? (the more
> people doing stuff in parallel the better).
>
> l.
I did a little bit of research on how gitlab archives build logs and
build artifacts.
https://docs.gitlab.com/ee/administration/job_artifacts.html
https://docs.gitlab.com/ee/administration/job_logs.html#new-incremental-logging-architecture
I believe this is their official tool for doing such things.
https://gitlab.com/gitlab-org/gitlab-workhorse
If you'd like I'd be willing to install gitlab and gitlab test runner on
my 2600x 32 GB machine, and purchase a sizable hard drive to serve as
one of the archives.
Is there some way that I can allocate only 2, 4, or 6 logical cores, and
say 12 or 16GB or ram, and 50MB/s of bandwidth? Perhaps I am not yet up
to the task of running a server on which the project critically depends.
But I do have these resources available, so if there is a way you can
think of making this useful and what you require please let me know.
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] submitted bugreport to upstream nmigen
From: Jacob Lifshay @ 2020-04-03 20:21 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDyB2Rng3Mm10ymgyz0WwY7EKHGLVgb4FT_1Xm7gOWZNRg@mail.gmail.com>
On Fri, Apr 3, 2020 at 12:24 PM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
>
> On Fri, Apr 3, 2020 at 7:26 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> > We can build it on any other gitlab installation, if all else fails, we can
> > install gitlab on jacob-build-server.
>
> which has ridiculous resources (32 GB RAM for a start). plus, we have
> root access so can do backups etc.
Actually only 20GB ram, I have 2 2GB sticks and 2 8GB sticks of ddr3
because if I have the ram why not use it. :)
If we want to get more ram, we should get ddr4 ram instead since I
also have a Ryzen 2600 and a motherboard for it that I could swap into
jacob-build-server, however I don't have any spare ddr4 ram.
> would you be happy for frieder to install gitlab on it? (the more
> people doing stuff in parallel the better).
Sure, though it doesn't have a public IP address and will be nearly
impossible to access publicly. Also, I won't guarantee that
jacob-build-server will be up and running all the time or that I will
even respond quickly to issues (feel free to ssh in and power it off
if all else fails), so we shouldn't have it be a critical
time-sensitive dependency, such as hosting a website.
We should probably still use debian salsa for building and setup some
kind of log scraper since it is publicly visible, unlike
jacob-build-server.
I was thinking we would just put gitlab on jacob-build-server if
debian salsa is no longer viable.
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] parser precedence, code review / checking needed
From: Jacob Lifshay @ 2020-04-03 20:08 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDz7zK4Db-qM+=aUd2ctsTjHJjBmRt9W3VMtbF9NV6rc9w@mail.gmail.com>
On Fri, Apr 3, 2020 at 11:50 AM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
>
> On Fri, Apr 3, 2020 at 7:23 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
> >
> > On Fri, Apr 3, 2020, 08:20 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> > wrote:
> >
> > > if anyone knows how to resolve operator precedence, my logic-dyslexia
> > > is kicking in and i am having difficulty working out which operators
> > > are supposed to be in which order, for bit-wise AND, OR, and
> > > PLUS/MINUS, MUL/DIV. someone else did the PLUS/MINUS MUL/DIV, i'm
> > > attempting to add AND and OR and am getting it wrong
> > >
> >
> > The way I always did it is by changing the grammar to have one non-terminal
> > symbol per precedence level. Example code from my LR(1) parser generator:
> > https://github.com/programmerjake/parser-generator/blob/master/test.parser#L108-L120
>
> ply has something called "precedence" which is a list-of-tuples that
> helps resolve parser ambiguities.
Just because something has a feature, doesn't mean that it's the best
way to do it.
As far as I can tell, it's working now.
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 269] auto-conversion / parser of POWER ISA Spec v3.0B
From: bugzilla-daemon @ 2020-04-03 19:45 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-269-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=269
--- Comment #10 from Michael Nolan <mtnolan2640@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #9)
> oh i know why. forgot to add __bool__. sorted. working now.
Yeah the values look correct to me now.
> when *not* using exec() but instead writing out the code-fragments to
> an actual file, we need some pre- and post- functions which are called
> before and after each function, that do the exact same thing.
>
> several ways to do that:
>
> 1) pass in a dictionary of variables that are
> to be added to locals():
This seems a little odd to me, but I'd be ok with it.
> 2) make everything class-based (yuk) self.RA, self.RT, blah blah.
>
> this one i feel looks messy.
I don't have a problem with this one, as it seems easier to understand to me
than locals() or dropping variables into a module
> 5) other
It'd make the generated code a little messier, but couldn't we do what
power_pseudo.py is currently doing and pass in a dict as a second argument?
This seems similar to option 2 in both pros and cons, in that the generated
code isn't as nice looking but it's a bit easier to understand
--
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] finishing off the crowdsupply update
From: Luke Kenneth Casson Leighton @ 2020-04-03 19:44 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <8A00D0AE-260C-4F09-8008-A08F779744CB@getmailspring.com>
On Fri, Apr 3, 2020 at 8:43 PM Cole Poirier <colepoirier@gmail.com> wrote:
>
> On Apr 3 2020, at 12:40 pm, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
>
> >> > https://git.libre-riscv.org/?p=dev-env-setup.git;a=summary
> > remember it is entirely empty so please do a first "empty commit".
> > google how to do that. --allow-empty i think
> >
> > l.
>
> Done. Thank you for the heads up, I would not have known to do this otherwise.
my friend phil taught me that one. without a first empty commit you
simply cannot do a "diff" against that very first commit.
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] finishing off the crowdsupply update
From: Cole Poirier @ 2020-04-03 19:43 UTC (permalink / raw)
To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAPweEDyofugHW8brxA2ScZkXKJ+WQfkkjWqKxziz5YguLQov1w@mail.gmail.com>
On Apr 3 2020, at 12:40 pm, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
>> > https://git.libre-riscv.org/?p=dev-env-setup.git;a=summary
> remember it is entirely empty so please do a first "empty commit".
> google how to do that. --allow-empty i think
>
> l.
Done. Thank you for the heads up, I would not have known to do this otherwise.
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] finishing off the crowdsupply update
From: Luke Kenneth Casson Leighton @ 2020-04-03 19:40 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <BBB39DD4-ADEC-4CDF-B5A2-7F95A95303DE@getmailspring.com>
On Fri, Apr 3, 2020 at 8:39 PM Cole Poirier <colepoirier@gmail.com> wrote:
> > https://git.libre-riscv.org/?p=dev-env-setup.git;a=summary
>
> Fantastic, cloning now.
remember it is entirely empty so please do a first "empty commit".
google how to do that. --allow-empty i think
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] finishing off the crowdsupply update
From: Cole Poirier @ 2020-04-03 19:39 UTC (permalink / raw)
To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAPweEDwweJPBnirPLGQB_F8jWfxiQt0rGb0OLsa5qsZJtnF3nQ@mail.gmail.com>
> On Fri, Apr 3, 2020 at 8:27 PM Cole Poirier <colepoirier@gmail.com> wrote:
>> Hi Luke and Jacob, I have written a section about this, as well as some
>> opinions of mine as to how this is going to benefit the project. Please
>> take a look and make edits (i.e. large deletions) or give me feedback on
>> what you think. I don't want to be overly verbose or flat our
>> misleading, so your cutting of extraneous, incorrect, or irrelevant
>> things is much appreciated.
>
> middle para is a repeat of the end of the 1st. cut. rest is great.
Awesome! Thanks for your edits Luke :)
>> Also, I left a TODO at the end Luke, because I looked for but was unable
>> to find the repo dev-env-setup on git.libre-riscv.org.
>
> that's because i hadn't done the symlink in /var/lib/git/repositories
>
> https://git.libre-riscv.org/?p=dev-env-setup.git;a=summary
Fantastic, cloning now.
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] finishing off the crowdsupply update
From: Luke Kenneth Casson Leighton @ 2020-04-03 19:35 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <F3857650-A597-4F51-9BB0-F7DDF5052B99@getmailspring.com>
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Fri, Apr 3, 2020 at 8:27 PM Cole Poirier <colepoirier@gmail.com> wrote:
>
> On Apr 3 2020, at 3:28 am, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> > On Thu, Apr 2, 2020 at 11:59 PM Jacob Lifshay
> > <programmerjake@gmail.com> wrote:
> >>
> >> what do we still need to do?
> >
> > build server section and i think that's it. can you write sonething
> > short? about Cl
>
> Hi Luke and Jacob, I have written a section about this, as well as some
> opinions of mine as to how this is going to benefit the project. Please
> take a look and make edits (i.e. large deletions) or give me feedback on
> what you think. I don't want to be overly verbose or flat our
> misleading, so your cutting of extraneous, incorrect, or irrelevant
> things is much appreciated.
middle para is a repeat of the end of the 1st. cut. rest is great.
> Also, I left a TODO at the end Luke, because I looked for but was unable
> to find the repo dev-env-setup on git.libre-riscv.org.
that's because i hadn't done the symlink in /var/lib/git/repositories
https://git.libre-riscv.org/?p=dev-env-setup.git;a=summary
_______________________________________________
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] finishing off the crowdsupply update
From: Cole Poirier @ 2020-04-03 19:27 UTC (permalink / raw)
To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAPweEDwPWo2WxV3fa5cXN5Sm2HY5NOOJJUaPrkAEH5Suh3jHyQ@mail.gmail.com>
On Apr 3 2020, at 3:28 am, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> On Thu, Apr 2, 2020 at 11:59 PM Jacob Lifshay
> <programmerjake@gmail.com> wrote:
>>
>> what do we still need to do?
>
> build server section and i think that's it. can you write sonething
> short? about Cl
Hi Luke and Jacob, I have written a section about this, as well as some
opinions of mine as to how this is going to benefit the project. Please
take a look and make edits (i.e. large deletions) or give me feedback on
what you think. I don't want to be overly verbose or flat our
misleading, so your cutting of extraneous, incorrect, or irrelevant
things is much appreciated.
Also, I left a TODO at the end Luke, because I looked for but was unable
to find the repo dev-env-setup on git.libre-riscv.org.
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
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