aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Bitcode/Writer/BitcodeWriter.cpp
diff options
context:
space:
mode:
authorStefan Gränitz <stefan.graenitz@gmail.com>2021-03-22 11:18:49 +0100
committerStefan Gränitz <stefan.graenitz@gmail.com>2021-03-22 11:20:23 +0100
commit4a8161fe40cce8503229d2835a38a38a30477b41 (patch)
treef878982995a9267bf46fef97494df6b84e2b8b08 /llvm/lib/Bitcode/Writer/BitcodeWriter.cpp
parent20d93267e18463292d54791f3c19211a85b27227 (diff)
downloadllvm-4a8161fe40cce8503229d2835a38a38a30477b41.zip
llvm-4a8161fe40cce8503229d2835a38a38a30477b41.tar.gz
llvm-4a8161fe40cce8503229d2835a38a38a30477b41.tar.bz2
[llvm-jitlink] Fix use of getaddrinfo(3) when connecting remote executor via TCP socket
Since llvm-jitlink moved from gethostbyname to getaddrinfo in D95477, it seems to no longer connect to llvm-jitlink-executor via TCP. I can reproduce this behavior on both, Debian 10 and macOS 10.15.7: ``` > llvm-jitlink-executor listen=localhost:10819 -- > llvm-jitlink --oop-executor-connect=localhost:10819 /path/to/obj.o Failed to resolve localhost:10819 ``` Reviewed By: rzurob Differential Revision: https://reviews.llvm.org/D98579
Diffstat (limited to 'llvm/lib/Bitcode/Writer/BitcodeWriter.cpp')
0 files changed, 0 insertions, 0 deletions