Prior to this change the clang interface stubs format resembled
something ending with a symbol list like this:
Symbols:
a: { Type: Func }
This was problematic because we didn't actually want a map format and
also because we didn't like that an empty symbol list required
"Symbols: {}". That is to say without the empty {} llvm-ifs would crash
on an empty list.
With this new format it is much more clear which field is the symbol
name, and instead the [] that is used to express an empty symbol vector
is optional, ie:
Symbols:
- { Name: a, Type: Func }
or
Symbols: []
or
Symbols:
This further diverges the format from existing llvm-elftapi. This is a
good thing because although the format originally came from the same
place, they are not the same in any way.
Differential Revision: https://reviews.llvm.org/D76979
26 lines
878 B
Plaintext
26 lines
878 B
Plaintext
# RUN: llvm-ifs -action write-ifs -o - %s | FileCheck --check-prefixes=CHECK-DEFAULT %s
|
|
# RUN: llvm-ifs -action write-ifs -o - %s %S/weak.ifs | FileCheck --check-prefixes=CHECK-MERGE %s
|
|
|
|
# CHECK-DEFAULT: --- !experimental-ifs-v2
|
|
# CHECK-DEFAULT-NEXT: IfsVersion: 2.0
|
|
# CHECK-DEFAULT-NEXT: Triple: ''
|
|
# CHECK-DEFAULT-NEXT: ObjectFileFormat: ELF
|
|
# CHECK-DEFAULT-NEXT: Symbols: []
|
|
# CHECK-DEFAULT-NEXT: ...
|
|
|
|
# CHECK-MERGE: --- !experimental-ifs-v2
|
|
# CHECK-MERGE-NEXT: IfsVersion: 2.0
|
|
# CHECK-MERGE-NEXT: Triple: x86_64-unknown-linux-gnu
|
|
# CHECK-MERGE-NEXT: ObjectFileFormat: ELF
|
|
# CHECK-MERGE-NEXT: Symbols:
|
|
# CHECK-MERGE-DAG: - { Name: _Z8weakFuncv, Type: Func, Weak: true }
|
|
# CHECK-MERGE-DAG: - { Name: _Z10strongFuncv, Type: Func }
|
|
# CHECK-MERGE: ...
|
|
|
|
--- !experimental-ifs-v2
|
|
IfsVersion: 2.0
|
|
Triple: ''
|
|
ObjectFileFormat: ELF
|
|
Symbols: []
|
|
...
|