... and add aarch32 to specifically refer to the 32-bit ones. Previously, 'arm' meant only 32-bit architectures and there was no way for a module to build with both 32 and 64 bit ARM architectures. Now a module that is intended to work on both architectures can specify requires arm whereas a module only for 32-bit platforms can say requires aarch32 and just like before, 64-bit only can say requires aarch64
Details
Details
- Reviewers
rsmith
Diff Detail
Diff Detail
- Repository
- rL LLVM
Event Timeline
lib/Basic/Targets.cpp | ||
---|---|---|
4552 | Should we also recognize "arm32" to better mirror the 64-bit case? |
lib/Basic/Targets.cpp | ||
---|---|---|
4552 | Kristof convinced me it was better to stick with aarch32 since it had a defined meaning unlike arm32 (and unlike arm64 there is no compatibility or historical reason for it). |
Should we also recognize "arm32" to better mirror the 64-bit case?