Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 7 Mar 2016 11:50:53 -0700
From:      Warner Losh <imp@bsdimp.com>
To:        Dimitry Andric <dim@freebsd.org>
Cc:        src-committers <src-committers@freebsd.org>, "svn-src-all@freebsd.org" <svn-src-all@freebsd.org>, "svn-src-head@freebsd.org" <svn-src-head@freebsd.org>
Subject:   Re: svn commit: r296428 - head/sys/boot/common
Message-ID:  <10F1E4F3-BE8A-4BC3-AFC3-FB4C3A729B60@bsdimp.com>
In-Reply-To: <C6FFFB5D-EAE1-4BFA-90EC-6AE2DF67A921@FreeBSD.org>
References:  <201603061557.u26FvhMi033982@repo.freebsd.org> <56DCD52F.4010709@freebsd.org> <AC0A9708-B618-4D05-8532-BD451AB94A60@FreeBSD.org> <1457365187.13785.174.camel@freebsd.org> <20160307155217.GJ67250@kib.kiev.ua> <CANCZdforb7gAanu4Hys6b2NmhOGVGn7UutsUqav5gGUsqSTMxA@mail.gmail.com> <C6FFFB5D-EAE1-4BFA-90EC-6AE2DF67A921@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--Apple-Mail=_0F3D2FDE-B021-4B5D-A595-A66AF3B5A464
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On Mar 7, 2016, at 10:41 AM, Dimitry Andric <dim@freebsd.org> wrote:
>=20
> On 07 Mar 2016, at 17:28, Warner Losh <imp@bsdimp.com> wrote:
> ...
>> Alternatively, is there a switch to clang 3.8 that says 'Don't =
generate the new
>> relocation, use the old one instead" which would also be safe and =
allow a
>> less-bumpy transition?
>=20
> On amd64, we actually compile source files for the kernel with
> -fno-asynchronous-unwind-tables, which is the flag that ensures object
> files do not end up with a .eh_frame section, because the compiler =
will
> refrain from inserting CFI directives into the assembler.

Excellent.

> However, this only affects C source files, and we have a number of
> hand-written assembler sources in the tree, with CFI directives in =
them.
> These will always result in .eh_frame sections, unless there is =
another
> assembler-specific flag of suppressing that.

what are the odds of fixing this? Since the vast majority of assembler =
code
is going to be in the base kernel. The AESNI stuff is the only exception
that I can think of=E2=80=A6

Are the CFI directives so that DTRACE works, or is there some other =
reason?

Warner


--Apple-Mail=_0F3D2FDE-B021-4B5D-A595-A66AF3B5A464
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJW3c2NAAoJEGwc0Sh9sBEAUqwP/1SksK5IiSg25Ui0EpcLfOXs
C2j33VzFUxTCnPMERgPW+gs5dHHE8MnMWl2LgDGmPeVtTn9R27wjqliOK1z6laOk
DkCvveuvQrodaO43ZcBgqWnkyq4feRAMCq0KDVPG+LDFI++7i8Lhfi+WbmGL+q09
l0AnYMLy7nbQD7zqbIg235MyWxf4fuByrw+jWcGje+LrB/P1TgrwtRkOAuGQX7eh
ihxYarEd7XF0+H9r5Byk5aXR33XyKIbJQCIAk7Vismom3YkPhHvPSuDGNpkrBf5L
T0KhBNdPF/9x5sQUBOIZ4lMxKEnGoUQPgKvAolJxuDZdMUlHfUYQ+QS9uoAQVD8t
ySwd8GO/ngqPk0GmzzDwhGiR9hH3ugbhChkxin70jcCf7mZia0ARvFTlgeTbrl1I
MLiKJMm5yUTkhGa5CSXWB9/cH1cBTHHNWksjInZ+KXFjgNBTulzWrA+klSaNMjkH
gi2Or/hyMrXX0os8zwJI8SAMuQzfPuBHbRnjhHhcKhrpar/QSa9MIR1201/bF7yN
5Nv4dlCTS+6eXsMBH13PnDtF1CESUiMUBZsJX9gNgqQvHqEwqTig3DhyBHR4yytB
rJukKlw/1fczz7wxKDKrS416NxdD1iJ0klGpLYlykNxQb3M41menBps7WGYDMTsM
p2SBhZEy8AS2ohgC9D5g
=kUVS
-----END PGP SIGNATURE-----

--Apple-Mail=_0F3D2FDE-B021-4B5D-A595-A66AF3B5A464--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?10F1E4F3-BE8A-4BC3-AFC3-FB4C3A729B60>