From owner-freebsd-gecko@freebsd.org Mon Apr 17 19:54:47 2017 Return-Path: Delivered-To: freebsd-gecko@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 95744D4226B; Mon, 17 Apr 2017 19:54:47 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F008180; Mon, 17 Apr 2017 19:54:47 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: by mail-io0-x22b.google.com with SMTP id a103so166379220ioj.1; Mon, 17 Apr 2017 12:54:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=R8wrKzVC9t1fsole2/Jq7U9sBicItED9cmwQaCa+tB4=; b=F4a8lH2z5L0HgoMyGVhKEEIq7i0sVav/DenNIVA5VnjoxS1NqV8cK/RRRo7QB4cNa/ rH6GSMkYZlIraQleP+XHi7AYtjtIQh1hv9GdVzB+mMBMCTQtqK3cW1KilBOSxWlkGruU HHFDf7DznRlWGyrDLsY+vlsQCULGBBJw1bugFSbSoRMIVJRN0AdYVmXGMHPO4JMj3Ln8 f8dGSdAbjlM9WUorme/WPEq1tSyRUh5AlWJxmUNbOQq3uIjlszn5dqNvcd7WApXgxOJS 2C1HyAx8Sh1VoFVDCJx3KLsl4AsJaWfclK5H2tDXjIKuZwW+bruRoKWBcQuF1qQ/iHD8 5gFg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=R8wrKzVC9t1fsole2/Jq7U9sBicItED9cmwQaCa+tB4=; b=JQAmdrsDJBvlIDcTrro/4TFaUBpJoFx2XC10iOqzdjuzFTyvdu2Dmmly7wzKPJpzIO a3jglFDhurEyjvEnlDbeZR9FhoGgnSFkqStqE/8rostqCjItBOLEMl8fmtUdemxxSghi FNKbqIgs+AjHGwnR9bTNL0hu/X4LYONX1zGW9WRIiQ2ISvm9gGt8bdJF8DOR9f3R8g99 UZGty6VYhkr+yND0oIvlTPUc/dZXhaQVA+zp+q4aHLajNGpxx+eXrT7tbU4d5xTZ2V+k LMQWq3w3rXJVphhW224KfeI2taMBvS/XpAGcYlJZPMrm1MLxE5pscRH5UTWXE6fjfA0j 0BGw== X-Gm-Message-State: AN3rC/7117k1GYyI5vsgYp+Q8oOk3oogW4LrKhUFF/j6p+nzQiOYjXer /t4+DywSf5dLmFyHWJNEEYHgCpAGbg== X-Received: by 10.36.53.7 with SMTP id k7mr10622783ita.65.1492458886763; Mon, 17 Apr 2017 12:54:46 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.132.202 with HTTP; Mon, 17 Apr 2017 12:54:46 -0700 (PDT) In-Reply-To: <76897620-E958-4AE2-9B6C-062C59526614@neville-neil.com> References: <3CEE1970-719B-42D1-A95A-FEAD3F375A30@neville-neil.com> <20170212191826.5599A45EA@freefall.freebsd.org> <77416dea-1e9d-4911-b5d0-2ebac227af7e@Spark> <76897620-E958-4AE2-9B6C-062C59526614@neville-neil.com> From: Ryan Stone Date: Mon, 17 Apr 2017 15:54:46 -0400 Message-ID: Subject: Re: DTrace issues? To: George Neville-Neil Cc: Jan Beich , freebsd-gecko@freebsd.org, "freebsd-dtrace@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-gecko@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Gecko Rendering Engine issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Apr 2017 19:54:47 -0000 On Sat, Apr 15, 2017 at 10:50 AM, George Neville-Neil wrote: > > Can you explain this grief? What is the problem? > > Best, > George > dtrace -G requires the ability to modify the object files in-place before linking. This causes havoc if the objects are in .a archives (dtrace can't read those) or if the objects need to be linked into multiple binaries. It also destroys the ability to do an incremental build, as dtrace -G can't be run on the same object twice. The whole process is really a hack. The build actions done by dtrace should be done by the compiler and linker instead. Getting the linker to support the process would go a long way, as then dtrace -G could be run on individual objects and most of my complaints go away.