yota9 wrote: @paschalis-mpeis Could you please check if the binaries are identical and it is indeed nm problem? E.g. with objdump, is plt entry is there? Maybe there is problem related to the plt section type, e.g. one of the binaries has .plt.sec or .plt.got section and there is some kind of but in nm that not lists symbols from these sections. Then we can use custom linker script with .plt section only. My next suggestion would be just using llvm-nm here is to pass llvm-nm with --nmtool arg to link_fdata.py, since the [lit.cfg.py](https://github.com/llvm/llvm-project/blob/main/bolt/test/lit.cfg.py#L118) has it in the list of mandatory tools for bolt testing, so we won't have environment dependencies here. Maybe even add nmtool as an link_fdata_cmd arg in lit.cfg.py , so all test would use it by default...
https://github.com/llvm/llvm-project/pull/135867 _______________________________________________ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
