Date: Mon, 17 Apr 2017 14:26:10 -0700 From: Mark Johnston <markj@FreeBSD.org> To: Sevan / Venture37 <venture37@gmail.com> Cc: Ryan Stone <rysto32@gmail.com>, George Neville-Neil <gnn@neville-neil.com>, freebsd-gecko@freebsd.org, Jan Beich <jbeich@freebsd.org>, "freebsd-dtrace@freebsd.org" <freebsd-dtrace@freebsd.org> Subject: Re: DTrace issues? Message-ID: <20170417212610.GE18960@wkstn-mjohnston.west.isilon.com> In-Reply-To: <CA%2BU3Mf4y4yyqdmXiHANniu3eeYF5WMhd8jXMiWGs13Z3a3-=OQ@mail.gmail.com> References: <3CEE1970-719B-42D1-A95A-FEAD3F375A30@neville-neil.com> <20170212191826.5599A45EA@freefall.freebsd.org> <shlc-anmv-wny@FreeBSD.org> <77416dea-1e9d-4911-b5d0-2ebac227af7e@Spark> <wpam-jesd-wny@FreeBSD.org> <76897620-E958-4AE2-9B6C-062C59526614@neville-neil.com> <CAFMmRNwudC_bb_rqus=fqM4tdwVp58fxUByLUmT8Df1J1Pdb7A@mail.gmail.com> <CA%2BU3Mf4y4yyqdmXiHANniu3eeYF5WMhd8jXMiWGs13Z3a3-=OQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Apr 17, 2017 at 09:28:07PM +0100, Sevan / Venture37 wrote: > On 17 April 2017 at 20:54, Ryan Stone <rysto32@gmail.com> wrote: > > On Sat, Apr 15, 2017 at 10:50 AM, George Neville-Neil <gnn@neville-neil.com> > > 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. > > Not to detract from the issue with the -G flag, I just wanted to > highlight that it's used for ELF binaries, until Apple switches away > from Mach-o, this wont be an issue there (dtrace on OS X does not > feature the -G flag). I think the more significant difference is that Apple has more control over their toolchain and have modified it to directly implement the functionality that's overwise implemented by dtrace -G. As Ryan pointed out, this functionality really belongs in the static linker; one more piece of evidence for this is the number of non-trivial modifications we've needed to make to dtrace -G to avoid relying on undocumented behaviour in the Sun link editor, and later, GNU ld 2.17. Now that FreeBSD is transitioning to lld, we have some opportunity to implement USDT support in the static linker, and at least one of the lld developers seems amenable to proposals along those lines. However, I don't know of any concrete plans or designs.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170417212610.GE18960>