2015-08-14 22:12:54 +08:00
|
|
|
//===- Config.h -------------------------------------------------*- C++ -*-===//
|
2015-07-25 05:03:07 +08:00
|
|
|
//
|
2019-01-19 16:50:56 +08:00
|
|
|
// Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
|
|
|
|
// See https://llvm.org/LICENSE.txt for license information.
|
|
|
|
// SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
|
2015-07-25 05:03:07 +08:00
|
|
|
//
|
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
|
|
|
|
#ifndef LLD_ELF_CONFIG_H
|
|
|
|
#define LLD_ELF_CONFIG_H
|
|
|
|
|
2018-01-31 17:22:44 +08:00
|
|
|
#include "lld/Common/ErrorHandler.h"
|
2015-11-12 17:52:08 +08:00
|
|
|
#include "llvm/ADT/MapVector.h"
|
2015-07-25 05:03:07 +08:00
|
|
|
#include "llvm/ADT/StringRef.h"
|
2016-12-20 02:00:52 +08:00
|
|
|
#include "llvm/ADT/StringSet.h"
|
2017-06-07 11:48:56 +08:00
|
|
|
#include "llvm/BinaryFormat/ELF.h"
|
2017-03-17 10:24:16 +08:00
|
|
|
#include "llvm/Support/CachePruning.h"
|
2017-03-01 07:43:26 +08:00
|
|
|
#include "llvm/Support/CodeGen.h"
|
2017-03-22 05:40:08 +08:00
|
|
|
#include "llvm/Support/Endian.h"
|
2019-02-06 22:43:30 +08:00
|
|
|
#include <atomic>
|
2015-09-28 21:11:36 +08:00
|
|
|
#include <vector>
|
|
|
|
|
2015-07-25 05:03:07 +08:00
|
|
|
namespace lld {
|
2016-02-28 08:25:54 +08:00
|
|
|
namespace elf {
|
2015-07-25 05:03:07 +08:00
|
|
|
|
2015-10-12 09:55:32 +08:00
|
|
|
class InputFile;
|
2018-04-18 07:30:05 +08:00
|
|
|
class InputSectionBase;
|
2015-10-10 05:12:40 +08:00
|
|
|
|
2015-10-07 17:13:03 +08:00
|
|
|
enum ELFKind {
|
|
|
|
ELFNoneKind,
|
|
|
|
ELF32LEKind,
|
|
|
|
ELF32BEKind,
|
|
|
|
ELF64LEKind,
|
|
|
|
ELF64BEKind
|
|
|
|
};
|
|
|
|
|
2016-08-31 16:38:11 +08:00
|
|
|
// For --build-id.
|
2016-09-14 19:32:57 +08:00
|
|
|
enum class BuildIdKind { None, Fast, Md5, Sha1, Hexstring, Uuid };
|
2016-04-08 06:49:21 +08:00
|
|
|
|
2017-01-26 05:23:06 +08:00
|
|
|
// For --discard-{all,locals,none}.
|
|
|
|
enum class DiscardPolicy { Default, All, Locals, None };
|
2016-08-31 16:46:30 +08:00
|
|
|
|
2018-07-19 06:49:31 +08:00
|
|
|
// For --icf={none,safe,all}.
|
|
|
|
enum class ICFLevel { None, Safe, All };
|
|
|
|
|
2016-08-31 16:38:11 +08:00
|
|
|
// For --strip-{all,debug}.
|
|
|
|
enum class StripPolicy { None, All, Debug };
|
|
|
|
|
|
|
|
// For --unresolved-symbols.
|
2018-08-14 19:55:31 +08:00
|
|
|
enum class UnresolvedPolicy { ReportError, Warn, Ignore };
|
2016-06-29 20:35:04 +08:00
|
|
|
|
2017-10-25 23:20:30 +08:00
|
|
|
// For --orphan-handling.
|
|
|
|
enum class OrphanHandlingPolicy { Place, Warn, Error };
|
|
|
|
|
2016-09-17 04:21:55 +08:00
|
|
|
// For --sort-section and linkerscript sorting rules.
|
2016-09-17 05:14:55 +08:00
|
|
|
enum class SortSectionPolicy { Default, None, Alignment, Name, Priority };
|
2016-09-17 04:21:55 +08:00
|
|
|
|
2016-10-18 02:12:24 +08:00
|
|
|
// For --target2
|
|
|
|
enum class Target2Policy { Abs, Rel, GotRel };
|
|
|
|
|
2018-07-31 21:41:59 +08:00
|
|
|
// For tracking ARM Float Argument PCS
|
|
|
|
enum class ARMVFPArgKind { Default, Base, VFP, ToolChain };
|
|
|
|
|
2016-07-16 20:26:39 +08:00
|
|
|
struct SymbolVersion {
|
[Coding style change] Rename variables so that they start with a lowercase letter
This patch is mechanically generated by clang-llvm-rename tool that I wrote
using Clang Refactoring Engine just for creating this patch. You can see the
source code of the tool at https://reviews.llvm.org/D64123. There's no manual
post-processing; you can generate the same patch by re-running the tool against
lld's code base.
Here is the main discussion thread to change the LLVM coding style:
https://lists.llvm.org/pipermail/llvm-dev/2019-February/130083.html
In the discussion thread, I proposed we use lld as a testbed for variable
naming scheme change, and this patch does that.
I chose to rename variables so that they are in camelCase, just because that
is a minimal change to make variables to start with a lowercase letter.
Note to downstream patch maintainers: if you are maintaining a downstream lld
repo, just rebasing ahead of this commit would cause massive merge conflicts
because this patch essentially changes every line in the lld subdirectory. But
there's a remedy.
clang-llvm-rename tool is a batch tool, so you can rename variables in your
downstream repo with the tool. Given that, here is how to rebase your repo to
a commit after the mass renaming:
1. rebase to the commit just before the mass variable renaming,
2. apply the tool to your downstream repo to mass-rename variables locally, and
3. rebase again to the head.
Most changes made by the tool should be identical for a downstream repo and
for the head, so at the step 3, almost all changes should be merged and
disappear. I'd expect that there would be some lines that you need to merge by
hand, but that shouldn't be too many.
Differential Revision: https://reviews.llvm.org/D64121
llvm-svn: 365595
2019-07-10 13:00:37 +08:00
|
|
|
llvm::StringRef name;
|
|
|
|
bool isExternCpp;
|
|
|
|
bool hasWildcard;
|
2016-07-16 20:26:39 +08:00
|
|
|
};
|
|
|
|
|
2016-06-20 19:55:12 +08:00
|
|
|
// This struct contains symbols version definition that
|
|
|
|
// can be found in version script if it is used for link.
|
2016-07-16 12:02:00 +08:00
|
|
|
struct VersionDefinition {
|
[Coding style change] Rename variables so that they start with a lowercase letter
This patch is mechanically generated by clang-llvm-rename tool that I wrote
using Clang Refactoring Engine just for creating this patch. You can see the
source code of the tool at https://reviews.llvm.org/D64123. There's no manual
post-processing; you can generate the same patch by re-running the tool against
lld's code base.
Here is the main discussion thread to change the LLVM coding style:
https://lists.llvm.org/pipermail/llvm-dev/2019-February/130083.html
In the discussion thread, I proposed we use lld as a testbed for variable
naming scheme change, and this patch does that.
I chose to rename variables so that they are in camelCase, just because that
is a minimal change to make variables to start with a lowercase letter.
Note to downstream patch maintainers: if you are maintaining a downstream lld
repo, just rebasing ahead of this commit would cause massive merge conflicts
because this patch essentially changes every line in the lld subdirectory. But
there's a remedy.
clang-llvm-rename tool is a batch tool, so you can rename variables in your
downstream repo with the tool. Given that, here is how to rebase your repo to
a commit after the mass renaming:
1. rebase to the commit just before the mass variable renaming,
2. apply the tool to your downstream repo to mass-rename variables locally, and
3. rebase again to the head.
Most changes made by the tool should be identical for a downstream repo and
for the head, so at the step 3, almost all changes should be merged and
disappear. I'd expect that there would be some lines that you need to merge by
hand, but that shouldn't be too many.
Differential Revision: https://reviews.llvm.org/D64121
llvm-svn: 365595
2019-07-10 13:00:37 +08:00
|
|
|
llvm::StringRef name;
|
|
|
|
uint16_t id = 0;
|
|
|
|
std::vector<SymbolVersion> globals;
|
2016-06-20 19:55:12 +08:00
|
|
|
};
|
|
|
|
|
2016-01-06 01:55:05 +08:00
|
|
|
// This struct contains the global configuration for the linker.
|
|
|
|
// Most fields are direct mapping from the command line options
|
|
|
|
// and such fields have the same name as the corresponding options.
|
|
|
|
// Most fields are initialized by the driver.
|
2015-07-25 05:03:07 +08:00
|
|
|
struct Configuration {
|
[Coding style change] Rename variables so that they start with a lowercase letter
This patch is mechanically generated by clang-llvm-rename tool that I wrote
using Clang Refactoring Engine just for creating this patch. You can see the
source code of the tool at https://reviews.llvm.org/D64123. There's no manual
post-processing; you can generate the same patch by re-running the tool against
lld's code base.
Here is the main discussion thread to change the LLVM coding style:
https://lists.llvm.org/pipermail/llvm-dev/2019-February/130083.html
In the discussion thread, I proposed we use lld as a testbed for variable
naming scheme change, and this patch does that.
I chose to rename variables so that they are in camelCase, just because that
is a minimal change to make variables to start with a lowercase letter.
Note to downstream patch maintainers: if you are maintaining a downstream lld
repo, just rebasing ahead of this commit would cause massive merge conflicts
because this patch essentially changes every line in the lld subdirectory. But
there's a remedy.
clang-llvm-rename tool is a batch tool, so you can rename variables in your
downstream repo with the tool. Given that, here is how to rebase your repo to
a commit after the mass renaming:
1. rebase to the commit just before the mass variable renaming,
2. apply the tool to your downstream repo to mass-rename variables locally, and
3. rebase again to the head.
Most changes made by the tool should be identical for a downstream repo and
for the head, so at the step 3, almost all changes should be merged and
disappear. I'd expect that there would be some lines that you need to merge by
hand, but that shouldn't be too many.
Differential Revision: https://reviews.llvm.org/D64121
llvm-svn: 365595
2019-07-10 13:00:37 +08:00
|
|
|
uint8_t osabi = 0;
|
|
|
|
uint32_t andFeatures = 0;
|
|
|
|
llvm::CachePruningPolicy thinLTOCachePolicy;
|
|
|
|
llvm::StringMap<uint64_t> sectionStartMap;
|
|
|
|
llvm::StringRef chroot;
|
|
|
|
llvm::StringRef dynamicLinker;
|
|
|
|
llvm::StringRef dwoDir;
|
|
|
|
llvm::StringRef entry;
|
|
|
|
llvm::StringRef emulation;
|
|
|
|
llvm::StringRef fini;
|
|
|
|
llvm::StringRef init;
|
|
|
|
llvm::StringRef ltoAAPipeline;
|
|
|
|
llvm::StringRef ltoCSProfileFile;
|
|
|
|
llvm::StringRef ltoNewPmPasses;
|
|
|
|
llvm::StringRef ltoObjPath;
|
|
|
|
llvm::StringRef ltoSampleProfile;
|
|
|
|
llvm::StringRef mapFile;
|
|
|
|
llvm::StringRef outputFile;
|
|
|
|
llvm::StringRef optRemarksFilename;
|
|
|
|
llvm::StringRef optRemarksPasses;
|
|
|
|
llvm::StringRef optRemarksFormat;
|
|
|
|
llvm::StringRef progName;
|
|
|
|
llvm::StringRef printSymbolOrder;
|
|
|
|
llvm::StringRef soName;
|
|
|
|
llvm::StringRef sysroot;
|
|
|
|
llvm::StringRef thinLTOCacheDir;
|
|
|
|
llvm::StringRef thinLTOIndexOnlyArg;
|
|
|
|
std::pair<llvm::StringRef, llvm::StringRef> thinLTOObjectSuffixReplace;
|
|
|
|
std::pair<llvm::StringRef, llvm::StringRef> thinLTOPrefixReplace;
|
|
|
|
std::string rpath;
|
|
|
|
std::vector<VersionDefinition> versionDefinitions;
|
|
|
|
std::vector<llvm::StringRef> auxiliaryList;
|
|
|
|
std::vector<llvm::StringRef> filterList;
|
|
|
|
std::vector<llvm::StringRef> searchPaths;
|
|
|
|
std::vector<llvm::StringRef> symbolOrderingFile;
|
|
|
|
std::vector<llvm::StringRef> undefined;
|
|
|
|
std::vector<SymbolVersion> dynamicList;
|
|
|
|
std::vector<SymbolVersion> versionScriptGlobals;
|
|
|
|
std::vector<SymbolVersion> versionScriptLocals;
|
|
|
|
std::vector<uint8_t> buildIdVector;
|
2018-04-18 07:30:05 +08:00
|
|
|
llvm::MapVector<std::pair<const InputSectionBase *, const InputSectionBase *>,
|
|
|
|
uint64_t>
|
[Coding style change] Rename variables so that they start with a lowercase letter
This patch is mechanically generated by clang-llvm-rename tool that I wrote
using Clang Refactoring Engine just for creating this patch. You can see the
source code of the tool at https://reviews.llvm.org/D64123. There's no manual
post-processing; you can generate the same patch by re-running the tool against
lld's code base.
Here is the main discussion thread to change the LLVM coding style:
https://lists.llvm.org/pipermail/llvm-dev/2019-February/130083.html
In the discussion thread, I proposed we use lld as a testbed for variable
naming scheme change, and this patch does that.
I chose to rename variables so that they are in camelCase, just because that
is a minimal change to make variables to start with a lowercase letter.
Note to downstream patch maintainers: if you are maintaining a downstream lld
repo, just rebasing ahead of this commit would cause massive merge conflicts
because this patch essentially changes every line in the lld subdirectory. But
there's a remedy.
clang-llvm-rename tool is a batch tool, so you can rename variables in your
downstream repo with the tool. Given that, here is how to rebase your repo to
a commit after the mass renaming:
1. rebase to the commit just before the mass variable renaming,
2. apply the tool to your downstream repo to mass-rename variables locally, and
3. rebase again to the head.
Most changes made by the tool should be identical for a downstream repo and
for the head, so at the step 3, almost all changes should be merged and
disappear. I'd expect that there would be some lines that you need to merge by
hand, but that shouldn't be too many.
Differential Revision: https://reviews.llvm.org/D64121
llvm-svn: 365595
2019-07-10 13:00:37 +08:00
|
|
|
callGraphProfile;
|
|
|
|
bool allowMultipleDefinition;
|
|
|
|
bool allowShlibUndefined;
|
|
|
|
bool androidPackDynRelocs;
|
|
|
|
bool armHasBlx = false;
|
|
|
|
bool armHasMovtMovw = false;
|
|
|
|
bool armJ1J2BranchEncoding = false;
|
|
|
|
bool asNeeded = false;
|
|
|
|
bool bsymbolic;
|
|
|
|
bool bsymbolicFunctions;
|
|
|
|
bool callGraphProfileSort;
|
|
|
|
bool checkSections;
|
|
|
|
bool compressDebugSections;
|
|
|
|
bool cref;
|
|
|
|
bool defineCommon;
|
|
|
|
bool demangle = true;
|
|
|
|
bool dependentLibraries;
|
|
|
|
bool disableVerify;
|
|
|
|
bool ehFrameHdr;
|
|
|
|
bool emitLLVM;
|
|
|
|
bool emitRelocs;
|
|
|
|
bool enableNewDtags;
|
|
|
|
bool executeOnly;
|
|
|
|
bool exportDynamic;
|
|
|
|
bool fixCortexA53Errata843419;
|
|
|
|
bool forceBTI;
|
|
|
|
bool formatBinary = false;
|
|
|
|
bool requireCET;
|
|
|
|
bool gcSections;
|
|
|
|
bool gdbIndex;
|
|
|
|
bool gnuHash = false;
|
|
|
|
bool gnuUnique;
|
|
|
|
bool hasDynamicList = false;
|
|
|
|
bool hasDynSymTab;
|
|
|
|
bool ignoreDataAddressEquality;
|
|
|
|
bool ignoreFunctionAddressEquality;
|
|
|
|
bool ltoCSProfileGenerate;
|
|
|
|
bool ltoDebugPassManager;
|
|
|
|
bool ltoNewPassManager;
|
|
|
|
bool mergeArmExidx;
|
|
|
|
bool mipsN32Abi = false;
|
|
|
|
bool nmagic;
|
|
|
|
bool noinhibitExec;
|
|
|
|
bool nostdlib;
|
|
|
|
bool oFormatBinary;
|
|
|
|
bool omagic;
|
|
|
|
bool optRemarksWithHotness;
|
|
|
|
bool pacPlt;
|
|
|
|
bool picThunk;
|
|
|
|
bool pie;
|
|
|
|
bool printGcSections;
|
|
|
|
bool printIcfSections;
|
|
|
|
bool relocatable;
|
|
|
|
bool relrPackDynRelocs;
|
|
|
|
bool saveTemps;
|
|
|
|
bool singleRoRx;
|
|
|
|
bool shared;
|
|
|
|
bool isStatic = false;
|
|
|
|
bool sysvHash = false;
|
|
|
|
bool target1Rel;
|
|
|
|
bool trace;
|
|
|
|
bool thinLTOEmitImportsFiles;
|
|
|
|
bool thinLTOIndexOnly;
|
|
|
|
bool tocOptimize;
|
|
|
|
bool undefinedVersion;
|
|
|
|
bool useAndroidRelrTags = false;
|
|
|
|
bool warnBackrefs;
|
|
|
|
bool warnCommon;
|
|
|
|
bool warnIfuncTextrel;
|
|
|
|
bool warnMissingEntry;
|
|
|
|
bool warnSymbolOrdering;
|
|
|
|
bool writeAddends;
|
|
|
|
bool zCombreloc;
|
|
|
|
bool zCopyreloc;
|
|
|
|
bool zExecstack;
|
|
|
|
bool zGlobal;
|
|
|
|
bool zHazardplt;
|
|
|
|
bool zIfuncNoplt;
|
|
|
|
bool zInitfirst;
|
|
|
|
bool zInterpose;
|
|
|
|
bool zKeepTextSectionPrefix;
|
|
|
|
bool zNodefaultlib;
|
|
|
|
bool zNodelete;
|
|
|
|
bool zNodlopen;
|
|
|
|
bool zNow;
|
|
|
|
bool zOrigin;
|
|
|
|
bool zRelro;
|
|
|
|
bool zRodynamic;
|
|
|
|
bool zText;
|
|
|
|
bool zRetpolineplt;
|
|
|
|
bool zWxneeded;
|
|
|
|
DiscardPolicy discard;
|
|
|
|
ICFLevel icf;
|
|
|
|
OrphanHandlingPolicy orphanHandling;
|
|
|
|
SortSectionPolicy sortSection;
|
|
|
|
StripPolicy strip;
|
|
|
|
UnresolvedPolicy unresolvedSymbols;
|
|
|
|
Target2Policy target2;
|
|
|
|
ARMVFPArgKind armVFPArgs = ARMVFPArgKind::Default;
|
|
|
|
BuildIdKind buildId = BuildIdKind::None;
|
|
|
|
ELFKind ekind = ELFNoneKind;
|
|
|
|
uint16_t defaultSymbolVersion = llvm::ELF::VER_NDX_GLOBAL;
|
|
|
|
uint16_t emachine = llvm::ELF::EM_NONE;
|
|
|
|
llvm::Optional<uint64_t> imageBase;
|
|
|
|
uint64_t commonPageSize;
|
|
|
|
uint64_t maxPageSize;
|
|
|
|
uint64_t mipsGotSize;
|
|
|
|
uint64_t zStackSize;
|
|
|
|
unsigned ltoPartitions;
|
|
|
|
unsigned ltoo;
|
|
|
|
unsigned optimize;
|
|
|
|
unsigned thinLTOJobs;
|
|
|
|
int32_t splitStackAdjustSize;
|
2017-02-14 13:45:47 +08:00
|
|
|
|
2017-03-18 07:29:01 +08:00
|
|
|
// The following config options do not directly correspond to any
|
|
|
|
// particualr command line options.
|
2017-03-15 17:12:56 +08:00
|
|
|
|
2017-03-18 07:29:01 +08:00
|
|
|
// True if we need to pass through relocations in input files to the
|
|
|
|
// output file. Usually false because we consume relocations.
|
[Coding style change] Rename variables so that they start with a lowercase letter
This patch is mechanically generated by clang-llvm-rename tool that I wrote
using Clang Refactoring Engine just for creating this patch. You can see the
source code of the tool at https://reviews.llvm.org/D64123. There's no manual
post-processing; you can generate the same patch by re-running the tool against
lld's code base.
Here is the main discussion thread to change the LLVM coding style:
https://lists.llvm.org/pipermail/llvm-dev/2019-February/130083.html
In the discussion thread, I proposed we use lld as a testbed for variable
naming scheme change, and this patch does that.
I chose to rename variables so that they are in camelCase, just because that
is a minimal change to make variables to start with a lowercase letter.
Note to downstream patch maintainers: if you are maintaining a downstream lld
repo, just rebasing ahead of this commit would cause massive merge conflicts
because this patch essentially changes every line in the lld subdirectory. But
there's a remedy.
clang-llvm-rename tool is a batch tool, so you can rename variables in your
downstream repo with the tool. Given that, here is how to rebase your repo to
a commit after the mass renaming:
1. rebase to the commit just before the mass variable renaming,
2. apply the tool to your downstream repo to mass-rename variables locally, and
3. rebase again to the head.
Most changes made by the tool should be identical for a downstream repo and
for the head, so at the step 3, almost all changes should be merged and
disappear. I'd expect that there would be some lines that you need to merge by
hand, but that shouldn't be too many.
Differential Revision: https://reviews.llvm.org/D64121
llvm-svn: 365595
2019-07-10 13:00:37 +08:00
|
|
|
bool copyRelocs;
|
2017-03-18 07:28:41 +08:00
|
|
|
|
2017-03-22 08:01:11 +08:00
|
|
|
// True if the target is ELF64. False if ELF32.
|
[Coding style change] Rename variables so that they start with a lowercase letter
This patch is mechanically generated by clang-llvm-rename tool that I wrote
using Clang Refactoring Engine just for creating this patch. You can see the
source code of the tool at https://reviews.llvm.org/D64123. There's no manual
post-processing; you can generate the same patch by re-running the tool against
lld's code base.
Here is the main discussion thread to change the LLVM coding style:
https://lists.llvm.org/pipermail/llvm-dev/2019-February/130083.html
In the discussion thread, I proposed we use lld as a testbed for variable
naming scheme change, and this patch does that.
I chose to rename variables so that they are in camelCase, just because that
is a minimal change to make variables to start with a lowercase letter.
Note to downstream patch maintainers: if you are maintaining a downstream lld
repo, just rebasing ahead of this commit would cause massive merge conflicts
because this patch essentially changes every line in the lld subdirectory. But
there's a remedy.
clang-llvm-rename tool is a batch tool, so you can rename variables in your
downstream repo with the tool. Given that, here is how to rebase your repo to
a commit after the mass renaming:
1. rebase to the commit just before the mass variable renaming,
2. apply the tool to your downstream repo to mass-rename variables locally, and
3. rebase again to the head.
Most changes made by the tool should be identical for a downstream repo and
for the head, so at the step 3, almost all changes should be merged and
disappear. I'd expect that there would be some lines that you need to merge by
hand, but that shouldn't be too many.
Differential Revision: https://reviews.llvm.org/D64121
llvm-svn: 365595
2019-07-10 13:00:37 +08:00
|
|
|
bool is64;
|
2017-03-22 08:01:11 +08:00
|
|
|
|
|
|
|
// True if the target is little-endian. False if big-endian.
|
[Coding style change] Rename variables so that they start with a lowercase letter
This patch is mechanically generated by clang-llvm-rename tool that I wrote
using Clang Refactoring Engine just for creating this patch. You can see the
source code of the tool at https://reviews.llvm.org/D64123. There's no manual
post-processing; you can generate the same patch by re-running the tool against
lld's code base.
Here is the main discussion thread to change the LLVM coding style:
https://lists.llvm.org/pipermail/llvm-dev/2019-February/130083.html
In the discussion thread, I proposed we use lld as a testbed for variable
naming scheme change, and this patch does that.
I chose to rename variables so that they are in camelCase, just because that
is a minimal change to make variables to start with a lowercase letter.
Note to downstream patch maintainers: if you are maintaining a downstream lld
repo, just rebasing ahead of this commit would cause massive merge conflicts
because this patch essentially changes every line in the lld subdirectory. But
there's a remedy.
clang-llvm-rename tool is a batch tool, so you can rename variables in your
downstream repo with the tool. Given that, here is how to rebase your repo to
a commit after the mass renaming:
1. rebase to the commit just before the mass variable renaming,
2. apply the tool to your downstream repo to mass-rename variables locally, and
3. rebase again to the head.
Most changes made by the tool should be identical for a downstream repo and
for the head, so at the step 3, almost all changes should be merged and
disappear. I'd expect that there would be some lines that you need to merge by
hand, but that shouldn't be too many.
Differential Revision: https://reviews.llvm.org/D64121
llvm-svn: 365595
2019-07-10 13:00:37 +08:00
|
|
|
bool isLE;
|
2017-03-18 07:29:01 +08:00
|
|
|
|
2019-07-16 13:50:45 +08:00
|
|
|
// endianness::little if isLE is true. endianness::big otherwise.
|
[Coding style change] Rename variables so that they start with a lowercase letter
This patch is mechanically generated by clang-llvm-rename tool that I wrote
using Clang Refactoring Engine just for creating this patch. You can see the
source code of the tool at https://reviews.llvm.org/D64123. There's no manual
post-processing; you can generate the same patch by re-running the tool against
lld's code base.
Here is the main discussion thread to change the LLVM coding style:
https://lists.llvm.org/pipermail/llvm-dev/2019-February/130083.html
In the discussion thread, I proposed we use lld as a testbed for variable
naming scheme change, and this patch does that.
I chose to rename variables so that they are in camelCase, just because that
is a minimal change to make variables to start with a lowercase letter.
Note to downstream patch maintainers: if you are maintaining a downstream lld
repo, just rebasing ahead of this commit would cause massive merge conflicts
because this patch essentially changes every line in the lld subdirectory. But
there's a remedy.
clang-llvm-rename tool is a batch tool, so you can rename variables in your
downstream repo with the tool. Given that, here is how to rebase your repo to
a commit after the mass renaming:
1. rebase to the commit just before the mass variable renaming,
2. apply the tool to your downstream repo to mass-rename variables locally, and
3. rebase again to the head.
Most changes made by the tool should be identical for a downstream repo and
for the head, so at the step 3, almost all changes should be merged and
disappear. I'd expect that there would be some lines that you need to merge by
hand, but that shouldn't be too many.
Differential Revision: https://reviews.llvm.org/D64121
llvm-svn: 365595
2019-07-10 13:00:37 +08:00
|
|
|
llvm::support::endianness endianness;
|
2017-03-22 05:40:08 +08:00
|
|
|
|
2017-03-18 07:29:01 +08:00
|
|
|
// True if the target is the little-endian MIPS64.
|
|
|
|
//
|
|
|
|
// The reason why we have this variable only for the MIPS is because
|
|
|
|
// we use this often. Some ELF headers for MIPS64EL are in a
|
|
|
|
// mixed-endian (which is horrible and I'd say that's a serious spec
|
|
|
|
// bug), and we need to know whether we are reading MIPS ELF files or
|
|
|
|
// not in various places.
|
|
|
|
//
|
|
|
|
// (Note that MIPS64EL is not a typo for MIPS64LE. This is the official
|
|
|
|
// name whatever that means. A fun hypothesis is that "EL" is short for
|
|
|
|
// little-endian written in the little-endian order, but I don't know
|
|
|
|
// if that's true.)
|
[Coding style change] Rename variables so that they start with a lowercase letter
This patch is mechanically generated by clang-llvm-rename tool that I wrote
using Clang Refactoring Engine just for creating this patch. You can see the
source code of the tool at https://reviews.llvm.org/D64123. There's no manual
post-processing; you can generate the same patch by re-running the tool against
lld's code base.
Here is the main discussion thread to change the LLVM coding style:
https://lists.llvm.org/pipermail/llvm-dev/2019-February/130083.html
In the discussion thread, I proposed we use lld as a testbed for variable
naming scheme change, and this patch does that.
I chose to rename variables so that they are in camelCase, just because that
is a minimal change to make variables to start with a lowercase letter.
Note to downstream patch maintainers: if you are maintaining a downstream lld
repo, just rebasing ahead of this commit would cause massive merge conflicts
because this patch essentially changes every line in the lld subdirectory. But
there's a remedy.
clang-llvm-rename tool is a batch tool, so you can rename variables in your
downstream repo with the tool. Given that, here is how to rebase your repo to
a commit after the mass renaming:
1. rebase to the commit just before the mass variable renaming,
2. apply the tool to your downstream repo to mass-rename variables locally, and
3. rebase again to the head.
Most changes made by the tool should be identical for a downstream repo and
for the head, so at the step 3, almost all changes should be merged and
disappear. I'd expect that there would be some lines that you need to merge by
hand, but that shouldn't be too many.
Differential Revision: https://reviews.llvm.org/D64121
llvm-svn: 365595
2019-07-10 13:00:37 +08:00
|
|
|
bool isMips64EL;
|
2017-03-18 07:28:41 +08:00
|
|
|
|
2019-02-07 02:53:17 +08:00
|
|
|
// True if we need to set the DF_STATIC_TLS flag to an output file,
|
|
|
|
// which works as a hint to the dynamic loader that the file contains
|
|
|
|
// code compiled with the static TLS model. The thread-local variable
|
|
|
|
// compiled with the static TLS model is faster but less flexible, and
|
|
|
|
// it may not be loaded using dlopen().
|
|
|
|
//
|
|
|
|
// We set this flag to true when we see a relocation for the static TLS
|
|
|
|
// model. Once this becomes true, it will never become false.
|
|
|
|
//
|
|
|
|
// Since the flag is updated by multi-threaded code, we use std::atomic.
|
|
|
|
// (Writing to a variable is not considered thread-safe even if the
|
2019-02-07 04:36:02 +08:00
|
|
|
// variable is boolean and we always set the same value from all threads.)
|
[Coding style change] Rename variables so that they start with a lowercase letter
This patch is mechanically generated by clang-llvm-rename tool that I wrote
using Clang Refactoring Engine just for creating this patch. You can see the
source code of the tool at https://reviews.llvm.org/D64123. There's no manual
post-processing; you can generate the same patch by re-running the tool against
lld's code base.
Here is the main discussion thread to change the LLVM coding style:
https://lists.llvm.org/pipermail/llvm-dev/2019-February/130083.html
In the discussion thread, I proposed we use lld as a testbed for variable
naming scheme change, and this patch does that.
I chose to rename variables so that they are in camelCase, just because that
is a minimal change to make variables to start with a lowercase letter.
Note to downstream patch maintainers: if you are maintaining a downstream lld
repo, just rebasing ahead of this commit would cause massive merge conflicts
because this patch essentially changes every line in the lld subdirectory. But
there's a remedy.
clang-llvm-rename tool is a batch tool, so you can rename variables in your
downstream repo with the tool. Given that, here is how to rebase your repo to
a commit after the mass renaming:
1. rebase to the commit just before the mass variable renaming,
2. apply the tool to your downstream repo to mass-rename variables locally, and
3. rebase again to the head.
Most changes made by the tool should be identical for a downstream repo and
for the head, so at the step 3, almost all changes should be merged and
disappear. I'd expect that there would be some lines that you need to merge by
hand, but that shouldn't be too many.
Differential Revision: https://reviews.llvm.org/D64121
llvm-svn: 365595
2019-07-10 13:00:37 +08:00
|
|
|
std::atomic<bool> hasStaticTlsModel{false};
|
2019-02-07 02:53:17 +08:00
|
|
|
|
2017-10-25 01:01:40 +08:00
|
|
|
// Holds set of ELF header flags for the target.
|
[Coding style change] Rename variables so that they start with a lowercase letter
This patch is mechanically generated by clang-llvm-rename tool that I wrote
using Clang Refactoring Engine just for creating this patch. You can see the
source code of the tool at https://reviews.llvm.org/D64123. There's no manual
post-processing; you can generate the same patch by re-running the tool against
lld's code base.
Here is the main discussion thread to change the LLVM coding style:
https://lists.llvm.org/pipermail/llvm-dev/2019-February/130083.html
In the discussion thread, I proposed we use lld as a testbed for variable
naming scheme change, and this patch does that.
I chose to rename variables so that they are in camelCase, just because that
is a minimal change to make variables to start with a lowercase letter.
Note to downstream patch maintainers: if you are maintaining a downstream lld
repo, just rebasing ahead of this commit would cause massive merge conflicts
because this patch essentially changes every line in the lld subdirectory. But
there's a remedy.
clang-llvm-rename tool is a batch tool, so you can rename variables in your
downstream repo with the tool. Given that, here is how to rebase your repo to
a commit after the mass renaming:
1. rebase to the commit just before the mass variable renaming,
2. apply the tool to your downstream repo to mass-rename variables locally, and
3. rebase again to the head.
Most changes made by the tool should be identical for a downstream repo and
for the head, so at the step 3, almost all changes should be merged and
disappear. I'd expect that there would be some lines that you need to merge by
hand, but that shouldn't be too many.
Differential Revision: https://reviews.llvm.org/D64121
llvm-svn: 365595
2019-07-10 13:00:37 +08:00
|
|
|
uint32_t eflags = 0;
|
2017-10-02 22:56:41 +08:00
|
|
|
|
2017-03-07 08:43:53 +08:00
|
|
|
// The ELF spec defines two types of relocation table entries, RELA and
|
|
|
|
// REL. RELA is a triplet of (offset, info, addend) while REL is a
|
|
|
|
// tuple of (offset, info). Addends for REL are implicit and read from
|
|
|
|
// the location where the relocations are applied. So, REL is more
|
|
|
|
// compact than RELA but requires a bit of more work to process.
|
|
|
|
//
|
|
|
|
// (From the linker writer's view, this distinction is not necessary.
|
|
|
|
// If the ELF had chosen whichever and sticked with it, it would have
|
|
|
|
// been easier to write code to process relocations, but it's too late
|
|
|
|
// to change the spec.)
|
|
|
|
//
|
2017-03-18 07:29:01 +08:00
|
|
|
// Each ABI defines its relocation type. IsRela is true if target
|
|
|
|
// uses RELA. As far as we know, all 64-bit ABIs are using RELA. A
|
|
|
|
// few 32-bit ABIs are using RELA too.
|
[Coding style change] Rename variables so that they start with a lowercase letter
This patch is mechanically generated by clang-llvm-rename tool that I wrote
using Clang Refactoring Engine just for creating this patch. You can see the
source code of the tool at https://reviews.llvm.org/D64123. There's no manual
post-processing; you can generate the same patch by re-running the tool against
lld's code base.
Here is the main discussion thread to change the LLVM coding style:
https://lists.llvm.org/pipermail/llvm-dev/2019-February/130083.html
In the discussion thread, I proposed we use lld as a testbed for variable
naming scheme change, and this patch does that.
I chose to rename variables so that they are in camelCase, just because that
is a minimal change to make variables to start with a lowercase letter.
Note to downstream patch maintainers: if you are maintaining a downstream lld
repo, just rebasing ahead of this commit would cause massive merge conflicts
because this patch essentially changes every line in the lld subdirectory. But
there's a remedy.
clang-llvm-rename tool is a batch tool, so you can rename variables in your
downstream repo with the tool. Given that, here is how to rebase your repo to
a commit after the mass renaming:
1. rebase to the commit just before the mass variable renaming,
2. apply the tool to your downstream repo to mass-rename variables locally, and
3. rebase again to the head.
Most changes made by the tool should be identical for a downstream repo and
for the head, so at the step 3, almost all changes should be merged and
disappear. I'd expect that there would be some lines that you need to merge by
hand, but that shouldn't be too many.
Differential Revision: https://reviews.llvm.org/D64121
llvm-svn: 365595
2019-07-10 13:00:37 +08:00
|
|
|
bool isRela;
|
2017-03-18 07:29:01 +08:00
|
|
|
|
|
|
|
// True if we are creating position-independent code.
|
[Coding style change] Rename variables so that they start with a lowercase letter
This patch is mechanically generated by clang-llvm-rename tool that I wrote
using Clang Refactoring Engine just for creating this patch. You can see the
source code of the tool at https://reviews.llvm.org/D64123. There's no manual
post-processing; you can generate the same patch by re-running the tool against
lld's code base.
Here is the main discussion thread to change the LLVM coding style:
https://lists.llvm.org/pipermail/llvm-dev/2019-February/130083.html
In the discussion thread, I proposed we use lld as a testbed for variable
naming scheme change, and this patch does that.
I chose to rename variables so that they are in camelCase, just because that
is a minimal change to make variables to start with a lowercase letter.
Note to downstream patch maintainers: if you are maintaining a downstream lld
repo, just rebasing ahead of this commit would cause massive merge conflicts
because this patch essentially changes every line in the lld subdirectory. But
there's a remedy.
clang-llvm-rename tool is a batch tool, so you can rename variables in your
downstream repo with the tool. Given that, here is how to rebase your repo to
a commit after the mass renaming:
1. rebase to the commit just before the mass variable renaming,
2. apply the tool to your downstream repo to mass-rename variables locally, and
3. rebase again to the head.
Most changes made by the tool should be identical for a downstream repo and
for the head, so at the step 3, almost all changes should be merged and
disappear. I'd expect that there would be some lines that you need to merge by
hand, but that shouldn't be too many.
Differential Revision: https://reviews.llvm.org/D64121
llvm-svn: 365595
2019-07-10 13:00:37 +08:00
|
|
|
bool isPic;
|
2017-03-18 07:29:01 +08:00
|
|
|
|
|
|
|
// 4 for ELF32, 8 for ELF64.
|
[Coding style change] Rename variables so that they start with a lowercase letter
This patch is mechanically generated by clang-llvm-rename tool that I wrote
using Clang Refactoring Engine just for creating this patch. You can see the
source code of the tool at https://reviews.llvm.org/D64123. There's no manual
post-processing; you can generate the same patch by re-running the tool against
lld's code base.
Here is the main discussion thread to change the LLVM coding style:
https://lists.llvm.org/pipermail/llvm-dev/2019-February/130083.html
In the discussion thread, I proposed we use lld as a testbed for variable
naming scheme change, and this patch does that.
I chose to rename variables so that they are in camelCase, just because that
is a minimal change to make variables to start with a lowercase letter.
Note to downstream patch maintainers: if you are maintaining a downstream lld
repo, just rebasing ahead of this commit would cause massive merge conflicts
because this patch essentially changes every line in the lld subdirectory. But
there's a remedy.
clang-llvm-rename tool is a batch tool, so you can rename variables in your
downstream repo with the tool. Given that, here is how to rebase your repo to
a commit after the mass renaming:
1. rebase to the commit just before the mass variable renaming,
2. apply the tool to your downstream repo to mass-rename variables locally, and
3. rebase again to the head.
Most changes made by the tool should be identical for a downstream repo and
for the head, so at the step 3, almost all changes should be merged and
disappear. I'd expect that there would be some lines that you need to merge by
hand, but that shouldn't be too many.
Differential Revision: https://reviews.llvm.org/D64121
llvm-svn: 365595
2019-07-10 13:00:37 +08:00
|
|
|
int wordsize;
|
2015-07-25 05:03:07 +08:00
|
|
|
};
|
|
|
|
|
2016-01-06 01:55:05 +08:00
|
|
|
// The only instance of Configuration struct.
|
[Coding style change] Rename variables so that they start with a lowercase letter
This patch is mechanically generated by clang-llvm-rename tool that I wrote
using Clang Refactoring Engine just for creating this patch. You can see the
source code of the tool at https://reviews.llvm.org/D64123. There's no manual
post-processing; you can generate the same patch by re-running the tool against
lld's code base.
Here is the main discussion thread to change the LLVM coding style:
https://lists.llvm.org/pipermail/llvm-dev/2019-February/130083.html
In the discussion thread, I proposed we use lld as a testbed for variable
naming scheme change, and this patch does that.
I chose to rename variables so that they are in camelCase, just because that
is a minimal change to make variables to start with a lowercase letter.
Note to downstream patch maintainers: if you are maintaining a downstream lld
repo, just rebasing ahead of this commit would cause massive merge conflicts
because this patch essentially changes every line in the lld subdirectory. But
there's a remedy.
clang-llvm-rename tool is a batch tool, so you can rename variables in your
downstream repo with the tool. Given that, here is how to rebase your repo to
a commit after the mass renaming:
1. rebase to the commit just before the mass variable renaming,
2. apply the tool to your downstream repo to mass-rename variables locally, and
3. rebase again to the head.
Most changes made by the tool should be identical for a downstream repo and
for the head, so at the step 3, almost all changes should be merged and
disappear. I'd expect that there would be some lines that you need to merge by
hand, but that shouldn't be too many.
Differential Revision: https://reviews.llvm.org/D64121
llvm-svn: 365595
2019-07-10 13:00:37 +08:00
|
|
|
extern Configuration *config;
|
2015-07-25 05:03:07 +08:00
|
|
|
|
[Coding style change] Rename variables so that they start with a lowercase letter
This patch is mechanically generated by clang-llvm-rename tool that I wrote
using Clang Refactoring Engine just for creating this patch. You can see the
source code of the tool at https://reviews.llvm.org/D64123. There's no manual
post-processing; you can generate the same patch by re-running the tool against
lld's code base.
Here is the main discussion thread to change the LLVM coding style:
https://lists.llvm.org/pipermail/llvm-dev/2019-February/130083.html
In the discussion thread, I proposed we use lld as a testbed for variable
naming scheme change, and this patch does that.
I chose to rename variables so that they are in camelCase, just because that
is a minimal change to make variables to start with a lowercase letter.
Note to downstream patch maintainers: if you are maintaining a downstream lld
repo, just rebasing ahead of this commit would cause massive merge conflicts
because this patch essentially changes every line in the lld subdirectory. But
there's a remedy.
clang-llvm-rename tool is a batch tool, so you can rename variables in your
downstream repo with the tool. Given that, here is how to rebase your repo to
a commit after the mass renaming:
1. rebase to the commit just before the mass variable renaming,
2. apply the tool to your downstream repo to mass-rename variables locally, and
3. rebase again to the head.
Most changes made by the tool should be identical for a downstream repo and
for the head, so at the step 3, almost all changes should be merged and
disappear. I'd expect that there would be some lines that you need to merge by
hand, but that shouldn't be too many.
Differential Revision: https://reviews.llvm.org/D64121
llvm-svn: 365595
2019-07-10 13:00:37 +08:00
|
|
|
static inline void errorOrWarn(const Twine &msg) {
|
|
|
|
if (!config->noinhibitExec)
|
|
|
|
error(msg);
|
2018-01-31 17:22:44 +08:00
|
|
|
else
|
[Coding style change] Rename variables so that they start with a lowercase letter
This patch is mechanically generated by clang-llvm-rename tool that I wrote
using Clang Refactoring Engine just for creating this patch. You can see the
source code of the tool at https://reviews.llvm.org/D64123. There's no manual
post-processing; you can generate the same patch by re-running the tool against
lld's code base.
Here is the main discussion thread to change the LLVM coding style:
https://lists.llvm.org/pipermail/llvm-dev/2019-February/130083.html
In the discussion thread, I proposed we use lld as a testbed for variable
naming scheme change, and this patch does that.
I chose to rename variables so that they are in camelCase, just because that
is a minimal change to make variables to start with a lowercase letter.
Note to downstream patch maintainers: if you are maintaining a downstream lld
repo, just rebasing ahead of this commit would cause massive merge conflicts
because this patch essentially changes every line in the lld subdirectory. But
there's a remedy.
clang-llvm-rename tool is a batch tool, so you can rename variables in your
downstream repo with the tool. Given that, here is how to rebase your repo to
a commit after the mass renaming:
1. rebase to the commit just before the mass variable renaming,
2. apply the tool to your downstream repo to mass-rename variables locally, and
3. rebase again to the head.
Most changes made by the tool should be identical for a downstream repo and
for the head, so at the step 3, almost all changes should be merged and
disappear. I'd expect that there would be some lines that you need to merge by
hand, but that shouldn't be too many.
Differential Revision: https://reviews.llvm.org/D64121
llvm-svn: 365595
2019-07-10 13:00:37 +08:00
|
|
|
warn(msg);
|
2018-01-31 17:22:44 +08:00
|
|
|
}
|
2016-02-28 08:25:54 +08:00
|
|
|
} // namespace elf
|
2015-07-25 05:03:07 +08:00
|
|
|
} // namespace lld
|
|
|
|
|
|
|
|
#endif
|