Differential Revision: https://reviews.llvm.org/D49147

git-svn-id: https://llvm.org/svn/llvm-project/lld/trunk@338767 91177308-0d34-0410-b5e6-96231b3b80d8

[LLD] Update split stack support to handle more generic prologues. Improve error handling. Add test file for better code-coverage. Update tests to be more complete.

Submitting patch on behalf of saugustine.

Differential Revision: https://reviews.llvm.org/D49926

git-svn-id: https://llvm.org/svn/llvm-project/lld/trunk@338750 91177308-0d34-0410-b5e6-96231b3b80d8

In according to the comment, undefined symbol should never reach there.
So, should be able to remove the check. I am assuming this is NFC. 

git-svn-id: https://llvm.org/svn/llvm-project/lld/trunk@338723 91177308-0d34-0410-b5e6-96231b3b80d8

BB is unhappy :`-(
http://lab.llvm.org:8011/builders/lld-perf-testsuite/builds/5632

git-svn-id: https://llvm.org/svn/llvm-project/lld/trunk@338722 91177308-0d34-0410-b5e6-96231b3b80d8

There is no point to explicitly proccess the expressions this patch removes.
We already have a llvm_unreachable for the default case.

git-svn-id: https://llvm.org/svn/llvm-project/lld/trunk@338718 91177308-0d34-0410-b5e6-96231b3b80d8

It does not seem that this code is alive.
I seems was needed previously but we fixed it.

If it is still needed, it needs new tests,
but for now I do not know how to trigger it,
and so I removed it.


git-svn-id: https://llvm.org/svn/llvm-project/lld/trunk@338713 91177308-0d34-0410-b5e6-96231b3b80d8

Code was never executed with our test cases,
though it is valid and I think we can always run it.
This improves code coverage.

git-svn-id: https://llvm.org/svn/llvm-project/lld/trunk@338708 91177308-0d34-0410-b5e6-96231b3b80d8

Some lit tests that call llvm-ar use the 'r' flag. If the target archive
already exists and is in a corrupt state, this can cause the test to fail. We
have added 'rm -f' calls before the llvm-ar calls to increase the
robustness of the tests.

Differential revision: https://reviews.llvm.org/D49184

git-svn-id: https://llvm.org/svn/llvm-project/lld/trunk@338705 91177308-0d34-0410-b5e6-96231b3b80d8

isHeaderSection can be useful I believe,
but probably not right now and not
for this case.

git-svn-id: https://llvm.org/svn/llvm-project/lld/trunk@338699 91177308-0d34-0410-b5e6-96231b3b80d8

Patch by Konstantin Schwarz!

If more than a single output section is added to a PT_LOAD header,
only the first section should set the LMAOffset of the segment.
Otherwise, we get a load-address overlap error

Differential revision: https://reviews.llvm.org/D50133

git-svn-id: https://llvm.org/svn/llvm-project/lld/trunk@338697 91177308-0d34-0410-b5e6-96231b3b80d8

Patch by Konstantin Schwarz!

If both the MemRegion and LMARegion are set for an output section in
a linker script, we should only increase the LMARegion if it is
different from the MemRegion. Otherwise, we reserve the memory twice.

Differential revision: https://reviews.llvm.org/D50065

git-svn-id: https://llvm.org/svn/llvm-project/lld/trunk@338684 91177308-0d34-0410-b5e6-96231b3b80d8

Patch by Konstantin Schwarz!

The condition to create a new phdr must also check the usage of "AT>" 
linker script command, and create a new PT_LOAD header if a new LMARegion is used.

This fixes PR38307

Differential revision: https://reviews.llvm.org/D50052

git-svn-id: https://llvm.org/svn/llvm-project/lld/trunk@338679 91177308-0d34-0410-b5e6-96231b3b80d8

git-svn-id: https://llvm.org/svn/llvm-project/lld/trunk@338647 91177308-0d34-0410-b5e6-96231b3b80d8

git-svn-id: https://llvm.org/svn/llvm-project/lld/trunk@338642 91177308-0d34-0410-b5e6-96231b3b80d8

This was useful for LTO bringup in lld-link while lld couldn't write PDBs. Now
that it can, this should no longer be needed. Hopefully the flag is obscure
enough and recent enough, that nobody uses it – but if somebody should use it,
they should be able to just stop passing it and things should continue to work.

https://reviews.llvm.org/D50139


git-svn-id: https://llvm.org/svn/llvm-project/lld/trunk@338615 91177308-0d34-0410-b5e6-96231b3b80d8

This reverts commit r338596 because it contained a functional change.
The patch accidentally replaced StringRef::startswith with the exact match.

git-svn-id: https://llvm.org/svn/llvm-project/lld/trunk@338600 91177308-0d34-0410-b5e6-96231b3b80d8

git-svn-id: https://llvm.org/svn/llvm-project/lld/trunk@338596 91177308-0d34-0410-b5e6-96231b3b80d8

git-svn-id: https://llvm.org/svn/llvm-project/lld/trunk@338558 91177308-0d34-0410-b5e6-96231b3b80d8

Removal of extra line

git-svn-id: https://llvm.org/svn/llvm-project/lld/trunk@338533 91177308-0d34-0410-b5e6-96231b3b80d8

git-svn-id: https://llvm.org/svn/llvm-project/lld/trunk@338498 91177308-0d34-0410-b5e6-96231b3b80d8

git-svn-id: https://llvm.org/svn/llvm-project/lld/trunk@338497 91177308-0d34-0410-b5e6-96231b3b80d8

Allow oformat to accept format starting with elf as acceptable format. isOutputFormatBinary returns false in such case.

Example: --oformat elf64-x86-64

Differential Revision: https://reviews.llvm.org/D50105



git-svn-id: https://llvm.org/svn/llvm-project/lld/trunk@338445 91177308-0d34-0410-b5e6-96231b3b80d8

Some test setups run tests in a read-only path, which means that opening the
default output path (a.out) for write will fail. This change adds appropriate -o
flags so the tests will not fail spuriously.

git-svn-id: https://llvm.org/svn/llvm-project/lld/trunk@338440 91177308-0d34-0410-b5e6-96231b3b80d8

If any of our inputs are bitcode files, the LTO code generator may create
references to certain library functions that might not be explicit in the
bitcode file's symbol table. If any of those library functions are defined
in a bitcode file in an archive member, we need to arrange to use LTO to
compile those archive members by adding them to the link beforehand.

Differential Revision: https://reviews.llvm.org/D50017

git-svn-id: https://llvm.org/svn/llvm-project/lld/trunk@338434 91177308-0d34-0410-b5e6-96231b3b80d8

git-svn-id: https://llvm.org/svn/llvm-project/lld/trunk@338409 91177308-0d34-0410-b5e6-96231b3b80d8

This patch does the same thing as r338153 for COFF.
Note that this patch affects only the order of log messages.
The output file is already deterministic.

Differential Revision: https://reviews.llvm.org/D50023

git-svn-id: https://llvm.org/svn/llvm-project/lld/trunk@338406 91177308-0d34-0410-b5e6-96231b3b80d8

[LLD][ELF] - ICF: Check we do not fold sections which relocations reffering to absolute symbols with a different values.

This adds a test for the following uncovered piece of code:
https://github.com/llvm-mirror/lld/blob/master/ELF/ICF.cpp#L263

Without that lines we would crash.

git-svn-id: https://llvm.org/svn/llvm-project/lld/trunk@338379 91177308-0d34-0410-b5e6-96231b3b80d8

The Tag_ABI_VFP_args build attribute controls the procedure call standard
used for floating point parameters on ARM. The values are:
0 - Base AAPCS (FP Parameters passed in Core (Integer) registers
1 - VFP AAPCS (FP Parameters passed in FP registers)
2 - Toolchain specific (Neither Base or VFP)
3 - Compatible with all (No use of floating point parameters)

If the Tag_ABI_VFP_args build attribute is missing it has an implicit value
of 0.
    
We use the attribute in two ways:
- Detect a clash in calling convention between Base, VFP and Toolchain.
we follow ld.bfd's lead and do not error if there is a clash between an
implicit Base AAPCS caused by a missing attribute. Many projects
including the hard-float (VFP AAPCS) version of glibc contain assembler
files that do not use floating point but do not have Tag_ABI_VFP_args.
- Set the EF_ARM_ABI_FLOAT_SOFT or EF_ARM_ABI_FLOAT_HARD ELF header flag
for Base or VFP AAPCS respectively. This flag is used by some ELF
loaders.
    
References:
- Addenda to, and Errata in, the ABI for the ARM Architecture for
Tag_ABI_VFP_args
- Elf for the ARM Architecture for ELF header flags
    
Fixes PR36009
    
Differential Revision: https://reviews.llvm.org/D49993


git-svn-id: https://llvm.org/svn/llvm-project/lld/trunk@338377 91177308-0d34-0410-b5e6-96231b3b80d8

Previously the following condition was not tested at all:
https://github.com/llvm-mirror/lld/blob/master/ELF/ICF.cpp#L300

Patch adds a test for `A->Flags != B->Flags` part.

git-svn-id: https://llvm.org/svn/llvm-project/lld/trunk@338375 91177308-0d34-0410-b5e6-96231b3b80d8

git-svn-id: https://llvm.org/svn/llvm-project/lld/trunk@338363 91177308-0d34-0410-b5e6-96231b3b80d8