Closed bradjc closed 6 years ago
There wasn't a plan, but I am not opposed to it. I would be happy to accept a PR that wraps --enable-multilib
appropriately.
When using a 32-bit flow, it is worth remembering that the appropriate flags must be used everywhere, including even when launching spike or qemu.
Please comment to re-open this if new info to contribute.
Revisiting my old issue I totally forgot I made...
The Tock project is working on embedded OS support, and there is rapidly growing interest in RISC-V based platforms. The kernel uses LLVM, but we want to support GCC for userspace apps written in C. Long story short: it would be great for users to have easy access to a 32 bit RISC-V compiler on mac.
Right now, brew install riscv-gnu-toolchain --with-multilib
works...but takes >30 min on my computer, which isn't very friendly for users. Ideally, there would be a pre-compiled option, since I don't want supporting RISC-V to feel like a burden.
I have three ideas, and I'm interested in what you think:
--enable-multilib
could be set in the formula by default. I'm not actually sure why the toolchain isn't just riscv-unknown-elf-gcc that supports both 64 and 32 always...but I suppose that is a different topic.riscv-gnu-toolchain-multilib.rb
formula.github.com/tock/homebrew-tock
with this hypothetical riscv-gnu-toolchain-multilib.rb formula. I don't think that forking this is good for the RISC-V ecosystem, but it is hypothetically possible.Do you have a preference, or an idea I didn't think of?
Is there any plan to add the 32 bit version of the tools (riscv32-unknown-elf) to the brew install?