diff options
| author | David Majnemer <david.majnemer@gmail.com> | 2015-12-21 22:09:27 +0000 |
|---|---|---|
| committer | David Majnemer <david.majnemer@gmail.com> | 2015-12-21 22:09:27 +0000 |
| commit | 03e2cc300747a4cfbe1cd05cc39ca247bddcb3f4 (patch) | |
| tree | cd4208481e26ccb00f16ffab3e61a19b03d317b9 /lldb/packages/Python/lldbsuite/test/python_api/thread/main2.cpp | |
| parent | a23e5f7516cabf2fc42148687cebf454ba3f5388 (diff) | |
| download | bcm5719-llvm-03e2cc300747a4cfbe1cd05cc39ca247bddcb3f4.tar.gz bcm5719-llvm-03e2cc300747a4cfbe1cd05cc39ca247bddcb3f4.zip | |
[MC, COFF] Support link /incremental conditionally
Today, we always take into account the possibility that object files
produced by MC may be consumed by an incremental linker. This results
in us initialing fields which vary with time (TimeDateStamp) which harms
hermetic builds (e.g. verifying a self-host went well) and produces
sub-optimal code because we cannot assume anything about the relative
position of functions within a section (call sites can get redirected
through incremental linker thunks).
Let's provide an MCTargetOption which controls this behavior so that we
can disable this functionality if we know a-priori that the build will
not rely on /incremental.
llvm-svn: 256203
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/thread/main2.cpp')
0 files changed, 0 insertions, 0 deletions
