On the release of clash-cores

[martijnbastiaan]

Tasks:

• Move clash-cores/ to clash-lang/clash-cores
  • Create repo
  • Remove code from clash-lang/clash-compiler: note that clash-testsuite also refers to clash-cores
• Setup CI on clash-lang/clash-cores
• Decide which cores are experimental / likely to change and mark them as internal/experimental
• Resolve issues with building under Clash 1.8:
  (resolve could mean: fix bugs, release Clash 1.10 and use that, disable problematic cores for 1.8 specifically)
  • Unmatchable constant as case subject #2806
  • tuple3_0_sel0_std_logic_vector is not declared #2807
  • Ila output test fragile clash-cores#9
• Decide on licence for clash-cores

[DigitalBrains1]

I think it would be good if we could merge the fourmolu formatting PR on clash-compiler before we split the repo's, so there is no need for another .git-blame-ignore-revs file in the new repo. But it's not a really big issue, just a nice-to-have.

[DigitalBrains1]

Do we want to split off the full history of everything happening in clash-compiler/clash-cores into the new repository, using git subtree?

Or do we want a new initial commit on the new repo with all the code as it currently is, and direct people to clash-compiler for the history before that?

@t-wallet and I both prefer the first.

[jvnknvlgl]

I have added a clash-cores label to mark everything that needs to be moved to the new repository when the time is there.

[leonschoorl]

There are still many references to clash-cores in the CI infra:

clash-compiler/.github/workflows/ci.yml

Lines 221 to 222 in 5927123

	cabal v2-run clash-cores:doctests
	cabal v2-run clash-cores:unittests -- --hide-successes

clash-compiler/.ci/gitlab/test.yml

Lines 94 to 97 in 5927123

	cores:doctests:
	extends: .test-nocache
	script:
	- bin/clash-cores:doctests -j$THREADS

clash-compiler/.ci/gitlab/test.yml

Lines 99 to 102 in 5927123

	cores:unittests:
	extends: .test-nocache
	script:
	- bin/clash-cores:unittests --hide-successes

clash-compiler/.ci/gitlab/test.yml

Lines 160 to 169 in 5927123

	# Vivado is quite slow, so we only run a subset of the tests on development branches
	# with it. The full testsuite gets run with Vivado every night on 'master'.
	suite:cores:
	extends: .test-cache-local
	script:
	- source /opt/tools/Xilinx/Vivado/2022.1/settings64.sh
	- bin/clash-testsuite:clash-testsuite -j$THREADS -p Cores --hide-successes --no-modelsim --no-ghdl --no-iverilog --no-verilator --no-symbiyosys
	tags:
	- local
	- vivado-2022.1-standard

That last one is now completely pointless after #2793 got merged.