summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Support/Windows/Path.inc
diff options
context:
space:
mode:
authorChris Bieneman <chris.bieneman@me.com>2018-06-01 22:07:36 +0000
committerChris Bieneman <chris.bieneman@me.com>2018-06-01 22:07:36 +0000
commitc8a3c86c77362ba8da55ff7514d03205771179c2 (patch)
treed851125fafc120aeca0ec7ba79359e0ed0efd17d /llvm/lib/Support/Windows/Path.inc
parentd74d04a6c5241f9e19147801573d84ed46030ecf (diff)
downloadbcm5719-llvm-c8a3c86c77362ba8da55ff7514d03205771179c2.tar.gz
bcm5719-llvm-c8a3c86c77362ba8da55ff7514d03205771179c2.zip
[MachO] Fixing ub in MachO BinaryFormat
This isn't encountered anywhere inside LLVM, so I wrote a test case to expose the issue and verify that it is fixed. The basic problem is that the macho_load_command union contains all load comamnd structs. Load command structs in 32-bit macho files can be 32-bit aligned instead of 64-bit aligned. There are some strange circumstances in which this can be exposed in a 64-bit macho if the load commands are invalid or if a 32-bit aligned load command is used. In the past we've worked around this type of problem with changes like r264232. llvm-svn: 333797
Diffstat (limited to 'llvm/lib/Support/Windows/Path.inc')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud