Albert Ou

The actual error is: ``` CXX auto-load.o ... chipyard/toolchains/riscv-tools/riscv-gnu-toolchain/build/../riscv-gdb/gdb/auto-load.c: In function 'int collect_matching_scripts(void**, void*)': chipyard/toolchains/riscv-tools/riscv-gnu-toolchain/build/../riscv-gdb/gdb/auto-load.c:1211:66: error: 're_exec' was not declared in this scope if (script->language == data->language && re_exec (script->name))...

I wasn't able to reproduce the errors on RHEL 6 ELS (6.10). The build succeeds for me on a clean EC2 instance using devtoolset-8. ```sh # RHSCL repository ID is...

riscv-gcc's configure script tests for `-rdynamic` support. Check `chipyard/toolchains/riscv-tools/riscv-gnu-toolchain/build/build-gcc-newlib-stage1/gcc/config.log` to confirm that the intended compiler is being used. Make sure to start from a clean environment. ``` configure:3855: checking for...

Follow the riscv-gnu-toolchain README to install the required dependencies: https://github.com/riscv-collab/riscv-gnu-toolchain#prerequisites The version of GNU m4 shipped with Xcode is evidently too old.

Try installing a newer GNU m4: ```sh brew install m4 ``` ---- It also turns out that the gcc-newlib-stage1 bootstrap later fails on arm64 with a link error: ``` Undefined...

> Unfortunately, something in Linux boot is breaking :/ causing a kernel panic. I'll have to look into if this is a QEMU issue, or more likely an issue with...

Subprojects are statically linked now, so shared libraries are not longer built by default. Here is a patch for dummy_rocc (apply with `git am`): https://gist.github.com/a0u/e7fd476ecb6981a8416108ec3c18e389 This isn't an ideal solution...

This test involves self-modifying code. The instructions from 0x80000100 to 0x8000014c, shown in the assembly below, change `addi a3, a3, 222` into `addi a3, a3, 333`. The `fence.i` should ensure...

The test is written correctly as is. To further explain how it works: 1. Two `lh` instructions load the new instruction bits from the memory location labeled by `insn` (`addi...

@abejgonzalez: Sleeping while holding a spinlock is a recipe for deadlock, especially when kernel preemption has been locally disabled by disabling interrupts. This is why `mutex_lock()` is unsafe to use...