summaryrefslogtreecommitdiff
path: root/core/fpdfapi/font/cfx_cttgsubtable.cpp
diff options
context:
space:
mode:
authorVlad Tsyrklevich <vtsyrklevich@chromium.org>2017-11-29 14:32:19 +0000
committerChromium commit bot <commit-bot@chromium.org>2017-11-29 14:32:19 +0000
commit7829b7048d5cf13a4f1a806fed57f2440d1b5dec (patch)
treeeab782e5653e5513eb554d5f4910fcf52dab39df /core/fpdfapi/font/cfx_cttgsubtable.cpp
parent1ff9b7ffa653de1d25c5e013d731054815b13e86 (diff)
downloadpdfium-7829b7048d5cf13a4f1a806fed57f2440d1b5dec.tar.xz
[CFI] Enable type generalization for LCMS
Control Flow Integrity [1] indirect call checking verifies that function pointers only call valid functions with a matching type signature. This condition can be too strict, a common form of 'abstraction' relies on function pointers being cast to generalize argument pointer types to void*. In LCMS these failures occur because of casts of function pointers called as both _cmsInterpFn16 (cmsInterpFunction.Lerp16) and _cmsOPTeval16Fn (as an argument to _cmsPipelineSetOptimizationParameters) types making it difficult to refactor out easily. Instead, enabling the type generalization build config weakens the type checking performed for CFI-icall to accomodate this common type of casts. [1] https://www.chromium.org/developers/testing/control-flow-integrity Bug: 785442 Change-Id: Ib42fb1b4e152d5042b170698c2707ebb9e0cc1ee Reviewed-on: https://pdfium-review.googlesource.com/19250 Commit-Queue: dsinclair <dsinclair@chromium.org> Reviewed-by: dsinclair <dsinclair@chromium.org>
Diffstat (limited to 'core/fpdfapi/font/cfx_cttgsubtable.cpp')
0 files changed, 0 insertions, 0 deletions