diff options
| author | Hafiz Abid Qadeer <abidh@codesourcery.com> | 2020-11-26 11:31:45 +0000 |
|---|---|---|
| committer | Hafiz Abid Qadeer <abidh@codesourcery.com> | 2020-11-26 11:43:17 +0000 |
| commit | 45ba2392d7e00aedd4d9fb04070dbae8a7fbbeeb (patch) | |
| tree | d7dc5fbca9dadf49b8bbf3502140528f53df714d /clang/lib/Frontend/CompilerInvocation.cpp | |
| parent | 5641b1dfddff847f7f3edc484537f9314c283225 (diff) | |
| download | llvm-45ba2392d7e00aedd4d9fb04070dbae8a7fbbeeb.zip llvm-45ba2392d7e00aedd4d9fb04070dbae8a7fbbeeb.tar.gz llvm-45ba2392d7e00aedd4d9fb04070dbae8a7fbbeeb.tar.bz2 | |
[clang][Driver] Handle risvc in Baremetal.cpp.
I am working on a baremetal riscv toolchain using LLVM runtime and
LLD linker. Baremetal.cpp provides most of the things needed for such
toolchain. So I have modified it to also handle riscv64/32-unknown-elf
targets alongside arm-none-eabi.
Currently, targets like riscv64-unknown-elf are handled by RISCVToolChain
which mostly expects a gcc toolchain to be present. If you dont
want the dependency on gcc-toolchain/libgloss or want to use LLD, then
RISCVToolChain is not a good fit.
So in the toolchain selection code, I have made this dependency of
RISCVToolChain on gcc toolchain explicit. It is created if gcc-toolchain
option is present. Otherwise Baremetal toolchain is created. I will be
happy to hear if there is a better way to choose between these two
toolchains.
Reviewed By: jroelofs
Differential Revision: https://reviews.llvm.org/D91442
Diffstat (limited to 'clang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions