Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] daily kan-ban update 09jun2020
Date: Tue, 9 Jun 2020 18:44:23 +0100
Message-ID: <CAPweEDwoNNgwcPb8SdBb8y_ZFTYCcwSYNiCniER-DWqxByj=bw@mail.gmail.com> (raw)
In-Reply-To: <CAC2bXD6Ct+RW_=p-J-M_0PdNtFA9XFS-OTFGim4WPCNr5WosAQ@mail.gmail.com>

On Tue, Jun 9, 2020 at 6:21 PM Jacob Lifshay <programmerjake@gmail.com> wrote:

> yesterday:
> not much

:) rest is good

> today:
> working on mul and div units -- they will most likely increase the core's
> gate count by a large amount, particularly the div pipeline, since it's
> designed for high performance, not as much for low area.

hm hm well as long as it is below 45k LUTs we should be good.  last
resort there is always the microwatt div algorithm, which i noticed in
its FSM has the option to skip large batches of zeros (8 at a time).
personally i hope it fits, hmm it should be easy to check, with
synth_ecp5
this is for test_div_pipe_core_bit_width_8_fract_width_4_radix_2.il

=== top ===

   Number of cells:               3411
     CCU2C                         461
     L6MUX21                       116
     LUT4                         1777
     PFUMX                         539
     TRELLIS_FF                    518

that's a very small one, though, isn't it?  bit-width of 8?

> Also, I saw the new *inter-core* speculative execution vulnerability in
> Intel processors, the previous ones were mostly intra-core.

oh no!  i don't know whether to laugh, start to feel sorry for them,
or look it up and make sure we don't make the same mistake.  probably
all of those :)

l.

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

  reply index

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-09 13:11 Luke Kenneth Casson Leighton
2020-06-09 13:23 ` Tobias Platen
2020-06-09 16:20   ` Luke Kenneth Casson Leighton
2020-06-09 17:21 ` Jacob Lifshay
2020-06-09 17:44   ` Luke Kenneth Casson Leighton [this message]
2020-06-09 19:35 ` Cole Poirier
2020-06-09 20:15   ` Luke Kenneth Casson Leighton
2020-06-09 21:01     ` Cole Poirier
2020-06-09 21:48       ` Luke Kenneth Casson Leighton
2020-06-09 22:07         ` Luke Kenneth Casson Leighton
2020-06-10  0:38         ` Cole Poirier
2020-06-10 13:16           ` Luke Kenneth Casson Leighton
2020-06-10 18:53         ` Michael Nolan
2020-06-10 21:30           ` Cole Poirier
2020-06-09 21:49 Alain D D Williams
2020-06-09 22:48 ` Luke Kenneth Casson Leighton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAPweEDwoNNgwcPb8SdBb8y_ZFTYCcwSYNiCniER-DWqxByj=bw@mail.gmail.com' \
    --to=lkcl@lkcl.net \
    --cc=libre-riscv-dev@lists.libre-riscv.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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