Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: Jacob Lifshay <programmerjake@gmail.com>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: [libre-riscv-dev] experimental code & monorepo
Date: Sat, 2 May 2020 21:49:15 -0700
Message-ID: <CAC2bXD7fw-mX9F_cNwfZg_dBpoRP-YHBB9vWqHzPLqC--WkUvQ@mail.gmail.com> (raw)
In-Reply-To: <9458BF50-C9A6-44E5-AC7B-4A3891DE6CC1@gatech.edu>

On Sat, May 2, 2020, 11:47 Yehowshua <yimmanuel3@gatech.edu> wrote:

> Also - we have some experimental files in the SOC repo.
> I think it is a good practice to make an experimental branch instead.


> Thoughts?
>

We really should move all code that's not actually used in the final soc to
its own folder or branch -- currently, there is lots of unused code that
either was used in the past or we intend to eventually use or even never
intended to use (lots of minerva and some of the FP code) and was only ever
reference code to base our new code on. All of that makes it very confusing
to newcomers and partially confusing for people who aren't newcomers
anymore -- I myself couldn't point out with any degree of certainty all the
code that we actually intend to use even though I've been here longer than
nearly everyone else.

Additionally, I'd advocate for all HDL code (at least soc, ieee754fpu, and
nmutil) to be moved to one repo (especially including the data files
currently hosted on the wiki -- libre-soc.org shouldn't need to be
online/accessible to build if someone gets the git repos some other way)
and using submodules for often updated external dependencies (nmigen at
least), since that helps tie all the code together so one commit id is
sufficient to describe the state of all the code that's tightly
interconnected. See LLVM switching to a monorepo for an example of how this
is a good idea.

Jacob

>
_______________________________________________
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: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-02 18:45 [libre-riscv-dev] GItlab For SOC repo Yehowshua
2020-05-02 18:47 ` Yehowshua
2020-05-03  4:49   ` Jacob Lifshay [this message]
2020-05-03 11:02     ` [libre-riscv-dev] experimental code & monorepo Luke Kenneth Casson Leighton
2020-05-06  0:08       ` Jacob Lifshay
2020-05-02 19:30 ` [libre-riscv-dev] GItlab For SOC repo 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=CAC2bXD7fw-mX9F_cNwfZg_dBpoRP-YHBB9vWqHzPLqC--WkUvQ@mail.gmail.com \
    --to=programmerjake@gmail.com \
    --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