Date: Sat, 9 Jan 2016 15:03:37 +0100 From: Dimitry Andric <dim@FreeBSD.org> To: Mark Millard <markmi@dsl-only.net> Cc: freebsd-arm <freebsd-arm@freebsd.org>, FreeBSD Toolchain <freebsd-toolchain@freebsd.org>, Ian Lepore <ian@FreeBSD.org> Subject: Re: Bug 205663 Clang getting Bus Errors (arm SCLTR Bit[12]==1 context): Reported fixed on llvm's trunk Message-ID: <39774562-F76E-41E9-85E7-ABE257B013D6@FreeBSD.org> In-Reply-To: <92264003-CF0E-4624-A28A-8AFB7C663BFB@dsl-only.net> References: <C90F0ABA-3C59-4FE1-AAB4-99F8FF32FB24@dsl-only.net> <CANCZdfoWDg_ZX8zxqRV2-Q6teYf_Ef4f3VKB0fhb0sikcW3hUA@mail.gmail.com> <1452020032.1320.21.camel@freebsd.org> <7EE8F65E-7485-4FA9-A136-F22090DB107F@FreeBSD.org> <92264003-CF0E-4624-A28A-8AFB7C663BFB@dsl-only.net>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On 09 Jan 2016, at 04:46, Mark Millard <markmi@dsl-only.net> wrote: > > On 2016-Jan-7, at 2:57 PM, Dimitry Andric <dim at FreeBSD.org> wrote: ... >> FYI, I have added a -mno-movt option for this purpose upstream, and >> imported a newer snapshot into the clang380-import branch. As of >> r293384, it now uses the new option spelling for modules, if your clang >> is 3.8.0 or higher. >> >> -Dimitry > > I've not been able to get to the point of running clang++ 3.8 on the rpi2 yet: R_ARM_CALL and R_ARM_JUMP24 relocation truncations during the cross build's buildworld interfere. Yes, this is caused by too large call distances. In other words, the clang executable is getting to big to link. Apparently we need to do some tricks with -mlongcall to fix this. As I am no arm expert, I welcome any patch submissions. :-) -Dimitry [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.29 iEYEARECAAYFAlaRE00ACgkQsF6jCi4glqMbYQCghsC0QH3MmmrUFHqWtJ9jZXQW beoAoOEceiIGWKwjXg/52vnJMYh9cyfs =dait -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39774562-F76E-41E9-85E7-ABE257B013D6>
