llvm-project/llvm/test/tools/llvm-ifs/Inputs/strong-mismatch-size.ifs

# NOTE: Used by weak-mismatch.ifs
--- !ifs-v1
IfsVersion: 3.0
Target: x86_64-unknown-linux-gnu
Symbols:
  - { Name: foobar, Type: Object, Size: 2 }
...
[llvm] llvm-ifs: Support for handling empty IFS and merging weak+strong symbols. The following changes enable llvm-ifs to handle the following merge conflicts: * Weak + Strong symbol merging for the same symbol * empty vs non-empty triple field * empty vs non-empty object file format Differential Revision: https://reviews.llvm.org/D70834 2019-11-29 05:43:56 +08:00			`# NOTE: Used by weak-mismatch.ifs`
[ifs] Prepare llvm-ifs for elfabi/ifs merging. This diff changes llvm-ifs to use unified IFS file format and perform other renaming changes in preparation for the merging between elfabi/ifs. Differential Revision: https://reviews.llvm.org/D99810 2021-04-08 06:50:12 +08:00			`--- !ifs-v1`
			`IfsVersion: 3.0`
			`Target: x86_64-unknown-linux-gnu`
[llvm] llvm-ifs: Support for handling empty IFS and merging weak+strong symbols. The following changes enable llvm-ifs to handle the following merge conflicts: * Weak + Strong symbol merging for the same symbol * empty vs non-empty triple field * empty vs non-empty object file format Differential Revision: https://reviews.llvm.org/D70834 2019-11-29 05:43:56 +08:00			`Symbols:`
[llvm][clang][IFS] Enhancing the llvm-ifs yaml format for symbol lists. 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 2020-03-28 16:08:27 +08:00			`- { Name: foobar, Type: Object, Size: 2 }`
[llvm] llvm-ifs: Support for handling empty IFS and merging weak+strong symbols. The following changes enable llvm-ifs to handle the following merge conflicts: * Weak + Strong symbol merging for the same symbol * empty vs non-empty triple field * empty vs non-empty object file format Differential Revision: https://reviews.llvm.org/D70834 2019-11-29 05:43:56 +08:00			`...`