ikudrin added a comment. In D149119#4312518 <https://reviews.llvm.org/D149119#4312518>, @simon_tatham wrote:
> Do LLVM's current portability goals include the constraint that you can only > build LLVM for a platform it can also target? If not, then there surely still > needs to be //some// kind of escape hatch so that you can avoid needing > `llvm-nm` to already support the object file format of the host platform. > > I suppose you could say that in that unusual situation it's up to you to > adapt `extract_symbols.py` so that it has some other way to get the answers. If I understand it right, the main targets to use `extract_symbols.py` are AIX and Windows. For both these platforms `llvm-nm` and `llvm-readobj` can be built. Support for more exotic situations can be added relatively easily should it be required. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D149119/new/ https://reviews.llvm.org/D149119 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
