From: Vbook A1 <vbooka1maillist@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: CentOS 7 build warning, chacha20_avx512vl
Date: Mon, 26 Mar 2018 01:50:21 +0700 [thread overview]
Message-ID: <CAHsAZcANfzjCysbSvgXDKidwcW_my2k+f9TsDqBTwPWv2dhSZA@mail.gmail.com> (raw)
Hello,
this is the build log of the latest "stable" WireGuard on the latest CentOS 7:
> -bash-4.2# make
> CC [M] /dev/shm/WireGuard-0.0.20180304/src/main.o
> CC [M] /dev/shm/WireGuard-0.0.20180304/src/noise.o
> CC [M] /dev/shm/WireGuard-0.0.20180304/src/device.o
> CC [M] /dev/shm/WireGuard-0.0.20180304/src/peer.o
> CC [M] /dev/shm/WireGuard-0.0.20180304/src/timers.o
> CC [M] /dev/shm/WireGuard-0.0.20180304/src/queueing.o
> CC [M] /dev/shm/WireGuard-0.0.20180304/src/send.o
> CC [M] /dev/shm/WireGuard-0.0.20180304/src/receive.o
> CC [M] /dev/shm/WireGuard-0.0.20180304/src/socket.o
> CC [M] /dev/shm/WireGuard-0.0.20180304/src/hashtables.o
> CC [M] /dev/shm/WireGuard-0.0.20180304/src/allowedips.o
> CC [M] /dev/shm/WireGuard-0.0.20180304/src/ratelimiter.o
> CC [M] /dev/shm/WireGuard-0.0.20180304/src/cookie.o
> CC [M] /dev/shm/WireGuard-0.0.20180304/src/netlink.o
> CC [M] /dev/shm/WireGuard-0.0.20180304/src/crypto/curve25519.o
> CC [M] /dev/shm/WireGuard-0.0.20180304/src/crypto/chacha20poly1305.o
> CC [M] /dev/shm/WireGuard-0.0.20180304/src/crypto/blake2s.o
> AS [M] /dev/shm/WireGuard-0.0.20180304/src/crypto/chacha20-x86_64.o
> /dev/shm/WireGuard-0.0.20180304/src/crypto/chacha20-x86_64.o: warning: objtool: chacha20_avx512vl()+0x3f: can't find jump dest instruction at .text+0x2669
> AS [M] /dev/shm/WireGuard-0.0.20180304/src/crypto/poly1305-x86_64.o
> AS [M] /dev/shm/WireGuard-0.0.20180304/src/crypto/blake2s-x86_64.o
> AS [M] /dev/shm/WireGuard-0.0.20180304/src/crypto/curve25519-x86_64.o
> CC [M] /dev/shm/WireGuard-0.0.20180304/src/compat/siphash/siphash.o
> LD [M] /dev/shm/WireGuard-0.0.20180304/src/wireguard.o
> Building modules, stage 2.
> MODPOST 1 modules
> CC /dev/shm/WireGuard-0.0.20180304/src/wireguard.mod.o
> LD [M] /dev/shm/WireGuard-0.0.20180304/src/wireguard.ko
> CC /dev/shm/WireGuard-0.0.20180304/src/tools/wg.o
> CC /dev/shm/WireGuard-0.0.20180304/src/tools/config.o
> CC /dev/shm/WireGuard-0.0.20180304/src/tools/show.o
> CC /dev/shm/WireGuard-0.0.20180304/src/tools/terminal.o
> CC /dev/shm/WireGuard-0.0.20180304/src/tools/ipc.o
> CC /dev/shm/WireGuard-0.0.20180304/src/tools/mnlg.o
> CC /dev/shm/WireGuard-0.0.20180304/src/tools/encoding.o
> CC /dev/shm/WireGuard-0.0.20180304/src/tools/curve25519.o
> CC /dev/shm/WireGuard-0.0.20180304/src/tools/setconf.o
> CC /dev/shm/WireGuard-0.0.20180304/src/tools/genkey.o
> CC /dev/shm/WireGuard-0.0.20180304/src/tools/showconf.o
> CC /dev/shm/WireGuard-0.0.20180304/src/tools/pubkey.o
> CC /dev/shm/WireGuard-0.0.20180304/src/tools/set.o
> LD /dev/shm/WireGuard-0.0.20180304/src/tools/wg
git "unstable" version gives the same warning:
> AS [M] /dev/shm/WireGuard/src/crypto/chacha20-x86_64.o
> /dev/shm/WireGuard/src/crypto/chacha20-x86_64.o: warning: objtool: chacha20_avx512vl()+0x3f: can't find jump dest instruction at .text+0x2669
However Wireguard [seemingly] works well despite this warning, tested
with three CentOS 7 servers. Is it OK?
System info:
CentOS 7.4.1708 64bit
Kernel 3.10.0-693.21.1.el7.x86_64
gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-16)
Make 3.82
elfutils 0.168-8.el7
libmnl 1.0.3-7.el7
BTW many thanks for such a great software, I fell in love with
Wireguard for its simplicity after working for several years with
OpenVPN.
next reply other threads:[~2018-03-25 18:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-25 18:50 Vbook A1 [this message]
2018-03-25 21:17 ` Samuel Neves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHsAZcANfzjCysbSvgXDKidwcW_my2k+f9TsDqBTwPWv2dhSZA@mail.gmail.com \
--to=vbooka1maillist@gmail.com \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).