This is the mail archive of the
mailing list for the GCC project.
Re: [PATCH] Use __inline instead of inline in emmintrin.h
- From: Daniel Jacobowitz <drow at false dot org>
- To: Jakub Jelinek <jakub at redhat dot com>
- Cc: Mike Stump <mrs at apple dot com>, Richard Henderson <rth at redhat dot com>,gcc-patches at gcc dot gnu dot org
- Date: Fri, 3 Jun 2005 11:36:31 -0400
- Subject: Re: [PATCH] Use __inline instead of inline in emmintrin.h
- References: <20050530155106.GB22349@devserv.devel.redhat.com> <DF21F173-D194-11D9-BA1B-003065BDF310@apple.com> <20050531080854.GE22349@devserv.devel.redhat.com>
On Tue, May 31, 2005 at 04:08:55AM -0400, Jakub Jelinek wrote:
> On Mon, May 30, 2005 at 10:28:51PM -0700, Mike Stump wrote:
> > On Monday, May 30, 2005, at 08:51 AM, Jakub Jelinek wrote:
> > >Given that __inline is used a few hundred times in *mmintrin.h and
> > >inline just for the 6 inlines added in January, I think the following
> > >patch makes sense if not for anything else, then for consistency.
> > >Ok for HEAD/4.0?
> > Hum, for Altivec, we found we like always inline... Any reason to not
> > do that here as well?
> inline doesn't work with -std=c89 -pedantic-errors, __inline or __inline__
I'm guessing that Mike meant __attribute__((__always_inline__)). Which
would make sense...