Date: Fri, 6 Feb 2009 13:19:06 -0500 From: Klapper Zhu <klapperzhu@gmail.com> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: To John Birrell: weird behaviors of DTrace on amd64 Message-ID: <a29c138b0902061019y7891fa78s59376582f72f2904@mail.gmail.com> In-Reply-To: <200902051311.00091.jhb@freebsd.org> References: <a29c138b0902050831q13844f7bm3aa3bdebdcb9733e@mail.gmail.com> <200902051311.00091.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi John, I rebuilt kernel with -fno-inline and I got all isp(4) functions listed in fbt. I noticed that there are other inline related flags "--finline-limit=8000 -param inline-unit-growth=100 -Winline". should I get rid of them OR -fno-inline will just overide them ? Thanks, anyone has suggestion for problem 2 ? On Thu, Feb 5, 2009 at 1:10 PM, John Baldwin <jhb@freebsd.org> wrote: > On Thursday 05 February 2009 11:31:52 am Klapper Zhu wrote: >> Hi John Birrell, >> >> I am exploring DTrace on "7.1-STABLE FreeBSD amd64" and I found several >> weird behaviors: >> >> 1) Not all kernel functions show up in fbt provider. Take isp(4) as example: >> "dtrace -l" shows >> static void isp_freeze_loopdown(ispsoftc_t *, int, char *); >> ___but not___ >> static void isp_handle_platform_atio2(ispsoftc_t *, at2_entry_t *); >> >> Both are static functions. But one shows up in fbt, another not. >> What's the rational behind it ? Any way to fix it ? > > Perhaps gcc inlined it? Try using -fno-inline perhaps. > > -- > John Baldwin >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a29c138b0902061019y7891fa78s59376582f72f2904>