Date: Tue, 10 Oct 2017 23:14:28 +0200 From: Marius Strobl <marius@freebsd.org> To: Mark Linimon <linimon@lonesome.com> Cc: Gerald Pfeifer <gerald@pfeifer.com>, "A. Wilcox" <AWilcox@Wilcox-Tech.com>, freebsd-sparc64@FreeBSD.org, freebsd-arch@freebsd.org Subject: Re: future of sparc64 (was: Making C++11 a hard requirement for FreeBSD) Message-ID: <20171010211428.GA51868@alchemy.franken.de> In-Reply-To: <20171007174124.GA20810@lonesome.com> References: <CANCZdfq5=KRp4NYKsc15gyS9C7CxrBFxcKQLPwnb_0oPb15vJw@mail.gmail.com> <20171005234149.GE8557@spindle.one-eyed-alien.net> <59D6CA6C.1040502@Wilcox-Tech.com> <20171007174124.GA20810@lonesome.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Oct 07, 2017 at 12:41:24PM -0500, Mark Linimon wrote: > > All gccs > 4.9 fail to build. Looking at the logs AFAICT the failure > is a floating-point exception as soon as the first built binary is run > during the internal testing. The most plausible cause for that is executables and/or dynamic libraries not installing the user trap handlers as specified by the libc 64 psABI, i. e. not call __sparc_utrap_setup(). Do the ports GCCs use their own CRT nowadays? Do they no longer link libc last? Please provide their linker invocation. Also, please provide the backtrace of a minimal program exhibiting that problem. Marius
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20171010211428.GA51868>