From owner-freebsd-current@freebsd.org Tue Jul 28 09:03:23 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D8BDC3A22C2 for ; Tue, 28 Jul 2020 09:03:23 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4BG9gv3NRTz45Yt; Tue, 28 Jul 2020 09:03:23 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.16.1/8.16.1) with ESMTPS id 06S93EW7058716 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 28 Jul 2020 12:03:17 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua 06S93EW7058716 Received: (from kostik@localhost) by tom.home (8.16.1/8.16.1/Submit) id 06S93DcF058715; Tue, 28 Jul 2020 12:03:13 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 28 Jul 2020 12:03:13 +0300 From: Konstantin Belousov To: Kyle Evans Cc: FreeBSD Current Subject: Re: [CFT] Updated devel/valgrind-devel port Message-ID: <20200728090313.GG2551@kib.kiev.ua> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on tom.home X-Rspamd-Queue-Id: 4BG9gv3NRTz45Yt X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jul 2020 09:03:23 -0000 On Mon, Jul 27, 2020 at 09:49:57PM -0500, Kyle Evans wrote: > On Fri, Jul 24, 2020 at 3:24 PM Kyle Evans wrote: > > > > Hello! > > > > Just a little bit ago, I committed an update[0] to the valgrind-devel > > port that updates it to Paul Floyd's branch, where he has rebased us > > forward to 3.17.0 and largely fixed valgrind operation on both 12.x > > and -CURRENT. > > > > He's put in significant effort to get the test suite to pass on > > FreeBSD, the status of which is summarized here: > > - https://github.com/paulfloyd/freebsd_valgrind/wiki/Regtest-status > > > > Some outstanding issues: > > - https://github.com/paulfloyd/freebsd_valgrind/issues > > > > Please go forth and test it! > > > > A quick follow-up to note that the new valgrind-devel > (3.17.0.g20200723,1) is reportedly now available on a pkg mirror near > you for all three FreeBSD branches, for your convenience. I have a low prio suggestion for the port. It seems that when valgrind-devel is built on 11, it does not know about newer syscalls. So when this instance of valgrind is run on 12 or HEAD, it is uncapable of handling new libc. Is it possible (without too much efforts) to make valgrind forward-compatible, hopefully just by enabling HEAD syscalls on all builds, instead of limiting it to the target equal to the build system ?