mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-11-22 18:54:02 +01:00
ba26a57bf4
This fixes a bug with string merging with string symbols that contain NULLs, as is the case in the `merge-string.s` test. The bug only showed when we run with `--relocatable` and then try read the resulting object back in. In this case we would end up with string symbols that extend past the end of the segment in which they live. The problem comes from the fact that sections which are flagged as string mergable assume that all strings are NULL terminated. The merging algorithm will drop trailing chars that follow a NULL since they are essentially unreachable. However, the "size" attribute (in the symbol table) of such a truncated symbol is not updated resulting a symbol size that can overlap the end of the segment. I verified that this can happen in ELF too given the right conditions and the its harmless enough. In practice Strings that contain embedded null should not be part of a mergable section. Differential Revision: https://reviews.llvm.org/D102281
32 lines
813 B
YAML
32 lines
813 B
YAML
# RUN: yaml2obj %s | not llvm-objdump -s - 2>&1 | FileCheck %s
|
|
|
|
# Check that data symbols must have and offset that is within the
|
|
# bounds of the containing segment
|
|
|
|
# CHECK: invalid data symbol offset: `foo` (offset: 42 segment size: 5)
|
|
|
|
--- !WASM
|
|
FileHeader:
|
|
Version: 0x00000001
|
|
Sections:
|
|
- Type: DATA
|
|
Segments:
|
|
- SectionOffset: 0
|
|
InitFlags: 0
|
|
Offset:
|
|
Opcode: I32_CONST
|
|
Value: 0
|
|
Content: '6401020304'
|
|
- Type: CUSTOM
|
|
Name: linking
|
|
Version: 2
|
|
SymbolTable:
|
|
- Index: 0
|
|
Kind: DATA
|
|
Name: foo
|
|
Flags: [ ]
|
|
Segment: 0
|
|
Offset: 42
|
|
Size: 1
|
|
...
|