Date: Fri, 13 Mar 2015 19:59:31 +0200 From: Konstantin Belousov <kostikbel@gmail.com> To: Nathan Whitehorn <nwhitehorn@freebsd.org> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r279937 - in head/sys/powerpc: include powerpc Message-ID: <20150313175931.GA2379@kib.kiev.ua> In-Reply-To: <5503224A.3010100@freebsd.org> References: <201503122115.t2CLFdmi026986@svn.freebsd.org> <20150312212234.GS2379@kib.kiev.ua> <55020547.7050102@freebsd.org> <20150312213530.GT2379@kib.kiev.ua> <5502094D.5090001@freebsd.org> <20150313084702.GV2379@kib.kiev.ua> <550318FD.1070906@freebsd.org> <20150313172345.GY2379@kib.kiev.ua> <5503224A.3010100@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Mar 13, 2015 at 10:45:46AM -0700, Nathan Whitehorn wrote: > We'll need to hack the compiler in this case, since it assumes setjmp() > saves and restores the vector registers. I'm really not sure which > option is worse. Changing the compiler is arguably much worse than breaking ABI of the tier 2 platform, indeed. We must maintain the situation where the stock build of the compilers work out of box. Still, how the compiler' assumptions are laid out ? It could be argued that compilers on x86 also assume that FPU register file is restored by longjmp. %st* and %xmm* are defined as not preserved across function calls, but I suspect that practical rule for setjmp() is that floating vars better not be used in the target frame. Hm, indeed f14-f31 and v20-v31 are marked as non-volatile for 64bit ABI.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150313175931.GA2379>