en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/ThinLTO/X86/reference_non_importable.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/ThinLTO/X86/reference_non_importable.ll Wed, 18 May 2022 03:33:22 +0000 Matthias Braun <matze@braunis.de> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/ThinLTO/X86/reference_non_importable.ll#7b1d7937 Reland "Change the X86 datalayout to add three address spaces for 32 bit signed, 32 bit unsigned, and 64 bit pointers."This reverts 57076d3199fc2b0af4a3736b7749dd5462cacda5.Original review at https://reviews.llvm.org/D64931.Review for added fix at https://reviews.llvm.org/D66843.llvm-svn: 371568 List of files: /llvm-project-15.0.7/llvm/test/ThinLTO/X86/reference_non_importable.ll Tue, 10 Sep 2019 23:15:38 +0000 Amy Huang <akhuang@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/ThinLTO/X86/reference_non_importable.ll#57076d31 Revert "Change the X86 datalayout to add three address spaces for 32 bit signed,"This reverts commit r370083 because it caused check-lld failures onsanitizer-x86_64-linux-fast.llvm-svn: 370142 List of files: /llvm-project-15.0.7/llvm/test/ThinLTO/X86/reference_non_importable.ll Wed, 28 Aug 2019 01:08:54 +0000 Vlad Tsyrklevich <vlad@tsyrklevich.net> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/ThinLTO/X86/reference_non_importable.ll#1299945b Change the X86 datalayout to add three address spaces for 32 bit signed,32 bit unsigned, and 64 bit pointers.llvm-svn: 370083 List of files: /llvm-project-15.0.7/llvm/test/ThinLTO/X86/reference_non_importable.ll Tue, 27 Aug 2019 17:46:53 +0000 Amy Huang <akhuang@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/ThinLTO/X86/reference_non_importable.ll#a5376f39 [LTO] Make processing of combined module more consistentSummary:1. Use stream 0 only for combined module. Previously if combined module was notprocesses ThinLTO used the stream for own output. However small changes in input,could trigger combined module and shuffle outputs making life of llvm::LTO harder.2. Always process combined module and write output to stream 0. Processing emptycombined module is cheap and allows llvm::LTO users to avoid implementing processingwhich is already done in llvm::LTO.Subscribers: mehdi_amini, inglorion, eraman, hiradityaDifferential Revision: https://reviews.llvm.org/D41267llvm-svn: 320905 List of files: /llvm-project-15.0.7/llvm/test/ThinLTO/X86/reference_non_importable.ll Sat, 16 Dec 2017 02:10:00 +0000 Vitaly Buka <vitalybuka@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/ThinLTO/X86/reference_non_importable.ll#4595a915 [LTO][ThinLTO] Use the linker resolutions to mark global values as dso_local.Now that we have a way to mark GlobalValues as local we can use the symbolresolutions that the linker plugin provides as part of lto/thinlto linkstep to refine the compilers view on what symbols will end up being local.Originally commited as r317374, but reverted in r317395 to update some missedtests.Differential Revision: https://reviews.llvm.org/D35702llvm-svn: 317408 List of files: /llvm-project-15.0.7/llvm/test/ThinLTO/X86/reference_non_importable.ll Sat, 04 Nov 2017 17:04:39 +0000 Sean Fertile <sfertile@ca.ibm.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/ThinLTO/X86/reference_non_importable.ll#39770ca0 Revert "[LTO][ThinLTO] Use the linker resolutions to mark global values ..."Changes more tests then expected on one of the build bots.reverting to investigate.This reverts https://llvm.org/svn/llvm-project/llvm/trunk@317374llvm-svn: 317395 List of files: /llvm-project-15.0.7/llvm/test/ThinLTO/X86/reference_non_importable.ll Sat, 04 Nov 2017 01:54:20 +0000 Sean Fertile <sfertile@ca.ibm.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/ThinLTO/X86/reference_non_importable.ll#36528c2a [LTO][ThinLTO] Use the linker resolutions to mark global values as dso_local.Now that we have a way to mark GlobalValues as local we can use the symbolresolutions that the linker plugin provides as part of lto/thinlto linkstep to refine the compilers view on what symbols will end up being local.Differential Revision: https://reviews.llvm.org/D35702llvm-svn: 317374 List of files: /llvm-project-15.0.7/llvm/test/ThinLTO/X86/reference_non_importable.ll Fri, 03 Nov 2017 21:45:55 +0000 Sean Fertile <sfertile@ca.ibm.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/ThinLTO/X86/reference_non_importable.ll#7faa60c4 llvm-lto2: Move the LTO::run() action behind a subcommand.Move LTO::run() to a "run" subcommand so that we can introduce new subcommandsfor testing different parts of the LTO implementation.This doesn't use llvm::cl subcommands because it doesn't appear to be currentlypossible to pass an argument not associated with a subcommand to a subcommand(e.g. -lto-use-new-pm, -mcpu=yonah).Differential Revision: https://reviews.llvm.org/D31410llvm-svn: 299967 List of files: /llvm-project-15.0.7/llvm/test/ThinLTO/X86/reference_non_importable.ll Tue, 11 Apr 2017 18:12:00 +0000 Peter Collingbourne <peter@pcc.me.uk> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/ThinLTO/X86/reference_non_importable.ll#185b4ab6 [ThinLTO] Stop importing constant global vars as copies in the backendSummary:We were doing an optimization in the ThinLTO backends of importingconstant unnamed_addr globals unconditionally as a local copy (regardlessof whether the thin link decided to import them). This should be done inthe thin link instead, so that resulting exported references are markedand promoted appropriately, but will need a summary enhancement to markthese variables as constant unnamed_addr.The function import logic during the thin link was trying to handlethis proactively, by conservatively marking all values referenced inthe initializer lists of exported global variables as also exported.However, this only handled values referenced directly from theinitializer list of an exported global variable. If the value is itselfa constant unnamed_addr variable, we could end up exporting itsreferences as well. This caused multiple issues. The first is that thetransitively exported references weren't promoted. Secondly, some couldnot be promoted/renamed (e.g. they had a section or other constraint).recursively, instead of just adding the first level of initializer listreferences to the ExportList directly.Remove this optimization and the associated handling in the functionimport backend. SPEC measurements indicate we weren't getting muchfrom it in any case.Fixes PR31052.Reviewers: mehdi_aminiSubscribers: krasin, llvm-commitsDifferential Revision: https://reviews.llvm.org/D26880llvm-svn: 288446 List of files: /llvm-project-15.0.7/llvm/test/ThinLTO/X86/reference_non_importable.ll Fri, 02 Dec 2016 01:02:30 +0000 Teresa Johnson <tejohnson@google.com>