diff options
author | George Rimar <grimar@accesssoftek.com> | 2019-07-10 14:36:48 +0000 |
---|---|---|
committer | George Rimar <grimar@accesssoftek.com> | 2019-07-10 14:36:48 +0000 |
commit | c44a23f8f450bdb8cec784ef0c4f0ca502b7524f (patch) | |
tree | 6bc41118316a133ac53e230f607b3385138c40db /llvm/lib/Transforms/Utils/SimplifyLibCalls.cpp | |
parent | d5214dfa7b5650745eaeb102857c9e90adb16137 (diff) | |
download | bcm5719-llvm-c44a23f8f450bdb8cec784ef0c4f0ca502b7524f.tar.gz bcm5719-llvm-c44a23f8f450bdb8cec784ef0c4f0ca502b7524f.zip |
[LLD][ELF] - Linkerscript: fix FILL() expressions handling.
D64130 introduced a bug described in the following message:
https://reviews.llvm.org/D64130#1571560
The problem can happen with the following script:
SECTIONS {
.out : {
...
FILL(0x10101010)
*(.aaa)
...
}
The current code tries to read (0x10101010) as an expression and
does not break when meets *, what results in a script parsing error.
In this patch, I verify that FILL command's expression always wrapped in ().
And at the same time =<fillexp> expression can be both wrapped or unwrapped.
I checked it matches to bfd/gold.
Differential revision: https://reviews.llvm.org/D64476
llvm-svn: 365635
Diffstat (limited to 'llvm/lib/Transforms/Utils/SimplifyLibCalls.cpp')
0 files changed, 0 insertions, 0 deletions