Skip to content
  1. Jul 08, 2016
  3. Jul 07, 2016
    • Rafael Espindola's avatar
      Fix formating. NFC. · 64c32d6f
      Rafael Espindola authored 
      llvm-svn: 274757
      64c32d6f
    • Rafael Espindola's avatar
      Use "using namespace llvm" like the rest of ELF lld. · d10f0b1e
      Rafael Espindola authored 
      llvm-svn: 274755
      d10f0b1e
    • George Rimar's avatar
      [ELF] - Fixed incorrect logic of version assignments when mixing wildcards with values matching. · f73a2581
      George Rimar authored 
      Previously we had incorrect logic here. Imagine we would have the next script:

LIBSAMPLE_1.0
{
  global:
   a_2;
 local:
  *;
};

LIBSAMPLE_2.0
{
  global:
   a*;
};
According to previous logic it would assign version 1 to a_2 and then
would try to reassign it to version 2 because of applying wildcard a*.
And show a warning about that.

Generally Ian Lance Tailor wrote about next rules that should be applied:
(http://www.airs.com/blog/archives/300)

Here are the current rules for gold:

"If there is an exact match for the mangled name, we use it. If there is more than one exact match, we give a warning, and we use the first tag in the script which matches. If a symbol has an exact match as both global and local for the same version tag, we give an error.
Otherwise, we look for an extern C++ or an extern Java exact match. If we find an exact match, we use it. If there is more than one exact match, we give a warning, and we use the first tag in the script which matches. If a symbol has an exact match as both global and local for the same version tag, we give an error.
Otherwise, we look through the wildcard patterns, ignoring “*” patterns. We look through the version tags in reverse order. For each version tag, we look through the global patterns and then the local patterns. We use the first match we find (i.e., the last matching version tag in the file).
Otherwise, we use the “*” pattern if there is one. We give a warning if there are multiple “*” patterns."

Patch makes wildcard matching to be in revered order and to follow after the regular naming matching.

Differential revision: http://reviews.llvm.org/D21894

llvm-svn: 274739
      f73a2581
    • Rui Ueyama's avatar
      Fix endianness issue. · 1d12ac1d
      Rui Ueyama authored 
      Previously, ch_size was read in host byte order, so if a host and
a target are different in byte order, we would produce a corrupted
output.

llvm-svn: 274729
      1d12ac1d
    • Rui Ueyama's avatar
      Fix formatting. · 523744dd
      Rui Ueyama authored 
      llvm-svn: 274724
      523744dd
    • Rui Ueyama's avatar
      Do not call warning() from ELFOptTable::parse(). · 0f282a59
      Rui Ueyama authored 
      warning() depends on Config->FatalWarnings, so we don't want to call
that function before we initialize that member.

llvm-svn: 274723
      0f282a59
    • Rui Ueyama's avatar
      Fix indentation. · a027d339
      Rui Ueyama authored 
      llvm-svn: 274719
      a027d339
  5. Jul 06, 2016
  7. Jul 04, 2016
  9. Jul 02, 2016
  11. Jul 01, 2016
  13. Jun 30, 2016
    • Rui Ueyama's avatar
      Do not allow "--" with single-letter options. · 1df56894
      Rui Ueyama authored 
      In general, we accept both -foo and --foo as command line options,
but if an option is a single letter option, we don't want to allow
double dashes because GNU linkers don't accept such combination.

llvm-svn: 274219
      1df56894
  15. Jun 29, 2016