[ORC] Use uint8_t rather than char for RPC wrapper-function calls.
authorLang Hames <lhames@gmail.com>
Fri, 18 Jun 2021 11:42:43 +0000 (21:42 +1000)
committerLang Hames <lhames@gmail.com>
Fri, 18 Jun 2021 11:56:09 +0000 (21:56 +1000)
commitcbfb12469ba312c8ff513397b29bef470f151caa
tree400fc02f573f4202fb587b6352aa7b6b5bfce973
parent7ddd15cd5dea76a19a9c5315e2a9903d74a49be8
[ORC] Use uint8_t rather than char for RPC wrapper-function calls.

This partially reverts 838490de7ed, which broke some Solaris bots. Apparently
Solaris defines int8_t as char rather than signed char, which made the
SerializationTypeName<char> specialization a redefinition.

This partial revert isolates use of uint8_t buffers to ORC-RPC handling of
wrapper functions only. The TargetProcessControl::runWrapper method will
continue to use char buffers.
llvm/include/llvm/ExecutionEngine/Orc/OrcRPCTargetProcessControl.h
llvm/include/llvm/ExecutionEngine/Orc/Shared/Serialization.h
llvm/include/llvm/ExecutionEngine/Orc/TargetProcess/OrcRPCTPCServer.h