hvdijk added a comment. In D52050#2466874 <https://reviews.llvm.org/D52050#2466874>, @glaubitz wrote:
> However, that's not the same as whether we're on an x86_64 system or on an > x32 system determines which GNU triplet to use and which include and library > search paths are our primary ones. I don't see why it should? When you target i386-linux-gnu, you can use objects from /usr/lib/gcc/i386-linux-gnu/*, /usr/lib/gcc/x86_64-linux-gnu/*/32, and /usr/lib/gcc/x86_64-linux-gnux32/*/32. When you target x86_64-linux-gnu, you can use objects from /usr/lib/gcc/x86_64-linux-gnu/*, /usr/lib/gcc/x86_64-linux-gnux32/*/64, and /usr/lib/gcc/i386-linux-gnu/*/64. When you target x86_64-linux-gnux32, you can use objects from /usr/lib/gcc/x86_64-linux-gnux32/*, /usr/lib/gcc/x86_64-linux-gnu/*/x32, and /usr/lib/gcc/i386-linux-gnu/*/x32. All cases should be read to include all variants of the triples as well. None of that depends on the LLVM host architecture, does it? The LLVM host architecture makes it more or less likely that a GCC installation will be found in any of the listed directories, but not how it should be handled if found. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D52050/new/ https://reviews.llvm.org/D52050 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
