Hi! On Tue, Oct 29, 2019 at 06:15:31PM +0100, Jakub Jelinek wrote: > The standard makes it implementation defined what an arch is and what is > isa, but I think because there is no selector like target that arch should > mostly contain identifiers that match the ABI incompatible stuff (target, > perhaps whether it is 32-bit or 64-bit, plus endianity where needed etc.) > and keep isa to be identifiers for the ISAs, or perhaps where there are no > clear ISA names say architecture variants or revisions or similar. > > I've only implemented i386 and nvptx so far, will leave the rest to > port maintainers; would be nice to coordinate what is added a little bit > with other implementations like LLVM, if they'd be willing to coordinate.
What would this be used for? Can you give some more context? There already are a lot of different ways to get information about the execution environment you're running on; why is this any better? Segher
