* [libre-riscv-dev] [Bug 185] Getting 502 Bad Gateway
From: bugzilla-daemon @ 2020-04-07 11:35 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-185-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=185
--- Comment #14 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Alain D D Williams from comment #13)
> Please create DNS entries for inbox.libre-soc.org
> IPv4 & IPv6
>
> Ta
done - it's in /etc/bind/libre-soc.org.db
--
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 185] Getting 502 Bad Gateway
From: bugzilla-daemon @ 2020-04-07 11:37 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-185-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=185
--- Comment #15 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
btw i'm just doing a snapshot of the offsite rsync backups that i do,
before rsync'ing. 3.2 GB copied so far, another 3 GB to go.
that way we have a comparison of before-and-after the libre-soc state,
and can do "diffs" on the configs (etc.)
--
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 267] The efficiency of adder/subtractor
From: bugzilla-daemon @ 2020-04-07 11:39 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-267-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=267
--- Comment #4 from Jock Tanner <tanner.of.kha@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #3)
> if you can put some links here as to what you're comparing (descriptions,
> tutorials, gate-level diagrams) i can get up to speed and follow the
> conversation.
I mostly rely on a college textbook by David & Sarah Harris, named “Digital
Design and Computer Architecture”. I read it only in Russian though. The book
has a very detailed explanation of carry-lookahead adder, with truth tables and
schematics.
Some knowledge can even be found in Wiki [1].
Very roughly speaking, N-bit ripple-carry adder takes a*N transistors and b*N
time for calculation, while straight-out carry-lookahead adder takes a^N
transistors and b time. AFAIK in practical ALU design they always make a
compromise between the two. And I just wonder what kind of compromise could be
suitable for *reconfigurable*, high-speed ALU.
I imagine something cascadable, like 74181 bit-slice ALUs + 74182 carry
generators [2], but with 'plexors in between. But the speed of such a design
may be questionable.
[1] https://en.wikipedia.org/wiki/Adder_(electronics)
[2] https://en.wikipedia.org/wiki/74181
--
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 267] The efficiency of adder/subtractor
From: bugzilla-daemon @ 2020-04-07 11:48 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-267-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=267
--- Comment #5 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jock Tanner from comment #4)
> (In reply to Luke Kenneth Casson Leighton from comment #3)
> > if you can put some links here as to what you're comparing (descriptions,
> > tutorials, gate-level diagrams) i can get up to speed and follow the
> > conversation.
>
> I mostly rely on a college textbook by David & Sarah Harris, named “Digital
> Design and Computer Architecture”. I read it only in Russian though. The
> book has a very detailed explanation of carry-lookahead adder, with truth
> tables and schematics.
interesting. well, what we will be relying on is yosys "synth" command
turning things from high-level "we want an N-bit adder" into low-level
"these 4-bit adders and etc. etc. get created".
we are pretty much trusting yosys "synth" to have the optimal state-of-the-art
latest industry-recognised "thing".
> Very roughly speaking, N-bit ripple-carry adder takes a*N transistors and
> b*N time for calculation, while straight-out carry-lookahead adder takes a^N
> transistors and b time. AFAIK in practical ALU design they always make a
> compromise between the two. And I just wonder what kind of compromise could
> be suitable for *reconfigurable*, high-speed ALU.
i honestly have no idea! :)
the basic units will actually be a 64+8-bit add (yes 72 bit).
https://git.libre-riscv.org/?p=ieee754fpu.git;a=blob;f=src/ieee754/part_mul_add/adder.py;h=e1849b4d25fc5ec4fc4473cc02b32f49dd5912b2;hb=77f150cff440bed025e2487b6f0fcda9f529290b#l108
see the comment description there of how it works
the "partitions" are done via the insertion of those "extra bits".
those "extra bits" will be set to 0 to create a partition, and "1"
to get a roll-over.
so we're not *actually* "partitioning" into completely separate 8-bit adders.
therefore i would hazard a guess that the (underlying 72-bit) adders are
properly optimised by yosys "synth" command to give a decent fast adder,
thus giving us the "best of both worlds".
in other words, a quick analysis leads me to believe that what we're using
is *not* adversely impacted just because it's a partitioned adder.
it has the *functionality* of a partitioned adder but is in fact a 72-bit
"straight" (normal) add.
--
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 267] The efficiency of adder/subtractor
From: bugzilla-daemon @ 2020-04-07 13:15 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-267-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=267
--- Comment #6 from Jock Tanner <tanner.of.kha@gmail.com> ---
The idea is so simple yet so out-of-the-box! I feel like I'm in a Western
movie, while my partner is devising a get-rich-fast scheme:
− And where's the catch?
− There is no catch.
BTW is it patented?
(In reply to Luke Kenneth Casson Leighton from comment #5)
> https://git.libre-riscv.org/?p=ieee754fpu.git;a=blob;f=src/ieee754/
> part_mul_add/adder.py;h=e1849b4d25fc5ec4fc4473cc02b32f49dd5912b2;
> hb=77f150cff440bed025e2487b6f0fcda9f529290b#l108
>
> see the comment description there of how it works
>
> the "partitions" are done via the insertion of those "extra bits".
>
> those "extra bits" will be set to 0 to create a partition, and "1"
> to get a roll-over.
>
>
> so we're not *actually* "partitioning" into completely separate 8-bit adders.
>
> therefore i would hazard a guess that the (underlying 72-bit) adders are
> properly optimised by yosys "synth" command to give a decent fast adder,
> thus giving us the "best of both worlds".
--
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 267] The efficiency of adder/subtractor
From: bugzilla-daemon @ 2020-04-07 13:36 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-267-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=267
--- Comment #7 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to Jock Tanner from comment #4)
> Very roughly speaking, N-bit ripple-carry adder takes a*N transistors and
> b*N time for calculation, while straight-out carry-lookahead adder takes a^N
> transistors and b time. AFAIK in practical ALU design they always make a
> compromise between the two. And I just wonder what kind of compromise could
> be suitable for *reconfigurable*, high-speed ALU.
>
> I imagine something cascadable, like 74181 bit-slice ALUs + 74182 carry
> generators [2], but with 'plexors in between. But the speed of such a design
> may be questionable.
I haven't checked which specific design yosys produces for an adder, but I know
there are divide and conquer carry lookahead designs that have area of
O(N*log(N)) and delay of O(log(N)) when ignoring delay due to wire length, so
that's much better than the above a^N value.
I found a paper with an overview of different carry lookahead adder designs:
https://www.ijrte.org/wp-content/uploads/papers/v7i5s4/E10920275S419.pdf
In fact, I'm planning on using the same kind of recursive divide and conquer
structure for purposes other than addition such as finding the first set bit or
a prefix-sum.
--
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 267] The efficiency of adder/subtractor
From: bugzilla-daemon @ 2020-04-07 13:38 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-267-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=267
Jacob Lifshay <programmerjake@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |programmerjake@gmail.com
--- Comment #8 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to Jock Tanner from comment #6)
> The idea is so simple yet so out-of-the-box! I feel like I'm in a Western
> movie, while my partner is devising a get-rich-fast scheme:
>
> − And where's the catch?
> − There is no catch.
>
> BTW is it patented?
Not that I'm aware of, I invented it.
--
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] Broken build notification from debian salsa
From: Jacob Lifshay @ 2020-04-07 14:37 UTC (permalink / raw)
To: Libre-RISCV General Development
Checking to see if you saw this Luke:
https://salsa.debian.org/Kazan-team/soc/-/jobs/652909
If you don't have email notifications enabled, you probably should. We
should probably figure out how to get salsa build failures sent to the
mailing list as well, though we'd have to remove the unsubscribe link to
prevent accidental/malicious unsubscription.
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 267] The efficiency of adder/subtractor
From: bugzilla-daemon @ 2020-04-07 14:44 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-267-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=267
--- Comment #9 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jock Tanner from comment #6)
> The idea is so simple yet so out-of-the-box! I feel like I'm in a Western
> movie, while my partner is devising a get-rich-fast scheme:
>
> − And where's the catch?
> − There is no catch.
a lot of what we're doing is like that. the 6600 scoreboards are *very*
badly misunderstood and drastically underestimated right across the
entire industry (thanks largely to Patterson's book on RISC architectures).
consequently what's in Thornton's book "Design of a Computer" (google it)
has had to be "reinvented" and often comes attached with unnecessary baggage
such as "register renamers".
then again there are areas where we are "functional" but need serious
improvement. we need a Dadda multiplier algorithm for example, because
we currently have a Wallace Tree one.
https://bugs.libre-soc.org/show_bug.cgi?id=136
--
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 185] Getting 502 Bad Gateway
From: bugzilla-daemon @ 2020-04-07 14:58 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-185-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=185
--- Comment #16 from Alain D D Williams <addw@phcomp.co.uk> ---
All done - except a quick tidy up - removing old config commented out.
Done:
* all libre-riscv sites redirect to a corresponding libre-soc site
* all http:// sites redirect to a https:// site
This might mean that web browsers will not auto fill passwords, since they are
looking at different domains.
Also: what to do with uelves.com ? What is this ?
--
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] Broken build notification from debian salsa
From: Luke Kenneth Casson Leighton @ 2020-04-07 15:00 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD6wXSz+NWMwOhgxosKnLtTMJXzCNt9NY-qe1X80gCLVqg@mail.gmail.com>
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Tue, Apr 7, 2020 at 3:37 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> Checking to see if you saw this Luke:
> https://salsa.debian.org/Kazan-team/soc/-/jobs/652909
no, i don't see anything from that because it's not sent to a public
mailing list / resource.
> If you don't have email notifications enabled, you probably should.
the implications of relying on and reacting to something that's sent
via a *private message* - even one that comes from an automated system
- are that we are "hiding something".
that seriously violates the goals of the project and undermines the
basis of the funding that we receive from NLNet.
although it's fantastic that you've done them, none of the rest of the
team have any idea why those bugs were fixed in the unit tests, except
when reviewing the "final result" - the commit.
this is a huge alarm-bell.
> We
> should probably figure out how to get salsa build failures sent to the
> mailing list as well,
build failures, job runs - everything.
this is important, jacob.
i didn't realise what was going to be involved in the deployment of
CI, otherwise i would have raised it as a proper discussion for
evaluation, long before the time and effort was spent on getting it
set up.
including properly evaluating alternatives, and how to ensure that
everything is archived and transparent.
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 185] Getting 502 Bad Gateway
From: bugzilla-daemon @ 2020-04-07 15:01 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-185-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=185
--- Comment #17 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Alain D D Williams from comment #16)
> All done - except a quick tidy up - removing old config commented out.
>
> Done:
>
> * all libre-riscv sites redirect to a corresponding libre-soc site
>
> * all http:// sites redirect to a https:// site
>
> This might mean that web browsers will not auto fill passwords, since they
> are looking at different domains.
yes. found that out already :)
> Also: what to do with uelves.com ? What is this ?
that's another domain i'm running, nothing to do with libre-soc.
--
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] Broken build notification from debian salsa
From: Immanuel, Yehowshua U @ 2020-04-07 15:03 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD6wXSz+NWMwOhgxosKnLtTMJXzCNt9NY-qe1X80gCLVqg@mail.gmail.com>
> We
> should probably figure out how to get salsa build failures sent to the
> mailing list as well, though we'd have to remove the unsubscribe link to
> prevent accidental/malicious unsubscription.
I think we had talked about creating another mailing list for builds and bugs.
Now might be a good time to set that up.
The three mailing lists discussed were
- main/dev
- bugs
- watercooler
I’ll see if I can find the reference links.
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 185] Getting 502 Bad Gateway
From: bugzilla-daemon @ 2020-04-07 15:04 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-185-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=185
--- Comment #18 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
the next one, before we get much further, is the mailing lists:
https://bugs.libre-soc.org/show_bug.cgi?id=184
however at the same time, each list needs a public-inbox:
https://bugs.libre-soc.org/show_bug.cgi?id=181
see /home/publicinbox and fortunately it's possible to have
a per-list-filter despite all messages going into /home/publicinbox/Maildir
to discuss at bug #184
--
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 184] new mailing lists proposal for libre-soc.org
From: bugzilla-daemon @ 2020-04-07 15:07 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-184-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=184
--- Comment #7 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
public-inbox needs to be set up for each list as well
see /home/publicinbox and fortunately it's possible to have
a per-list-filter despite all messages going into /home/publicinbox/Maildir
the config (/home/publicinbox/.public-inbox/config) basically has
a filter to look for (the listid) and, when spotted, sucks that message
out.
btw, i recall now: we are *not* using Maildir, the messages are delivered
*directly* to publicinboxmda, actually in exim4:
/etc/exim4/conf.d/router/890-local_publicinbox: local_parts = publicinbox
--
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 184] new mailing lists proposal for libre-soc.org
From: bugzilla-daemon @ 2020-04-07 15:09 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-184-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=184
--- Comment #8 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
we also will need an auto-build (continuous integration) list where
notifications (read-only) about builds and tests are sent.
--
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] Broken build notification from debian salsa
From: Luke Kenneth Casson Leighton @ 2020-04-07 15:10 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <A0849B16-A2AD-47A1-9622-7DA77EDC7EF1@gatech.edu>
On Tue, Apr 7, 2020 at 4:03 PM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:
>
> > We
> > should probably figure out how to get salsa build failures sent to the
> > mailing list as well, though we'd have to remove the unsubscribe link to
> > prevent accidental/malicious unsubscription.
>
> I think we had talked about creating another mailing list for builds and bugs.
> Now might be a good time to set that up.
https://bugs.libre-soc.org/show_bug.cgi?id=184
best discussed there.
> The three mailing lists discussed were
> - main/dev
> - bugs
> - watercooler
_______________________________________________
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] Broken build notification from debian salsa
From: Jacob Lifshay @ 2020-04-07 15:13 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzD3y7YXGu=L5B4Voi0WXaYFy2CctzzgpJtugyULHaJmA@mail.gmail.com>
On Tue, Apr 7, 2020, 08:00 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:
> ---
> crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
>
> On Tue, Apr 7, 2020 at 3:37 PM Jacob Lifshay <programmerjake@gmail.com>
> wrote:
> >
> > Checking to see if you saw this Luke:
> > https://salsa.debian.org/Kazan-team/soc/-/jobs/652909
>
> no, i don't see anything from that because it's not sent to a public
> mailing list / resource.
>
>
> > If you don't have email notifications enabled, you probably should.
>
> the implications of relying on and reacting to something that's sent
> via a *private message* - even one that comes from an automated system
> - are that we are "hiding something".
>
> that seriously violates the goals of the project and undermines the
> basis of the funding that we receive from NLNet.
>
> although it's fantastic that you've done them, none of the rest of the
> team have any idea why those bugs were fixed in the unit tests, except
> when reviewing the "final result" - the commit.
>
Actually, everything but the notification email is currently public --
anyone can look at the build log and see the builds corresponding to all
commits. I think anyone can subscribe to the notifications, but I could be
wrong. If we subscribe the mailing list we should figure out how to filter
out the unsubscribe link to avoid people unsubscribing the mailing list
from gitlab.
https://salsa.debian.org/Kazan-team/soc/pipelines
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] [Bug 267] The efficiency of adder/subtractor
From: whygee @ 2020-04-07 15:14 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <bug-267-13-EWn9DEVAiO@http.bugs.libre-riscv.org/>
Have a look :
http://www.ecs.umass.edu/ece/koren/arith/simulator/Add/lookahead/
On 2020-04-07 16:44, bugzilla-daemon@libre-riscv.org wrote:
> http://bugs.libre-riscv.org/show_bug.cgi?id=267
>
> --- Comment #9 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
> (In reply to Jock Tanner from comment #6)
>> The idea is so simple yet so out-of-the-box! I feel like I'm in a
>> Western
>> movie, while my partner is devising a get-rich-fast scheme:
>>
>> − And where's the catch?
>> − There is no catch.
>
> a lot of what we're doing is like that. the 6600 scoreboards are
> *very*
> badly misunderstood and drastically underestimated right across the
> entire industry (thanks largely to Patterson's book on RISC
> architectures).
>
> consequently what's in Thornton's book "Design of a Computer" (google
> it)
> has had to be "reinvented" and often comes attached with unnecessary
> baggage
> such as "register renamers".
>
> then again there are areas where we are "functional" but need serious
> improvement. we need a Dadda multiplier algorithm for example, because
> we currently have a Wallace Tree one.
> https://bugs.libre-soc.org/show_bug.cgi?id=136
_______________________________________________
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 267] The efficiency of adder/subtractor
From: Jacob Lifshay @ 2020-04-07 15:25 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <395ba2c70f9f495f81e02056b8cf8b22@f-cpu.org>
On Tue, Apr 7, 2020, 08:14 <whygee@f-cpu.org> wrote:
> Have a look :
> http://www.ecs.umass.edu/ece/koren/arith/simulator/Add/lookahead/
Neat! It is, however, limited to only 2 levels of lookahead circuits, which
is only sufficient for 16 or maybe 32 bits, not for 64 or more.
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 185] Getting 502 Bad Gateway
From: bugzilla-daemon @ 2020-04-07 15:31 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-185-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=185
--- Comment #19 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to Alain D D Williams from comment #16)
> All done - except a quick tidy up - removing old config commented out.
>
> Done:
>
> * all libre-riscv sites redirect to a corresponding libre-soc site
>
> * all http:// sites redirect to a https:// site
Bugzilla needs to be updated to send out the correct url.
--
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] [Bug 267] The efficiency of adder/subtractor
From: whygee @ 2020-04-07 15:46 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD5Vd=OPuHr5hTyE7E3aLQL924aHmeq3-z7MNWCsLFF3_A@mail.gmail.com>
On 2020-04-07 17:25, Jacob Lifshay wrote:
> On Tue, Apr 7, 2020, 08:14 <whygee@f-cpu.org> wrote:
>> Have a look :
>> http://www.ecs.umass.edu/ece/koren/arith/simulator/Add/lookahead/
>
> Neat! It is, however, limited to only 2 levels of lookahead circuits,
> which
> is only sufficient for 16 or maybe 32 bits, not for 64 or more.
It shouldn't be too hard to extend it...
> Jacob
y
_______________________________________________
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] Broken build notification from debian salsa
From: Luke Kenneth Casson Leighton @ 2020-04-07 15:47 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD7T3tjv9irjC7NU5gMWQgWVr8rV2k_oNoSmcW6aZ6s8_w@mail.gmail.com>
On Tue, Apr 7, 2020 at 4:13 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> On Tue, Apr 7, 2020, 08:00 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> wrote:
> Actually, everything but the notification email is currently public --
> anyone can look at the build log and see the builds corresponding to all
> commits. I think anyone can subscribe to the notifications, but I could be
> wrong. If we subscribe the mailing list we should figure out how to filter
> out the unsubscribe link to avoid people unsubscribing the mailing list
> from gitlab.
a separate list can be set up, one that is admin-moderator-only, no
subscribes or unsubscribes permitted.
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 185] Getting 502 Bad Gateway
From: bugzilla-daemon @ 2020-04-07 15:50 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-185-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=185
--- Comment #20 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jacob Lifshay from comment #19)
> Bugzilla needs to be updated to send out the correct url.
well spotted. done (in bzla admin interface)
--
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] Broken build notification from debian salsa
From: Luke Kenneth Casson Leighton @ 2020-04-07 15:52 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDyvmOxf7Yr-J0_hwJQ+owyP_c7aaZW_7Lz80NQtbNAtEg@mail.gmail.com>
On Tue, Apr 7, 2020 at 4:47 PM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
> a separate list can be set up, one that is admin-moderator-only, no
> subscribes or unsubscribes permitted.
hm that wouldn't work, would it... hmm...
_______________________________________________
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