Perform symbol binding for .symver versioned symbols
Summary:
In a .symver assembler directive like:
.symver name, name2@@nodename
"name2@@nodename" should get the same symbol binding as "name".
While the ELF object writer is updating the symbol binding for .symver
aliases before emitting the object file, not doing so when the module
inline assembly is handled by the RecordStreamer is causing the wrong
behavior in *LTO mode.
E.g. when "name" is global, "name2@@nodename" must also be marked as
global. Otherwise, the symbol is skipped when iterating over the LTO
InputFile symbols (InputFile::Symbol::shouldSkip). So, for example,
when performing any *LTO via the gold-plugin, the versioned symbol
definition is not recorded by the plugin and passed back to the
linker. If the object was in an archive, and there were no other symbols
needed from that object, the object would not be included in the final
link and references to the versioned symbol are undefined.
The llvm-lto2 tests added will give an error about an unused symbol
resolution without the fix.
Reviewers: rafael, pcc
Reviewed By: pcc
Subscribers: mehdi_amini, llvm-commits
Differential Revision: https://reviews.llvm.org/D30485
llvm-svn: 297332
2017-03-09 01:19:49 +01:00
|
|
|
; Test to ensure symbol binding works correctly for symver directives,
|
|
|
|
|
; when the aliased symbols are defined in inline assembly, including
|
|
|
|
|
; cases when the symbol attributes are provided after the .symver
|
|
|
|
|
; directive.
|
|
|
|
|
|
|
|
|
|
; RUN: llvm-as < %s >%t1
|
|
|
|
|
; RUN: llvm-lto -o %t2 %t1
|
|
|
|
|
; RUN: llvm-nm %t2 | FileCheck %s
|
2017-04-11 20:12:00 +02:00
|
|
|
; RUN: llvm-lto2 run -r %t1,_start,plx -r %t1,_start3,plx -r %t1,foo@@SOME_VERSION -r %t1,foo@SOME_VERSION3 -o %t3 %t1 -save-temps
|
Perform symbol binding for .symver versioned symbols
Summary:
In a .symver assembler directive like:
.symver name, name2@@nodename
"name2@@nodename" should get the same symbol binding as "name".
While the ELF object writer is updating the symbol binding for .symver
aliases before emitting the object file, not doing so when the module
inline assembly is handled by the RecordStreamer is causing the wrong
behavior in *LTO mode.
E.g. when "name" is global, "name2@@nodename" must also be marked as
global. Otherwise, the symbol is skipped when iterating over the LTO
InputFile symbols (InputFile::Symbol::shouldSkip). So, for example,
when performing any *LTO via the gold-plugin, the versioned symbol
definition is not recorded by the plugin and passed back to the
linker. If the object was in an archive, and there were no other symbols
needed from that object, the object would not be included in the final
link and references to the versioned symbol are undefined.
The llvm-lto2 tests added will give an error about an unused symbol
resolution without the fix.
Reviewers: rafael, pcc
Reviewed By: pcc
Subscribers: mehdi_amini, llvm-commits
Differential Revision: https://reviews.llvm.org/D30485
llvm-svn: 297332
2017-03-09 01:19:49 +01:00
|
|
|
; RUN: llvm-nm %t3.0 | FileCheck %s
|
|
|
|
|
|
|
|
|
|
target datalayout = "e-m:e-i64:64-f80:128-n8:16:32:64-S128"
|
|
|
|
|
target triple = "x86_64-unknown-linux-gnu"
|
|
|
|
|
|
|
|
|
|
module asm ".global _start"
|
|
|
|
|
module asm "_start:"
|
|
|
|
|
module asm "_start2:"
|
|
|
|
|
module asm "_start3:"
|
|
|
|
|
module asm ".symver _start, foo@@SOME_VERSION"
|
|
|
|
|
module asm ".symver _start2, foo@SOME_VERSION2"
|
|
|
|
|
module asm ".symver _start3, foo@SOME_VERSION3"
|
|
|
|
|
module asm ".local _start2"
|
|
|
|
|
module asm ".weak _start3"
|
|
|
|
|
|
|
|
|
|
; CHECK-DAG: T _start
|
|
|
|
|
; CHECK-DAG: t _start2
|
|
|
|
|
; CHECK-DAG: W _start3
|
|
|
|
|
; CHECK-DAG: T foo@@SOME_VERSION
|
|
|
|
|
; CHECK-DAG: t foo@SOME_VERSION2
|
|
|
|
|
; CHECK-DAG: W foo@SOME_VERSION3
|
