en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/LTO/X86/Inputs/opaque-pointers.ll#850d53a1 LTO: Decide upfront whether to use opaque/non-opaque pointer typesLTO code may end up mixing bitcode files from various sources varying intheir use of opaque pointer types. The current strategy to decidebetween opaque / typed pointers upon the first bitcode file loaded doesnot work here, since we could be loading a non-opaque bitcode file firstand would then be unable to load any files with opaque pointer typeslater.So for LTO this:- Adds an `lto::Config::OpaquePointer` option and enforces an upfront decision between the two modes.- Adds `-opaque-pointers`/`-no-opaque-pointers` options to the gold plugin; disabled by default.- `--opaque-pointers`/`--no-opaque-pointers` options with `-plugin-opt=-opaque-pointers`/`-plugin-opt=-no-opaque-pointers` aliases to lld; disabled by default.- Adds an `-lto-opaque-pointers` option to the `llvm-lto2` tool.- Changes the clang driver to pass `-plugin-opt=-opaque-pointers` to the linker in LTO modes when clang was configured with opaque pointers enabled by default.This fixes https://github.com/llvm/llvm-project/issues/55377Differential Revision: https://reviews.llvm.org/D125847 List of files: /llvm-project-15.0.7/llvm/test/LTO/X86/Inputs/opaque-pointers.ll Wed, 18 May 2022 03:33:22 +0000 Matthias Braun <matze@braunis.de>