summaryrefslogtreecommitdiffstats
path: root/llvm/utils/lit/tests/shtest-shell.py
diff options
context:
space:
mode:
authorPavel Labath <labath@google.com>2019-10-25 21:44:46 +0000
committerPavel Labath <labath@google.com>2019-10-25 22:11:53 +0000
commit73a7a55c0ec976fecadd7a872d24d850f8cd793a (patch)
tree26449ff00265f540b6ac31cc4f83f18138e245da /llvm/utils/lit/tests/shtest-shell.py
parent4c0251da149c99f49550d6c938e6e7f45075194d (diff)
downloadbcm5719-llvm-73a7a55c0ec976fecadd7a872d24d850f8cd793a.tar.gz
bcm5719-llvm-73a7a55c0ec976fecadd7a872d24d850f8cd793a.zip
lldb/COFF: Create a separate "section" for the file header
In an attempt to ensure that every part of the module's memory image is accounted for, D56537 created a special "container section" spanning the entire image. While that seemed reasonable at the time (and it still mostly does), it did create a problem of what to put as the "file size" of the section, because the image is not continuous on disk, as we generally assume (which is why I put zero there). Additionally, this arrangement makes it unclear what kind of permissions should be assigned to that section (which is what my next patch does). To get around these, this patch partially reverts D56537, and goes back to top-level sections. Instead, what I do is create a new "section" for the object file header, which is also being loaded into memory, though its not considered to be a section in the strictest sense. This makes it possible to correctly assign file size section, and we can later assign permissions to it as well. Reviewers: amccarth, mstorsjo Subscribers: lldb-commits Differential Revision: https://reviews.llvm.org/D69100
Diffstat (limited to 'llvm/utils/lit/tests/shtest-shell.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud