Date: Thu, 27 Mar 2014 23:03:11 -0400 From: Mark Johnston <markj@freebsd.org> To: Dimitry Andric <dim@freebsd.org> Cc: freebsd-stable stable <freebsd-stable@freebsd.org>, Kai Wang <kaiw@freebsd.org> Subject: Re: HEADS UP: merged llvm/clang 3.4 Message-ID: <CAMw1wOxgwC47sj_rDvzys7_xb8%2BYRz=kdMq9dj=Z=WchypmU5Q@mail.gmail.com> In-Reply-To: <C0345D09-CC49-49F6-ACCA-B85C7882AAC3@FreeBSD.org> References: <0E7E81A1-54E9-4920-A360-005A1C0C4D47@FreeBSD.org> <20140327002240.GC49672@raichu> <C0345D09-CC49-49F6-ACCA-B85C7882AAC3@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Mar 27, 2014 at 6:32 PM, Dimitry Andric <dim@freebsd.org> wrote:
> On 27 Mar 2014, at 01:22, Mark Johnston <markj@freebsd.org> wrote:
>> On Fri, Mar 21, 2014 at 07:17:22PM +0100, Dimitry Andric wrote:
>>> Hi,
>>>
>>> I have just merged llvm and clang 3.4 release to stable/10 (r263508) and
>>> stable/9 (r263509). This already includes a number of post-3.4 fixes,
>>> though there are a few that are still awaiting the MFC timeout (e.g. the
>>> updated Sparc64 backend, and some things that were just fixed the day
>>> before yesterday).
>>>
>>> Since the most obvious problems have already been addressed in head, I
>>> expect this to be a fairly smooth upgrade. If you run into something
>>> strange anyway, please reply to this message (CC'ing the list).
>>>
>>> -Dimitry
>>>
>>
>> Hello,
>>
>> DTrace seems to no longer work properly on stable/10; I get errors like
>> the following
>>
>> dtrace: invalid probe specifier pid$target::malloc:entry{ }:
>> "/usr/lib/dtrace/io.d", line 49: cannot find type: struct devstat*: Type
>> information is in parent and unavailable
>>
>> and I know of a couple other users running into the same problem.
>>
>> I recall that some changes to libdwarf, libelf and the CTF tools were needed
>> in order to work with clang 3.4; do you know if there's any plan to MFC them
>> soon as well?
>
> I have taken a look, but libdwarf and libelf were reorganized quite a
> bit, and it would require library bumps, which are difficult (but
> apparently not unheard of) for stable branches. I am also not sure if
> the actual workarounds can be successfully ported back to the versions
> of libdwarf, libelf and CTF in stable/10 and stable/9.
Is there any reason that the newer libdwarf and libelf couldn't
coexist alongside libdwarf and libelf in stable/9 and 10? That is,
install them to /usr/lib/private or so and have the CTF tools link
against them instead of the system libraries.
>
> In other words, it is going to take a while to fix it. If you really
> need DTrace, you can compile your kernel with gcc for now.
I'm willing to work on the above if there's consensus that it's an
acceptable solution. To my knowledge, 10.0 is the first release where
(kernel) DTrace works out of the box; it's rather unfortunate that
stable/10 has regressed to a point where DTrace is just completely
broken when using the system compiler, especially now that gcc is no
longer built by default.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAMw1wOxgwC47sj_rDvzys7_xb8%2BYRz=kdMq9dj=Z=WchypmU5Q>