target-lexicon icon indicating copy to clipboard operation
target-lexicon copied to clipboard

Target "triple" support

Results 8 target-lexicon issues
Sort by recently updated
recently updated
newest added

According to [Apple's documentation](https://developer.apple.com/documentation/xcode/writing-arm64-code-for-apple-platforms), their C data model seems to conform to LP64. [This Wikipedia article](https://en.wikipedia.org/wiki/64-bit_computing#64-bit_data_models) also says that macOS uses LP64. Unless I've missed something, it should be possible...

This PR proposes adding the `riscv32im-risc0-zkvm-elf` target. Unlike the `zkasm` target which may be premature, the risc0 one has been used by developers, can be used to create ZK/blockchain applications...

Currently compiling a program that depends on target-lexicon for `wasm32-wasi-preview1-threads` results in a compile error as the build script can't parse the triple for the target.

I've been playing around with `target-lexicon` a bit and it seems like while most of the time it is pretty faithful to the rustc target json, some of the time...

Would it be possible to add the `xtensa-esp32-espidf` target? It's the target for an esp32 chip with the standard library implemented in espressifs [rust fork](https://github.com/esp-rs/rust).

`avr-unknown-gnu-atmega328` is a new target in rustc. "atmega328" isn't recognized by [LLVM's Triple](https://llvm.org/doxygen/classllvm_1_1Triple.html) or [GNU autotools](https://git.savannah.gnu.org/gitweb/?p=config.git&view=view+git+repository) so it's unclear how to categorize it. I posted [here](https://github.com/rust-lang/rust/pull/74941#issuecomment-712219034) asking for clarification.

Similar to the `CallingConvention` enum and the `default_calling_convention()` method, should we add an `UnwindKind` enum and `default_unwind_kind()` method? One question is, do we need this, or should the unwind kind...

I've been considering if we could get rid of the build script for determining the host architecture, using [`target_*` cfgs](https://doc.rust-lang.org/reference/conditional-compilation.html) instead of parsing the `TARGET`. Something like the following: ```rust...