When ARCH is specifically set to amd64 (i.e. for a cross tolchain) tc-arch yield unknown, while i.e. gcc cleary states that amd64-*-* is a synonym for x86_64-*-*. So toolchain-funcs should return the same value for both ARCHs. Reproducible: Always
i'm assuming you meant CHOST and not ARCH, and you're referring to the tc-arch & tc-arch-kernel funcs which parse it via tc-ninja_magic_to_arch while it's true the gnuconfig (config.sub) file accepts amd64-* tuples and rewrites them to x86_64, i don't see any value in supporting that in Gentoo. what use cases do you have to warrant this ? seems like pointless pain when 99.9% of the rest of the world uses x86_64-* tuples.
Erh, yes, I indeed meant the part in in ninja_magic_to arch. I consider it rather a question of completness and choice. Anyhow, if it is not supported and won't be supported, I assume it is at least documented properly somewhere?
(In reply to Sven E. from comment #2) the "choice" part is kind of specious don't you think ? as for documentation, i'm not sure what you're looking for ... all Gentoo stages ever released by the project have used x86_64-* tuples. all of our profiles default to x86_64-*. all of our tools have only ever used x86_64-*. it's pretty unlikely you'd use amd64-* by accident. listing it in any documentation would serve just to confuse people rather than contribute anything useful imo.
