From owner-freebsd-toolchain@freebsd.org Tue Mar 2 22:55:51 2021 Return-Path: Delivered-To: freebsd-toolchain@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 E0BF155449D for ; Tue, 2 Mar 2021 22:55:51 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4DqstH4Xgvz3lKf for ; Tue, 2 Mar 2021 22:55:51 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mailman.nyi.freebsd.org (Postfix) id 9BD5F55458F; Tue, 2 Mar 2021 22:55:51 +0000 (UTC) Delivered-To: toolchain@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 9B9C5554171 for ; Tue, 2 Mar 2021 22:55:51 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-il1-f181.google.com (mail-il1-f181.google.com [209.85.166.181]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DqstH3zH9z3lNL for ; Tue, 2 Mar 2021 22:55:51 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-il1-f181.google.com with SMTP id f10so19062312ilq.5 for ; Tue, 02 Mar 2021 14:55:51 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=8B22DV++SGR+rRziqWiP7+jQMUcIBs6e1YiuAgOia0g=; b=VUZCgGS3IGEOPnr2366ZudW/iLvJ5SVapI7PLRNbcL9k3F6qKX02r8zT6tziueFiZ0 CENPQ+D/x+AJtv+swOj4ma5SaB1uUywTNgcLPBbGOOZMVT/1tx4CtzbwTKOS8hdEkGRM 4mKsyeumqX7X4jmHHn4ygz0G7/mlCEYQcRjUeMl9Sj/HWaBID12P9s8BMvHJfgrdj6ba 9s+AjM/qZKepubq5Axtp9SCEpYtRUD6ZyXJMhTi78LLzaFvJPYhfqBPTJveIyR0nIWSS CdwfDX5I1S9Z8E/Qe4bt6ypgEikzNX/Q+E1qZNHpj0SBdIW008nk+50D0rdFNiDadQ4y LNkw== X-Gm-Message-State: AOAM531yQy2PRuExsipPhHS9sT/x2FL5QYz+kGXyKyHAktXSCCTvA8Vm vKlL4d/FWZE3Dj0KscTj/PJWINsTNP8Fy4bZlQo8z7OxRvQ= X-Google-Smtp-Source: ABdhPJz0HJfLeBhZVBnr3/TyTgkPgIcyJI+VFds8tujComAa6Q54M++f/Aa7wJIbvuBPYOFAEIRMHXlYl2m8QBGBIO0= X-Received: by 2002:a92:c690:: with SMTP id o16mr20021071ilg.256.1614725750279; Tue, 02 Mar 2021 14:55:50 -0800 (PST) MIME-Version: 1.0 References: <4D81BCDE-ECBC-49D8-BF17-38E334141FE0@FreeBSD.org> <89794bb8-5e97-36a7-0b6a-fa2eaf76a72a@wanadoo.fr> In-Reply-To: <89794bb8-5e97-36a7-0b6a-fa2eaf76a72a@wanadoo.fr> From: Ed Maste Date: Tue, 2 Mar 2021 17:55:37 -0500 Message-ID: Subject: Re: clang options for load segments To: Paul Floyd Cc: "toolchain@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4DqstH3zH9z3lNL X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Mar 2021 22:55:51 -0000 On Tue, 2 Mar 2021 at 14:37, Paul Floyd wrote: > > I'll work on fixing it in Valgrind, but that is likely to be fair amount > of work. I guess that recent Clang+lld will produce the same PT_LOAD on Linux too, so it seems like this is definitely something Valgrind will need to handle. > No need to hold your breath. Concerning the FreeBSD port I've been > working on Valgrind on FreeBSD for about a year or so and now it's not > too far from working as well on FreeBSD as it does on Linux*. > > Either install the devel/valgrind-devel package (note: not > devel/valgrind) or even better build and install from my github repo > https://github.com/paulfloyd/freebsd_valgrind. I have a commit bit for > upstream Valgrind and am working on integrating FreeBSD support in the > 'official' Valgrind. This probably won't be in the next release, 3.17, > due soon, but I hope that it gets into the next one (3.17.1 or 3.18). > And I'm always on the lookout for any user feedback :-) . Thank you so much for this, I will be very happy to finally see FreeBSD support upstream. IMO we should look at removing devel/valgrind and replacing it with valgrind-devel, given the amount of not-upstream work that exists in both of them.