[release] fix docker image builder

[Avimitin]

No description provided.

[Avimitin]

How to use the docker image:

Note

Make sure machine have at least 4 usable cores.

# change these variable to fit the needs.
config=blastoise
ip=t1emu
docker pull ghcr.io/chipsalliance/t1-${config}-${ip}:latest
docker run --name t1 -it --rm ghcr.io/chipsalliance/t1-${config}-${ip}:latest /bin/bash

Inside docker shell, there are four sample source code in /workspace/examples directory. T1 runtime stub are placed under /workspace/share. This docker container ship with a clang wrapper that already handles most of the compiler options, so users can easily compile the example source code, as the following code block shows:

cd /workspace/intrinsic.linear_normalization
ls -al
t1-cc -T /workspace/share/t1.ld linear_normalization.c /workspace/share/main.S -o linear_normalization.elf
t1emu-verilated-simulator +t1_elf_file=linear_normalization.elf

Command explain

• The t1-cc wraps the following clang option:

riscv32-none-elf-clang -I/path/to/t1-runtime/include -L/path/to/t1-runtime/lib -mabi=ilp32f -march=rv32gc_zvl2048b_zve32f -mno-relax -static -mcmodel=medany -fvisibility=hidden -fno-PIC -g -O3 -frandom-seed=<random string>

• simulator binary can differ across container. The t1emu-verilated-simulator handle scalar instruction with Spike and t1rocketemu-verilated-simulator use the Rocket core.

[sequencer]

Please cherry-pick #942 to see if the emulator issue has been resolved.
There should also be a readme.txt in the root dir of the docker image.