Date: Wed, 22 Feb 2017 12:06:38 -0500 From: Ed Maste <emaste@freebsd.org> To: Warner Losh <imp@bsdimp.com> Cc: "freebsd-mips@freebsd.org" <freebsd-mips@freebsd.org> Subject: Re: Retiring __ABICALLS__ Message-ID: <CAPyFy2AChAkNkyFB8sj5jsDgoR05SGiU1S9_EnK8GsLSOdFAfQ@mail.gmail.com> In-Reply-To: <CANCZdfpv_k9HGjBaQWVUKhKx81oaTZg6NgKaLkjBijEydcVr3g@mail.gmail.com> References: <20170221194748.GA16066@britannica.bec.de> <CANCZdfpv_k9HGjBaQWVUKhKx81oaTZg6NgKaLkjBijEydcVr3g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 21 February 2017 at 14:56, Warner Losh <imp@bsdimp.com> wrote: > While this is for NetBSD, I think we should do something similar, if > such work isn't already in progress. > > Warner > > ---------- Forwarded message ---------- > From: Joerg Sonnenberger <joerg@bec.de> > Date: Tue, Feb 21, 2017 at 12:47 PM > Subject: Retiring __ABICALLS__ > To: port-mips@netbsd.org > > > Hello all, > GCC has moved to defining __mips_abicalls when -mabicalls is used a long > time ago for the generic MIPS code. I agree with Warner. FYI, this came up on the LLVM list, in https://reviews.llvm.org/D29032. The initial patch proposed defining __mips_abicalls on Linux (only) and __ABICALLS__ on the BSDs (only). Joerg and I argued for having __mips_abicalls defined everywhere.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2AChAkNkyFB8sj5jsDgoR05SGiU1S9_EnK8GsLSOdFAfQ>