Hi I saw there is no one target passes driver's `-mabi` option to LTO code generation, ex. pass driver option `-mabi=ooo` as `-plugin-opt=-target-abi=ooo` to LTO. Does anyone know the reason for this? I know there are some options are encoded in bitcode function attributes (ex. `-target-feature`, `-Os`, `-Oz`), but I didn't see `-mabi`, is it a good idea to pass `-mabi` vai option only for specific target? or maybe usually targets use `-triple` and `-mcpu` to decide `-mabi`? Thanks. Regards Zakk Chen -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20191201/4475d2cc/attachment.html>