Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 23 Oct 2018 16:26:41 +0300
From:      Lev Serebryakov <lev@FreeBSD.org>
To:        Ryan Stone <rysto32@gmail.com>
Cc:        freebsd-hackers@freebsd.org
Subject:   Re: What is wrong with dtrace's stack()?
Message-ID:  <5bbf4ebe-c62a-3c6d-617f-d1c832d87cf5@FreeBSD.org>
In-Reply-To: <CAFMmRNz35Ay82NcMnUkSAvpyU5p2m9ykiji1xXcbEanH9A2H%2Bw@mail.gmail.com>
References:  <170994671.20181021201021@serebryakov.spb.ru> <CAG6CVpVCe-8OVU%2BKEyAh8swFSAjRshNcNLN0tjAS3W8bZxyrTA@mail.gmail.com> <475670271.20181022003734@serebryakov.spb.ru> <CAOtMX2goztCYJXM72WNR711DEBEKAGk1zFHF=NpE4UiVAF2bAQ@mail.gmail.com> <234d745d-37a9-9610-15b9-0f5cd5af21bf@FreeBSD.org> <b30f2080-1037-1752-60fb-6d22e28ce90d@FreeBSD.org> <CAFMmRNz35Ay82NcMnUkSAvpyU5p2m9ykiji1xXcbEanH9A2H%2Bw@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--TBzVzW1niMUhHplfKbuanMsOfPGfwxkNK
Content-Type: multipart/mixed; boundary="4ZnTLQATgwaJPyMTWhLp0DW4j7CQmgB8L";
 protected-headers="v1"
From: Lev Serebryakov <lev@FreeBSD.org>
Reply-To: lev@FreeBSD.org
To: Ryan Stone <rysto32@gmail.com>
Cc: freebsd-hackers@freebsd.org
Message-ID: <5bbf4ebe-c62a-3c6d-617f-d1c832d87cf5@FreeBSD.org>
Subject: Re: What is wrong with dtrace's stack()?
References: <170994671.20181021201021@serebryakov.spb.ru>
 <CAG6CVpVCe-8OVU+KEyAh8swFSAjRshNcNLN0tjAS3W8bZxyrTA@mail.gmail.com>
 <475670271.20181022003734@serebryakov.spb.ru>
 <CAOtMX2goztCYJXM72WNR711DEBEKAGk1zFHF=NpE4UiVAF2bAQ@mail.gmail.com>
 <234d745d-37a9-9610-15b9-0f5cd5af21bf@FreeBSD.org>
 <b30f2080-1037-1752-60fb-6d22e28ce90d@FreeBSD.org>
 <CAFMmRNz35Ay82NcMnUkSAvpyU5p2m9ykiji1xXcbEanH9A2H+w@mail.gmail.com>
In-Reply-To: <CAFMmRNz35Ay82NcMnUkSAvpyU5p2m9ykiji1xXcbEanH9A2H+w@mail.gmail.com>

--4ZnTLQATgwaJPyMTWhLp0DW4j7CQmgB8L
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 22.10.2018 23:50, Ryan Stone wrote:

> Adding -fno-optimize-sibling-calls to the compiler flags will eliminate=
 the TCO.
 How could I add it for kernel properly?! Adding
"CFLAGS=3D-fno-optimize-sibling-calls" to make.conf affects modules build=
,
but not kernel itself (I'm surprised, to be honest).

--=20
// Lev Serebryakov


--4ZnTLQATgwaJPyMTWhLp0DW4j7CQmgB8L--

--TBzVzW1niMUhHplfKbuanMsOfPGfwxkNK
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQKTBAEBCgB9FiEE+W0coLX0MYtnSzMK6rA8WL/cR48FAlvPIZFfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEY5
NkQxQ0EwQjVGNDMxOEI2NzRCMzMwQUVBQjAzQzU4QkZEQzQ3OEYACgkQ6rA8WL/c
R49Ekg/5Af0mNVcISW0qkaVfRorKq7k325x+lwLTUYbhVfpTlTKAxrEPyZl9s8Bn
+7gQPSuqgXXFDy4H+WSogNml2NZW6IPHcOJryWdgu4Sx3a3VtVmwI5szpN/GiFU/
nVpc4KvUs/0sv59LsFjjkxULwjilCK7eb9RRGky5gMCRvTS4ukRTJCf2i+rBVvg1
uDDQSec+IKvtqBqdcR3sGAgBzg8RCOQ2CRfziS3EobRHOBjJw5u7NDswhd0LC8TY
l/6hJsMUxZPUwzeIeeF5uCuHpRyGTw6vpM3RWC7wetHgq/1SdVgHmUnM1YBmgrjz
UECpAsnlsmdDK1Ae405ZnF6YI9PT7+0XGrhm4AQiYzT0YmNfjMudNQHtfoyTKMKN
GhuumzAGV+bw8ogxt1qTrIynZjoSE91naBzcdPeegwiyP/mOuPAs0q7eT165FVjo
Vh4Ym1bDjQra9N/b/85TO6XnpNdqZoSrIyvPnQNsdBdpjCINc/l1dqZWPOeOwz3m
+jqWWlkx5gFODSeM7R8Mp5BQxWPVAN9oguoCnafQb+cPjEHap6lV/sB3gQ+b3fl+
W4MurHBLsE7j1lwGLfnlaNoVXUccOkPkqoq2hTum+dsUuMzEx2gyA3Apex0aBlQc
WgAhvRSx41IP4TavvHihpBM/gA1ifmdRdA8gdOqJWxb9eGZV2r8=
=GLNf
-----END PGP SIGNATURE-----

--TBzVzW1niMUhHplfKbuanMsOfPGfwxkNK--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5bbf4ebe-c62a-3c6d-617f-d1c832d87cf5>