aboutsummaryrefslogtreecommitdiff
path: root/llvm/docs/tutorial/MyFirstLanguageFrontend
diff options
context:
space:
mode:
authorLeonard Chan <leonardchan@google.com>2024-01-12 19:09:35 -0800
committerLeonard Chan <leonardchan@google.com>2024-01-12 19:09:35 -0800
commita08402f95bc785c124702b075904cc110128661f (patch)
treeced88fc3394878145420f36fad36801f67104932 /llvm/docs/tutorial/MyFirstLanguageFrontend
parent1df4fb98813a33d14f2112a1bb906039d112fa3f (diff)
downloadllvm-a08402f95bc785c124702b075904cc110128661f.zip
llvm-a08402f95bc785c124702b075904cc110128661f.tar.gz
llvm-a08402f95bc785c124702b075904cc110128661f.tar.bz2
[sanitizer_common][fuchsia] Get correct vmar info
Forward fix for https://github.com/llvm/llvm-project/pull/75256 The process for MmapAlignedOrDieOnFatalError involves trimming the start and end of a mapping to ensure it's aligned correctly. This invloves calling zx_vmar_map again but overwriting a part of the original vmar which involves a call to zx_object_get_info(ZX_INFO_VMAR). After https://github.com/llvm/llvm-project/pull/75256, we unconditionally called this on gSanitizerHeapVmar but this can lead to a ZX_ERR_INVALID_ARGS if the prior mapping was on the root vmar. This can be fixed by also returning the vmar we did the last mapping to and using that for followup operations that specifically involve the same vmar. This way we don't have to try each syscall for both vmars.
Diffstat (limited to 'llvm/docs/tutorial/MyFirstLanguageFrontend')
0 files changed, 0 insertions, 0 deletions